Website Rebuild Budget Planner for EU Small Businesses

There is no single sensible price for a website rebuild. A simple service site with clear copy and a contact form needs a different budget from a multilingual site that must preserve search traffic, connect to a CRM, and serve several teams.

The useful starting point is not a page count. It is a list of the jobs the website needs to do, the risk of changing the existing site, and who will own the work after launch.

This planner helps a small service business in the EU set that budget before comparing quotes. It is a decision tool, not a substitute for a scoped proposal. Billy’s managed plans are quoted and billed in EUR.

Start with the outcome

Write one or two outcomes the rebuild must support. Good examples are specific:

• make it easier for a visitor to understand a specialist service;
• turn mobile visits into qualified enquiries;
• move routine content updates away from a developer;
• protect useful pages and leads while replacing an old platform;
• support a new market, language, or location.

An aim such as “make the website look modern” is not wrong, but it cannot decide whether copywriting, a booking flow, photography, or redirects deserve the budget. Pair the visual goal with a business outcome.

If the present site attracts visitors but produces few enquiries, first work through why a website is not getting customers. A rebuild can help, but it is not always the first fix.

Build your budget in five parts

Use the sections below to describe the project. Mark each item as essential for launch, useful soon after launch, or not needed. That makes proposals easier to compare because every supplier is costing the same underlying work.

1. Discovery and structure

This is the work that decides what pages exist and what each page should achieve. It can include reviewing the current site, mapping priority customer journeys, choosing navigation, planning service pages, and agreeing who approves content.

Keep this part light for a new business with one clear offer. Give it more room when the existing site has many pages, several audiences, or established search visibility. Cutting discovery often means paying to redesign the same page twice later.

2. Content and proof

List what is ready: service descriptions, photography, testimonials, case studies, team details, legal copy, and prices. Then list what must be written, selected, translated, or approved.

Content is frequently the real pace-setter. A build can move quickly when the business has clear, approved material. It slows down when every page needs a new decision from several people. Include the time or supplier cost for that work rather than treating it as free input.

3. Design and build

Describe the number of distinct page types, not only the number of pages. A homepage, service page, case study, article, contact page, and location page may use different components and review cycles.

Also record the functional work: forms, booking, payments, newsletter signup, CRM routing, multilingual content, member access, or staff editing. A contact form and a lead-routing workflow are not equivalent tasks.

4. Migration and launch protection

Existing sites carry technical history. This category may include URL inventory, redirect mapping, domain and DNS access, analytics, consent tooling, email delivery, Search Console, sitemap setup, backups, and a rollback plan.

It matters most when the old website already receives enquiries or organic visits. Read the website redesign checklist before deciding this work is optional. Losing a useful URL or a working form can cost more than the apparent saving.

5. Care after launch

Ask what happens in the next 12 months: hosting, monitoring, security updates, backups, support, small edits, performance checks, third-party subscriptions, and emergency response.

Some businesses prefer a handover and an internal owner. Others prefer an ongoing managed relationship. Neither model is automatically better; the important point is to compare the full first-year and likely three-year cost, not only the initial deposit.

Use three scope levels

After listing the work, sort the project into a scope level. This is more reliable than asking for “a five-page website” and hoping every supplier makes the same assumptions.

Scope level	Usually includes	Watch for
Essential presence	Clear offer, a few core pages, contact route, mobile testing, basic technical setup	Missing ownership, analytics, or a plan for future edits
Lead-focused rebuild	Content improvements, focused service pages, proof, conversion paths, form testing, existing-site migration	Unclear content approvals or uncosted integrations
Complex operational site	Multiple audiences or markets, languages, CRM or booking flows, detailed migration, staff workflows	Extra coordination, testing, and ongoing support requirements

You do not need to choose a supplier before choosing the level. The level simply makes the trade-offs visible. A small site can still need a lead-focused rebuild if it has valuable traffic or an important buying decision.

Compare proposals on the same sheet

Put each quote into one table with the same rows:

• upfront build and discovery;
• content, design, and image work;
• integrations and third-party subscriptions;
• migration, redirects, and launch checks;
• hosting, support, and routine edits;
• VAT, payment terms, cancellation, ownership, and handover.

Then ask four questions. What is explicitly excluded? Who tests the important customer journeys? Who controls the domain and core accounts? What is the cost and process if the relationship ends?

A lower upfront number may still be the right choice. It is only a meaningful comparison when it covers the same responsibilities as the alternatives.

Keep a contingency for discoveries

Older websites often reveal work after the project starts: inaccessible accounts, broken form delivery, missing image licences, duplicate pages, plugin dependencies, or URLs that need special handling.

Set aside a modest contingency or agree a clear change-control process. The goal is not to create vague scope; it is to stop a genuine discovery from becoming an argument about who pays for it.

A practical way to decide

Before requesting quotes, prepare a one-page brief with your outcome, audience, essential pages, required features, available content, current accounts, deadline, and chosen scope level. Give that same brief to every provider.

For a simple comparison of delivery models, see agency vs freelancer vs Website-as-a-Service. The best option is the one that makes the work, responsibility, and future cost clear enough for you to manage with confidence.