Start with the scope, then compare the price
A useful estimate explains what will be delivered, who supplies the content, what needs to connect to existing systems and what happens after launch. Use this guide to prepare a brief for Build Awesome and compare proposals on the same basis. Your written proposal should confirm the price, currency, milestones and exclusions before work starts.
What changes the cost of a website?
- Pages and customer journeys: a focused service website has a different scope from a multi-location site, booking system or customer portal.
- Content readiness: clarify whether you will supply approved copy, photography and brand assets or need help creating them.
- Features and integrations: booking, payments, CRM connections and custom forms add implementation and testing work.
- Existing-site migration: preserving useful URLs, moving content and checking tracking are separate tasks from designing new pages.
- Review and launch requirements: agree who approves the work, the revision allowance and any fixed launch dependencies.
See our website design and development service for the core project scope.
Separate project work from ongoing costs
A website build or automation project may be a defined piece of work. Maintenance, content production, advertising management and reporting may need ongoing support. Ask for these items to be shown separately so you can see the initial investment and continuing commitments.
- Website management: confirm update coverage, backups, monitoring, support hours and any included content edits. Review website maintenance responsibilities.
- SEO and content: define the audit, priority pages, writing responsibilities and reporting cadence. Explore small-business SEO and content support.
- Paid advertising: distinguish platform media spend from setup, creative, landing-page and management fees. Review paid advertising scope.
- Third-party services: identify domain, hosting, software subscriptions and usage charges, including who owns and pays for each account.
Budgeting for analytics and automation
Analytics scope depends on the number of data sources, tracking gaps, conversion definitions and reporting questions. Automation scope depends on the workflow, system access, API limits, exception handling and ongoing maintenance. A clearly bounded first workflow or reporting question is easier to estimate than an undefined request to automate everything.
Review analytics and tracking options or custom automation and systems integration before choosing the work to include.
What to include when requesting an estimate
- Your website URL and the main business problem.
- The action you want customers or staff to complete.
- Required pages, features and connected systems.
- Content and account access you already have available.
- Your preferred timing and budget range, if known.
- The person who will review and approve the work.
Questions to settle before committing
Can you publish a fixed price for every project?
This page does not list fixed packages. Request a proposal based on your actual requirements, with deliverables and exclusions clearly documented.
How should I compare two estimates?
Compare the same deliverables, revision allowance, ownership and access arrangements, launch support and ongoing costs. A lower initial quote may exclude work that another proposal includes.
Can the project be delivered in stages?
Ask which essential customer journey or operational task should come first, and which features can wait. Any staged delivery, schedule and payment milestones should be confirmed in the proposal.