How to write a website brief that gets accurate quotes

Business owners and marketing leads often reach out to freelancers and agencies with a simple question: how much will it cost to build our new website? The replies they get back are often baffling. One developer might estimate $2,000, another might propose $15,000, and a third might decline to quote entirely without several paid discovery calls.

This wide variance rarely means developers are guessing at random. In most cases, the difference comes down to ambiguity in the project brief. When details are vague, cautious developers add significant contingency pricing to cover hidden complexity, while optimistic developers submit low bids only to surprise you with change orders once development begins.

When I build a new Next.js + Sanity website, having clear technical and functional parameters from day one allows me to outline exact milestones, suggest appropriate architecture, and provide a realistic estimate. Writing a solid brief does not require technical expertise, but it does require answering a few fundamental questions upfront.

Define your commercial goals and primary user actions

A developer needs to understand the business problem the website solves, not just the visual aesthetic you want. A marketing site designed to educate enterprise buyers on complex software requires a different technical approach than a direct-to-consumer page optimized for quick signups.

Start by describing your company in two or three sentences, followed by the specific business problem triggering this build. State whether you are launching a new brand, redesigning to support a higher tier of client, or fixing a slow existing platform that struggles to convert traffic.

Identify the primary conversion goal for the site. If the main goal is booking a sales call via an embedded calendar, the development setup will look quite different than if the user needs to calculate pricing or create an account.

• State your target audience and the industry sector you serve.
• Identify the single most important call to action on the site.
• Mention existing metrics if relevant, such as current monthly traffic or bounce rates.

List page templates instead of just total pages

One of the most common pitfalls in website briefs is stating a raw page count, such as we need a 25-page website. To a developer, total page count says very little about the actual scope of work.

In modern web development, websites are built around templates and reusable components. A site with 40 blog posts using one single post layout takes far less development time than a 6-page marketing site where every page features custom interactive charts, unique filtering systems, and distinct section layouts.

Group your sitemap into distinct page layouts. For each layout, note whether it uses standard text and image blocks or requires bespoke interactive elements such as filtering systems, searchable directories, or interactive calculators.

• Homepage with custom modular marketing sections.
• Service detail page template used across multiple offerings.
• Case study layout with client quotation blocks and metric callouts.
• Resource hub with category filtering and pagination.
• Standard utility pages, such as privacy policies and simple contact forms.

Clarify design status and content readiness

Content and design bottlenecks stall more website builds than code bugs. If a developer assumes you already have production-ready designs and finalized copy, their quote will cover only development implementation. If they later discover they must design layouts or write copy, the timeline and budget will quickly break apart.

Specify the exact state of your visual designs. If you already have completed wireframes or high-fidelity design files, mention the tool used. For example, moving from approved Figma to Next.js code is a defined implementation task because the layouts, typography, and spacing tokens are already resolved.

Be honest about the state of your text and media assets. State clearly whether copy is written and approved, if high-resolution photography is ready, or if existing assets need to be migrated from an older system.

Document all third-party integrations and CMS needs

Surprise integrations are a leading cause of scope creep. A brief that simply says includes a contact form might mean a simple email notification, or it might mean routing lead data through HubSpot, validating the entry against an email verification service, and sending an instant SMS alert.

List every external software tool your business relies on that must connect to the website. This includes customer relationship management (CRM) software, newsletter platforms, analytics suites, scheduling tools, and transactional email providers.

You should also outline how your team plans to manage content after launch. If non-technical marketers need to create new landing pages independently, the developer needs to build a modular editing system inside a content management system (CMS) like Sanity. If your content updates are rare and handled by a technical team, a simpler content setup can save initial development time.

• Form destinations, such as HubSpot, ActiveCampaign, or basic email alerts.
• Analytics and tracking scripts, such as Google Analytics, PostHog, or Meta Pixel.
• Appointment booking widgets, such as Calendly or SavvyCal.
• Content management preferences, including who will edit the site and how often.

A copy-paste website brief template

You do not need a twenty-page specification document to receive accurate proposals. A structured two-page brief provides developers with everything required to produce reliable estimates and ask targeted follow-up questions.

You can copy and adapt this outline for your next project inquiry to share via document link or direct message through a contact page:

• Project Summary: Who we are, what we offer, and why we are commissioning this build.
• Target Audience & Goals: Primary visitor persona and the exact action they should take on the site.
• Sitemap & Templates: List of unique page layouts needed, along with expected total page counts.
• Design & Assets: Current state of wireframes, Figma files, written copy, and imagery.
• Integrations: Every tool the site must connect to (CRM, email, tracking, booking, payment).
• CMS Requirements: Who will update the site post-launch and what types of content they need to edit.
• Timeline & Budget: Target launch date, non-negotiable milestones, and your expected budget range.

Practical takeaways for your next build

Writing a thorough brief takes an extra hour or two before reaching out to developers, but it saves weeks of back-and-forth negotiations and prevents expensive misunderstandings later. It allows developers to review the scope objectively, propose the right technical stack, and quote accurately rather than defensively.

When developers have clear visibility into your page layouts, third-party connections, and content readiness, their quotes become directly comparable. You can evaluate candidates based on their technical insight, communication clarity, and portfolio experience, rather than trying to decipher why their price estimates differ so drastically.

Want help with this? See my New Next.js + Sanity website service, or send me your site for a free review.