Plan your business website before asking for a design
Two website proposals can have very different prices because they describe different work. One may provide a small set of pages using an existing design. Another includes research, copywriting, integrations, migration and ongoing support. Compare them only after you have defined what the business needs.
Seven decisions will make the brief clearer. They also expose the work that is easy to omit from an attractive launch price.
1. Decide what the site must achieve
A contact-focused site helps an existing prospect confirm the service and get in touch. A lead-generation site needs persuasive service explanations and a reliable enquiry process. A publication needs an editorial workflow. An online shop needs payments, order handling and appropriate customer information.
Choose the main job and describe how success will be checked. Do not add a shop or complicated booking system simply because it appears in a template. Every extra function creates content, testing and maintenance work.
Define the audience in practical terms: buyer role, service need, language and actual countries served. “Everyone in Europe” is not a useful brief if the service has geographic or operational limits.
2. Keep domain ownership clear
The business should retain appropriate registration rights, renewal control and recovery access. A supplier may manage technical settings, but the arrangement should not leave ownership ambiguous.
Choose a domain that fits the brand and intended market. Check eligibility and registration conditions for the extension. Keep renewal details current and enable strong protection on the registrar account.
A later domain change is possible, but it requires redirects, updates to linked services and monitoring. There is no universal search-recovery timetable. Our domain basics guide explains the ownership questions.
3. Choose an operating model for hosting
A self-managed server gives a capable team control and responsibility for the operating environment. Shared hosting can provide a simpler environment, but application tasks still depend on the package. Managed WordPress hosting adds specified maintenance work.
Ask about supported software, backups, restoration, updates and response arrangements. Do not infer security quality from price alone or assume every service called managed includes the same tasks.
ResaHost web hosting places hosting and agreed technical maintenance with one team. Review the plans for scope, plugin limits and first-response commitments. Content creation and new functionality need a separate agreement where not included.
4. Match the builder to the scope
| Route | What you should be ready to provide | What to verify |
|---|---|---|
| Build it yourself | Time, learning and ongoing ownership | Whether the critical functions exceed your skills |
| Freelancer | A clear brief, content and timely decisions | Handover, cover and support after launch |
| Agency | Business input and an approval process | Which specialists and deliverables are actually included |
A freelancer can deliver a complex project and an agency can deliver a modest one. Judge the proposal, relevant work and continuity arrangements rather than assuming the label establishes quality.
Our WordPress DIY versus professional guide goes deeper into those trade-offs. Ask every bidder to price the same required work before comparing totals.
5. Prepare the content package
List the pages and give each one a purpose, main message and next action. Write the service facts first: scope, exclusions, process, geography and quotation basis. Identify who will supply images, permissions, customer examples and translations.
Do not prescribe a page length simply to fill a design. A concise contact page and a detailed technical guide have different jobs. Remove repeated generic claims and explain the evidence behind stronger statements.
For an English version of an existing national site, decide what should be adapted and what should be left out. Country-specific comparisons and legal case stories may not help a broader audience. Preserve relevant technical guidance and link to the appropriate European context.
6. Include search, measurement and privacy before launch
Agree descriptive URLs, titles and internal links. Map old pages to appropriate replacements when changing the structure. A search plugin helps manage fields but does not write accurate content or guarantee rankings. Google's SEO starter guide describes the foundation.
Choose useful business measurements such as qualified enquiries, not just traffic. Identify the privacy requirements of any analytics or advertising setup. Use the cookie consent guide to plan implementation and testing.
Include accessibility in the acceptance criteria: readable content, keyboard operation, labelled forms and clear feedback. Treat it as part of the build, not a cosmetic adjustment at the end.
7. Budget for the website after publication
Separate the one-off build from recurring hosting, licences and maintenance. Then identify variable work: new content, campaigns, integration changes and unusual incidents. Include your own time for approvals and content updates without assuming every hour would otherwise be billable revenue.
Ask who performs the first update after launch and who checks the form still works. Ask for a recovery demonstration or documented procedure. The website lifecycle guide connects launch with ongoing ownership.
Turn the decisions into acceptance criteria
Write down the required pages and functions, responsibilities, price basis, dependencies and what “ready to launch” means. Include account ownership, licence handover, testing evidence and maintenance contacts.
A complete brief makes the proposal concrete enough to judge. Use the step-by-step build guide when you are ready to implement it.
Frequently asked questions
How much will the site cost?
Ask for a quote against that scope. Local market estimates from another country or an old article do not establish the price of your European project.