When comparing proposals for a new website, the total price tells only part of the story. A €900 proposal and a €2,000 proposal are not necessarily comparable if one covers only a template setup while the other also includes structure, technical SEO, migration, analytics and post-launch support.
A good proposal should therefore answer the following questions clearly.
1. What exactly will be built?
The proposal should specify:
- the expected number of pages,
- languages,
- forms,
- custom modules,
- integrations,
- ecommerce, booking or other functions,
- what is included and excluded.
The term "website" is too broad to define project scope on its own.
2. Is the design custom or template-based?
Either option can make sense, but it should be stated clearly. Check:
- whether the design is created for your project,
- how many revision rounds are included,
- who prepares the mobile layouts,
- whether paid components or licences are required.
3. Who prepares the content?
Agree in advance:
- who writes the copy,
- who provides images,
- who enters the content,
- who prepares metadata,
- who handles translations.
Many projects are delayed because this responsibility was never clearly defined.
4. What does "SEO included" actually mean?
The phrase should be specific. A technical SEO foundation can include:
- page titles,
- meta descriptions,
- canonicals,
- sitemap,
- robots rules,
- structured data where appropriate,
- a fast, mobile-friendly implementation,
- redirects during a redesign.
This is not the same as an ongoing SEO campaign or a guaranteed Google ranking.
5. How will an existing website be migrated?
If you already have a website, the proposal should explain:
- what will be transferred,
- what will be preserved,
- who prepares the redirect map,
- how old URLs will be checked,
- how Search Console will be reviewed after launch.
This is particularly important when the existing website already receives organic traffic.
Tip: Everything that belongs on a migration list: Website redesign without losing SEO.
6. Who owns the domain, content and accounts?
The domain and key accounts should remain under the client's control or ownership should be explicitly agreed. Also check access to:
- hosting,
- analytics,
- Search Console,
- CMS,
- licences,
- data exports,
- what happens if you change provider.
7. What happens after launch?
A good proposal should explain:
- whether bug fixes are included,
- whether maintenance is available,
- what maintenance includes,
- how additional changes are billed,
- who monitors technical issues.
8. How is project completion accepted?
Define acceptance criteria in advance:
- which functions must work,
- which devices and browsers are tested,
- who approves content,
- which access credentials must be handed over,
- whether analytics, Search Console and sitemap are configured.
Quick comparison checklist
- scope,
- design,
- mobile,
- content,
- SEO foundation,
- migration,
- analytics,
- ownership,
- hosting,
- maintenance,
- licences,
- timeline,
- payment terms,
- acceptance criteria.
Tip: Our prices and what they include: website cost. Service: website development.
Frequently asked questions
Is a more expensive proposal always better?
No. Only proposals with the same scope are comparable. A higher price is justified when it includes more of the work you actually need — content, migration or measurement, for example — not just a bigger number.
What should I ask for if a proposal only says "SEO included"?
A concrete list: titles and meta descriptions, canonicals, sitemap, robots rules, performance, mobile optimisation and — for a redesign — redirects. Ask what is not included as well.
Who should own the domain?
The client. The domain and key accounts (hosting, analytics, Search Console) should be registered to your company, or ownership should be stated explicitly in the proposal.
How do I know the project is really finished?
When acceptance criteria were defined in advance: which functions work, which devices were tested, which access credentials were handed over and whether analytics, Search Console and the sitemap are configured.