Decide what a website needs to earn
Put a useful purpose behind the investment, including the time, attention, and ongoing work a website asks of you.

A website has a clear project cost and a less visible cost of keeping it useful. Someone updates the content, checks inquiries, renews services, and fixes information that has fallen out of date. An investment decision should account for both.
The purpose can be commercial, creative, or operational. A portfolio needs to represent the work you want to do. A community project needs to keep information accessible. A shop needs a reliable path to purchase. Write down the result that matters before comparing proposals.
Establish what is happening today
Identify the main action your site supports: an inquiry, a purchase, an appointment or an account task. Check that you can distinguish a visitor starting the action from completing it. Then review what happens after it reaches your team.
- Record which customer questions arrive repeatedly by phone or email.
- Note where someone copies data, checks an external system or follows up for missing details.
- Review failed submissions and confusing error messages.
- Check important pages on phones, with a keyboard and on a slower connection.
- Compare the site's published information with the information your team uses.
Give performance and accessibility their own checks
Web Vitals separates loading, responsiveness and visual stability. That makes it more useful than treating performance as a single impression that a site feels fast. Review the experience people actually receive as well as a controlled test.
W3C's initial accessibility checks cover practical starting points such as titles, image alternatives, headings, contrast and keyboard use. These checks can expose problems early, but they do not replace a full accessibility evaluation.
Use a business case you can defend
Estimate the time spent on a recurring manual task using a sample of actual work. Record the assumptions: how often it happens, who handles it and whether the new system would remove it or simply move it elsewhere.
Treat changes in customer behavior as a hypothesis to test. A clearer form may help people finish an inquiry, but a percentage increase borrowed from another business is not a forecast for yours. Traffic quality, pricing, demand and the offer itself all affect the result.
Price the ongoing work
Ask what you will pay for after launch and what time you will need to give the site. Include hosting, third-party services, content updates, and any maintenance agreement. Find out which changes you can make yourself and which need a developer.
Compare the same boundaries across proposals. A lower build estimate may leave photography, writing, migration, or account setup with you. That can be a good arrangement when you want those responsibilities and have time for them.
Define what you will check after launch
Before the build starts, agree on the tasks that must work and the evidence you will review. That might include successful form delivery, a complete purchase flow, fewer manual transfers or a clear way for staff to update content.
Keep the baseline and review the same measures after launch. A useful website investment should have a clear purpose and an observable result, even when the result is operational rather than a headline revenue number.
Further reading
Have a project in mind?
Share the idea, the brief, or the part you want help figuring out. We work with individuals, businesses, and creative teams.
Discuss your project