Ask three agencies for a website price and you may receive three very different answers. That does not necessarily mean one is expensive and another is good value. They may be pricing three different interpretations of what the website needs to do.
A template-led brochure site, a bespoke lead-generation platform and an integrated e-commerce operation are not comparable products. Even websites with similar page counts can involve very different levels of strategy, content, functionality and technical work.
The useful question is not simply what a website costs. It is what your business needs to invest in, why it matters and how to distinguish essential work from unnecessary scope.
Start with the role the website plays in revenue
A website that validates referrals has a different commercial role from one responsible for generating most new enquiries. A retailer's online store may also need to support merchandising, payment, fulfilment and customer service.
Define that role before setting the budget. Identify the important audiences, the actions you need them to take and the problems with the current experience. Include internal requirements where the platform needs to reduce manual work or connect systems.
Turn perspective into progress
Ready to make
the next move?
Bring the challenge to Seven52. We will help identify the clearest route forward.
This creates a basis for prioritisation. If the main constraint is unclear service messaging, a complex animation system is unlikely to be the first investment that deserves attention. If duplicate order entry is consuming the team's time, an integration may be more valuable than another layer of visual customisation.
Page count is only part of the scope
The number of pages tells you something about content volume, but very little about the complexity of the underlying work. Ten pages using one reusable layout can be simpler than five pages with different interactive requirements.
Ask how many distinct page templates are needed, what content types they support and which features require custom development. A searchable directory, product configurator or customer portal introduces work that a static page list does not reveal.
Content migration also matters. Existing information may need restructuring, rewriting, checking and importing. Images may need sourcing or preparation. Multilingual pages require a process for translation, review and ongoing updates.
A reliable scope makes these requirements visible. Without that detail, a low initial quote can become difficult to compare with a more complete proposal that includes the work needed to launch properly.
Strategy and content should not become leftovers
It is easy to treat design and development as the website project, then expect the business to supply the words later. That can leave important decisions unresolved until layouts have already been approved.
Strategy establishes the audiences, proposition, journeys and priorities. Content turns those decisions into information that helps people understand and act. Both influence what needs to be designed and built.
Clarify who will write the copy, gather case studies, prepare product information and approve the final material. If your team is supplying content, allow realistic time and give someone responsibility for coordinating it.
The same applies to photography and video. Existing assets may be suitable, but they should be reviewed early. A considered design cannot compensate for missing evidence, incomplete information or imagery that misrepresents the offer.
Budget for the connections and the exceptions
Integrations can change project complexity substantially. Connecting an enquiry form to a CRM is different from synchronising products, pricing, stock and orders between several systems.
Discuss how each connection will work, what documentation is available and who controls access. Identify the exceptions too: missing information, failed transfers, conflicting records or changes made in more than one system.
These questions help distinguish a straightforward configuration from work that needs investigation, custom logic and additional testing. Where uncertainty is material, a discovery phase can define the requirement before the full build is committed.
Avoid assuming that a named integration means every workflow is included. Ask the agency to describe the actual information flow and the business tasks it will support. That explanation is more useful than a row of software logos in a proposal.
Compare complete delivery, not just the design fee
A proposal should explain how the website moves from brief to launch. Look for the approach to design approval, development, content population, quality assurance, migration, training and handover.
Testing deserves particular attention. Ask which journeys, devices and integrations are covered and how issues will be resolved before release. Understand who is responsible for launch-day checks and what support follows immediately afterwards.
Review exclusions with the same care as inclusions. Hosting, software licences, paid extensions, photography, copywriting and third-party charges may sit outside the project fee. That is not inherently a problem, provided the full commitment is clear.
Also establish how changes are handled. A clear approval and change-control process protects both the investment and the timeline when new ideas emerge during delivery.
Consider the cost of running the website
The build fee is one part of ownership. The platform may also require hosting, subscriptions, maintenance, security work, support and future development. The balance depends on the technology and the responsibility retained by your team.
Ask for an outline of expected recurring commitments and what each covers. Distinguish keeping the website operational from actively improving its performance. Those are related responsibilities, but they are not the same service.
Internal effort matters as well. A cheaper platform that makes routine changes difficult may create additional work elsewhere. Conversely, paying for features your team will not use can add complexity without delivering value.
Compare options over a realistic ownership period, including implementation and ongoing support. The objective is a platform the business can operate and improve, not simply afford to launch.
Phase the ambition without weakening the foundation
If the ideal scope exceeds the available budget, prioritise the journeys and capabilities that create immediate value. Separate essential launch requirements from enhancements that can follow once there is evidence of demand.
Phasing works when the initial architecture supports the next stage. It fails when essential content, testing or operational requirements are removed merely to reach a lower price.
Use commercial scenarios to assess the investment, but keep assumptions explicit. Additional enquiries only create value if they are suitable and the business can convert and serve them. Revenue is not the same as profit, and a new website cannot guarantee either.
At Seven52, we scope website design and development around the commercial opportunity and the work required to deliver it properly. Book a discovery call to discuss your priorities, dependencies and budget. We will help shape a realistic scope before asking you to commit to a build.
