There is no useful price without a scope
Website estimates can differ because the underlying work differs. A small brochure site, a store and a customer portal are not equivalent projects. Begin with the audience, main journeys, page types, editing needs and launch requirements. A clear brief helps agencies estimate the same work.
Count the content work
Writing, editing, photography, translation and content migration take time. Identify what already exists, what can be reused and who will create or approve the missing material. A site with a few carefully produced pages can require more content work than a larger site using ready, structured material.
Describe the interactions and integrations
Simple enquiry forms differ from account dashboards, conditional applications or connected checkout flows. List external systems and describe the data moving between them. Include administration, validation, permission rules and failure handling, because those details affect both implementation and testing.
Compare inclusions and ongoing costs
Ask what the estimate includes for discovery, design revisions, development, content entry, testing and handover. Separate initial work from recurring hosting, domain, platform, integration and support costs. Confirm who owns accounts and how future changes are requested.
Use priorities to shape a sensible first release
If the scope exceeds the available budget, identify the smallest release that still completes a useful customer journey. Defer enhancements with clear dependencies, rather than removing essential quality checks. Request a written scope with assumptions, exclusions and acceptance criteria before agreeing the project.
Make it specific to your business.
Use our project builder to turn the ideas in this guide into a clear, shareable brief.
Build your project brief