Short answer: Send your developer eight things: what the business does and for whom, the one goal of the website or app, the pages or screens you need, the features (booking, payments, logins), two or three examples you like, the content and photos you already have, your domain and hosting status, and your deadline. A clear brief gets you an accurate quote and fewer surprises.
Practical Takeaway
An effective project brief defines eight foundational requirements: business model and target audience, the single primary conversion objective, complete page/screen inventory, required third-party integrations, design inspirations with commentary, available text/photo assets, current domain/hosting infrastructure, and realistic delivery milestones. A comprehensive brief prevents scope creep and enables apples-to-apples quotation comparisons.
Why the brief matters
Two developers quoting on "a website for my clinic" may be pricing completely different projects. A short, clear brief means quotes you can compare, a timeline you can trust, and far fewer surprises halfway through.
The eight things to include
- Your business: what you do, for whom, and where.
- The goal: calls, bookings, sales, sign-ups or credibility. Pick the main one.
- Pages or screens: for example home, services, about, contact.
- Features: booking, payments, logins, admin panel, multiple languages.
- Examples: two or three sites or apps you like, and what you like about each.
- Content: text, photos, logo and videos you already have, and what is missing.
- Domain and hosting: whether you own a domain, and where any current site is hosted.
- Deadline and decision-maker: when you need it, and who approves the work.
A copy-paste template
Business: [name], [what you do], [city or areas served] Goal: [main thing visitors should do] Pages or screens: [list] Features: [booking / payments / logins / languages] Examples I like: [links + why] Content ready: [text / photos / logo] Domain and hosting: [own a domain? current host?] Deadline: [date] Decision-maker: [name]
Questions to ask the developer
- Will I own the domain, hosting accounts and code?
- What exactly is included, and what costs extra later?
- How will I update content after launch?
- Can I see a sample or a design before paying the full amount?
- What happens if something breaks after launch?
Red flags
- No written scope or timeline.
- Guaranteed first-page Google rankings.
- Accounts registered only in the developer's name.
- No way to see work in progress.
| Brief Section | Information to Provide | Direct Impact on Quotation & Timeline |
|---|---|---|
| Core Value Proposition | Business niche, target audience, and geographic service region | Determines architectural complexity, tone, and page layout hierarchy |
| Primary Conversion Goal | WhatsApp enquiry, booking submission, direct phone call, or checkout | Dictates wireframing, CTA button placement, and analytics tracking |
| Screen & Page Inventory | Required URLs (Home, Services, Case Studies, Contact, Legal) | Directly controls development hours, milestone sizing, and quote accuracy |
| Technical Integrations | Payment gateways, user authentication, CRM, or appointment calendars | Determines backend API requirements, database schemas, and external fees |
| Content & Media Assets | High-res photography, logo vectors, copy drafts, or service lists | Prevents multi-week launch bottlenecks caused by missing creative assets |
| Infrastructure Ownership | Domain registrar access, cloud hosting, Apple/Google developer accounts | Ensures clear intellectual property handover and eliminates vendor lock-in |