Two websites that look alike can differ several times over in price, and that is usually not about a contractor being greedy. The difference sits in work that is not visible at first glance: the number of templates, the languages, the integrations and who prepares the content. Here is what an estimate is made of and where misunderstandings usually start.
Why similar sites cost differently
When comparing proposals it is easy to look only at the number of pages. But a page is not a page: a home page with six blocks, a service page and an order form with a calculator are three different amounts of work.
The second hidden factor is templates. A forty-page site may consist of five page types, in which case five templates are built, not forty. So the question is not how many pages there are, but how many different screens.
What shapes the scope
- The number of unique page templates rather than the total page count
- Design complexity: adapting an existing theme or custom layouts built around a brand identity
- Features: catalog, filters, price calculation, customer account, online payment
- Language versions: each adds translation, review and links between pages
- Integrations: inventory system, delivery service, payment provider, CRM, messengers
- Content: texts, photographs and service descriptions supplied by the company or produced by the contractor
- Migrating data from the old site and setting up redirects
Three items that get underestimated most often
Content. Structure can be planned in a week, but gathering real copy, photographs and service descriptions can take a month, because it needs time from the company staff. Projects are delayed by material more often than by development.
Multilingual content. Three languages are not three buttons but three sets of copy, three sets of metadata and the links between versions. If three languages are planned, allow for them from the start: adding a language to a finished site costs more than building it in.
Review and revisions. After a demo there are almost always comments. It is sensible to agree in advance how many rounds of revisions are included and what counts as a new task.
Where spending can be reduced safely
- Launch in stages: core sections first, secondary ones a month later
- Reduce the number of unique templates by reusing one layout for similar pages
- Use an existing platform instead of custom development when the task is standard
- Defer features nobody is ready to use yet: customer accounts, loyalty programmes
- Prepare texts and photographs in-house against an agreed structure
What is not worth saving on
Register the domain and hosting to the company rather than to the contractor - it is your asset, and changing suppliers should not create a problem.
Backups and the ability to restore. A copy that has never been deployed is not a backup.
The technical basis for search: page URLs, metadata, speed, links between language versions. These are set during development and cost little; fixing them after launch becomes a project of its own.
Testing forms before launch. A site that looks good and does not deliver enquiries does not pay for itself, whatever it cost.
Frequently asked questions
Why do contractors quote different prices for the same task?
Usually because the same words cover different amounts of work. In one proposal design means adapting a ready theme; in another it means custom layouts for every page type. A fair comparison is only possible against the same list of work, so it is worth asking for the scope rather than only the final figure.
Can a price be given without a detailed brief?
A range can be indicated once the project type, the number of languages and the feature set are clear. A precise estimate needs an agreed scope; without one, any figure is provisional and will almost certainly change. A short description of the task and a link to a reference site are usually enough for a first conversation.
Are there costs after launch?
Recurring costs remain in any case: the domain and hosting renew annually. Technical support is a separate decision: platform and module updates are needed regularly, otherwise the site gradually becomes vulnerable. The level of support can range from basic checks to full maintenance.