A useful website budget starts with the work the website must support. Two projects with the same number of pages can require very different content, editing tools, integrations and launch checks. Asking several suppliers for a price before those differences are visible can produce quotations that are difficult to compare.
You do not need a finished specification before the first conversation. You need a clear account of the customer tasks, the information available and the questions still unresolved. This guide helps you prepare that account before requesting quotes. Once proposals arrive, use our website proposal comparison guide to assess their actual deliverables.
Start with the customer journey
Describe what a visitor must be able to do. A service business might need someone to understand the available work and send a useful enquiry. A shop may need product selection, payment and order handling. A franchise operator may need location information, recruitment routes and several kinds of editable content.
Then identify what happens behind the screen. Who receives the enquiry? Where is it recorded? Does someone need to approve a submission or update a record? A simple-looking interface can depend on substantial business rules, while a visually rich page may need little custom functionality.
Separate page quantity from page complexity
A page count is useful for describing scale, but it does not explain every delivery task. Several service pages might share one agreed layout. A searchable directory, an article and a customer account screen may each need different information, behaviour and editing controls.
Record the page types as well as their approximate quantity. Explain which are new, which reuse existing material and which depend on decisions still to be made. Do not label an uncertain integration as a standard page simply because its first screen appears small.
Make content and approval work visible
Writing, checking, photography, image permissions and migration all take responsibility and time. Tell suppliers whether the material is ready, needs editing or must be created. Identify who can confirm service facts and approve the final version.
Approval arrangements affect the plan too. A named decision-maker and consolidated feedback make the work easier to organise. Conflicting comments from several people create unresolved decisions, rather than a useful instruction to the designer. Our website project brief guide helps record these responsibilities.
Use a scope and uncertainty worksheet
Complete a first version of this worksheet before asking for a quotation. An honest unknown gives the supplier something to investigate. It is more useful than treating an assumption as confirmed.
| Work area | What to record | Why the requirement matters |
|---|---|---|
| Pages and content types | Approximate quantities, shared layouts and any directory, product or account records. | Different structures can require different design, editing and testing work. |
| Content preparation | Existing copy and images, missing material, rights and the person approving facts. | The proposal needs to identify who creates, checks and supplies the content. |
| Connected systems | Booking, payment, CRM or email systems, their owners and available documentation. | Access and technical discovery may be needed before an integration can be scoped. |
| Migration | Existing URLs, important content, forms, accounts and services that must keep working. | Moving a site can require mapping, validation and a controlled changeover. |
| Acceptance and decisions | Representative customer tasks, approval owners and unresolved requirements. | The team needs an agreed way to recognise completed work and approve changes. |
| Ongoing operation | Hosting, editing, support, licences, renewals and responsibility for maintenance. | Launch cost alone does not describe the continuing arrangement. |
For each unresolved item, name an owner and the evidence needed to answer it. Keep essential launch work separate from later improvements, but check that a later phase is not actually a dependency of the first release.
Use examples to explain requirements
The Pups N’ Walks case study shows service and price presentation, real pet media and a local enquiry route. The AMH Family Enterprise case study includes restaurant information, stories and a bespoke CMS. These are different content and management tasks, even before discussing individual page counts.
Use a relevant example to explain the kind of task you need, then identify what differs in your business. A screenshot can clarify presentation, but it does not specify every underlying feature. These cases document delivered work; they are not prices for reproducing either website.
Include migration and continuing costs
If you have an existing website, explain what must be retained and how its important journeys work. Discuss URLs, content, domain and email dependencies before agreeing a launch approach. Our redesign and SEO planning guide covers that preparation in more detail.
Ask which costs recur and which depend on a third party. Hosting, domains, mailboxes, premium licences, payment fees and additional content work may follow different arrangements. Ask what happens when you need a change or eventually leave. The written proposal should resolve the applicable ownership, access and transfer terms.
Choose a suitable commercial route
Giraffe Digital offers separately scoped website design, monthly website plans and a free design application. Their allowances and commitments differ. The accepted free-design offer covers up to five brochure pages with £179.88 annual hosting paid upfront and the domain charged separately; it is not a promise that every requirement is included at no cost.
Compare the current terms and explain your requirements before choosing. Bespoke functionality or an unusual editing workflow needs an agreed scope. SEO, content and measurement responsibilities should also be explicit, rather than inferred from a general promise of a modern website.
Frequently asked questions
Can I request a quote before every detail is settled?
Yes. Explain the known requirements and mark the unknowns. Ask how discovery will resolve them and which parts of an initial estimate depend on assumptions. Do not treat an indicative discussion as a fully agreed delivery scope.
Does adding more pages always increase the work by the same amount?
No. Pages may share a layout, while a new content type or interactive journey can introduce additional design, editing and testing needs. Record both quantity and the different jobs those pages perform.
Should I provide a budget?
Sharing a realistic budget or constraint helps a supplier discuss priorities and possible phases. It does not replace an explanation of the requirements. Ask what the proposed approach includes and which important tasks remain unresolved.
What if the content is not ready?
Identify the missing copy, images and factual approvals. Agree who prepares each item and how that work affects the proposal and timetable. A placeholder should not quietly become a promise that someone else will supply the final material.
Should SEO and migration be included in the first discussion?
Yes, where relevant. Explain the existing website, important pages and customer journeys, and ask which checks and responsibilities are included. A redesign should not assume that a general reference to SEO covers every migration task.
How do I compare the quotations once they arrive?
Compare them against the same brief. Check deliverables, responsibilities, acceptance criteria, assumptions, recurring costs and agreed support. Resolve differences before comparing the headline amounts as equivalent offers.
Start with the worksheet and your most important customer journey. Talk to Giraffe Digital when you are ready to discuss the scope and the questions that still need an answer.


