Website development cost: prepare a clear project brief

1. Start with the visitor and the next action

Decide who the website is for and what they should do after reading it. A service business may want quote enquiries; a product page may explain one offer. Booking, online selling and a customer dashboard each introduce their own work.

For example, a tutor may need an introduction, lesson information and an enquiry form. Student accounts, paid lessons and a private dashboard would be additional requirements. This is an illustration of how scope grows, not a promise of a fixed page package.

• Who visits the site?
• What information do they need before contacting you?
• What is the main action: enquiry, booking or purchase?

2. List pages and the content each needs

Write a short purpose beside each proposed page. “Services: explain the classes, audience and how to enquire” is easier to scope than a page name alone. Avoid adding pages that repeat the same information without helping visitors.

Decide who supplies the logo, photographs, service descriptions and policy text. Say whether writing, editing, translation or image creation is needed. Reference websites help explain your preferences; they are not permission to copy another business’s content or design.

• Page list with a purpose for each page
• Logo, photographs and text you can supply
• Content that still needs writing or review
• Preferred contact details and social links

3. Describe what must work

A contact form needs decisions about its fields, where the enquiry is stored or sent, spam protection and the confirmation visitors see. A booking or payment flow needs its own scope and testing. Mention integrations and existing accounts before accepting a quote.

If you want to update content yourself, explain which parts change and how often. An editable admin area is a different deliverable from a site whose updates are handled by the developer.

• Form fields and enquiry destination
• Booking, payments or external integrations
• Who can edit which content
• Required languages and existing pages to retain

4. Separate the build price from provider charges

The starting development price does not imply a fixed page count or every feature. Domain, hosting and other provider charges are separate. Ask for the included work, exclusions and recurring services in the quote so you can compare the full requirement.

Confirm account ownership and renewal responsibility. If you already have a site or domain, explain what needs to move and what must keep working. Redirects, email arrangements and content migration should be discussed rather than assumed.

5. Agree on the schedule and acceptance checks

The delivery target is 15 days for the agreed scope. The quote confirms the schedule once the page list, content and required access are ready. A change in features or late content can change the delivery date.

Before handover, agree which pages, devices, forms and integrations will be checked. Include mobile navigation, keyboard access, form errors and confirmations. If search setup is included, specify titles, canonical URLs, crawl settings and a sitemap. These checks support discoverability; they do not promise a first-place Google ranking.

• Agreed pages and acceptance checks
• Mobile and desktop coverage
• Enquiry delivery and failure behaviour
• Code, accounts and editing instructions at handover

A brief you can send today

Use these prompts to request a quote. You can leave uncertain items open for discussion. Clear priorities help decide what belongs in the first version and what can be added later.

• My business helps [audience] with [service].
• The website should help visitors [main action].
• The pages I need are [list and purpose].
• I can supply [logo, text and photos].
• The site needs [forms, editing or integrations].
• My budget, target date and existing domain are [details].