Every freelance project starts the same way: the client sends a chaotic message, you reply with questions, they send more chaos back, and somewhere in that thread you lose track of what was actually agreed. A project brief fixes this. A project brief template fixes it every time, without you having to remember the structure.
Below: the full 10-section template as a copy-paste block, section-by-section guidance including what clients push back on, a table for adapting it per project type, and three filled-in examples.
The Master Template (Copy This)
PROJECT BRIEF: [project name]
Client: [name / company] Prepared by: [you] Date: [date]
1. PROJECT SUMMARY
[2-3 plain sentences: what is being built and why]
2. BUSINESS GOALS
[The measurable result this project must produce]
3. TARGET AUDIENCE
[Who this is for: demographics, technical level, primary device]
4. SCOPE OF WORK (DELIVERABLES)
- [deliverable]
- [deliverable]
- [deliverable]
5. OUT OF SCOPE
- [exclusion]
- [exclusion]
- [exclusion]
Anything not listed in section 4 is out of scope. Additions are
handled through a written change order with its own fee and timeline.
6. TIMELINE
[Phases, durations, and the client input each phase depends on]
7. BUDGET + PAYMENT TERMS
Total: $[X]
Schedule: [deposit % / milestone % / final %]
Revisions included: [N] rounds. Additional rounds: $[X]/hour.
Invoices due within [N] days.
8. TECHNICAL REQUIREMENTS
[Stack, hosting, integrations, who owns which accounts]
9. ACCEPTANCE CRITERIA
[Objective, testable definition of "done"]
10. SIGN-OFF
This brief defines the complete scope of the project. Both parties
confirm the scope, timeline, and payment terms below.
Client: ____________ Date: ______
Freelancer: ____________ Date: ______
Section-by-Section Guidance (With Negotiation Notes)
1. Project Summary
A two to three sentence description anyone could understand. No jargon.
Example: "A 5-page marketing website for an Istanbul-based legal firm specializing in startup law. The site must generate consultation bookings and establish credibility for enterprise clients."
Negotiation note: no pushback here, but vagueness in this section infects every other section. If you can't write these three sentences, the project isn't understood yet.
2. Business Goals
What result does this project need to deliver? Tie it to numbers when possible.
Example: "Generate at least 20 qualified consultation leads per month within 90 days of launch."
Negotiation note: clients sometimes resist committing to a number because they read it as a promise you're making. Clarify: the goal shapes design decisions, it is not a performance guarantee.
3. Target Audience
Who is this for? Demographics, technical level, and primary device.
Example: "Founders of Series A-B SaaS startups, 30-45 years old, technically fluent, primarily desktop during business hours."
4. Scope of Work (Deliverables)
List every deliverable. Specificity is your armor. Every line should be verifiable by a stranger.
- Homepage with hero + services overview
- 3 service detail pages
- About + team page
- Contact page with Calendly booking embed
- Mobile-responsive layouts for all pages
- Basic on-page SEO (meta titles, descriptions, schema.org markup)
- Favicon and Open Graph image
Negotiation note: clients want this list to stay loose ("we'll figure out the details as we go"). Loose deliverables are how a 5-page site becomes a 9-page site. Hold the line: details can change through change orders, not through vibes.
5. Out of Scope
Everything not listed in section 4, with the likely assumptions written out explicitly.
- Blog setup or ongoing content writing
- Logo design or brand identity (client has existing brand)
- E-commerce or payment processing
- Email marketing integration
- Post-launch maintenance beyond 14-day bug window
- Multilingual support
Negotiation note: this is the most pushed-on section ("why so negative?"). The reframe that works: this list is a budget guarantee. Nothing on it will ever appear on an invoice unannounced. For the full logic of exclusions, see the scope of work template guide.
6. Timeline
Phased breakdown with deadlines, including the client's obligations.
| Phase | Duration | Client input needed | |---|---|---| | Discovery + wireframes | Week 1 | Approval by day 7 | | Visual design (2 rounds) | Week 2-3 | Revisions within 48h | | Development + CMS setup | Week 4-5 | Content delivered by day 28 | | QA + launch | Week 6 | Final approval by day 42 |
Negotiation note: the third column is your protection against "why is this late?" conversations. Late content means a shifted timeline, and the signed brief already says so.
7. Budget + Payment Terms
Total, breakdown, and schedule. Never hide these.
- Total project fee: $6,500
- 40% deposit upon signing: $2,600
- 30% at design approval: $1,950
- 30% at launch: $1,950
- Additional revisions beyond 2 rounds: $100/hour
- Late payment after 14 days: 5% monthly interest
Negotiation note: expect pushback on the deposit and the revision cap. The deposit is non-negotiable (it filters non-serious clients). The revision cap can flex in exchange for something: more rounds, higher price.
8. Technical Requirements
Stack, hosting, integrations, credentials needed, and who owns which accounts.
- CMS: Sanity.io (client manages content post-launch)
- Hosting: Vercel (Pro plan, billed to client)
- Domain: client already owns the domain
- Analytics: Plausible
- Booking: Calendly embed
Negotiation note: "billed to client" lines matter. Hosting and SaaS subscriptions that quietly land on your card become permanent unpaid overhead.
9. Acceptance Criteria
What "done" looks like. Objective, testable.
- All pages render correctly on latest Chrome, Safari, Firefox, Edge
- Mobile performance score of 85+ on PageSpeed Insights
- Zero critical accessibility issues on WAVE
- CMS training session completed with client team
Negotiation note: without this section, "done" is a feeling, and the client's feeling arrives later than yours. Objective criteria end the project cleanly.
10. Signatures
Both parties sign and date. A brief without signatures is a draft, not a contract.
Adapting the Template Per Project Type
The skeleton holds; the emphasis shifts.
| Project type | Heaviest sections | Most common missing input | Watch out for | |---|---|---|---| | Website / marketing site | Scope, Timeline | Who writes the copy | Page count creep | | Branding / identity | Scope, Acceptance criteria | Decision-maker list | "One more concept" loops | | Mobile app | Technical, Acceptance criteria | Backend/API ownership | Platform scope (iOS AND Android?) | | Landing page | Business goals, Timeline | Traffic source and CTA | "Small" A/B variants | | No-code (Webflow/Framer) | Technical, Out of scope | Plan limits and billing owner | "You can edit it yourself" support creep |
Three Filled-In Examples
Example A: Logo + Brand Identity ($4,200, 4 weeks)
- Summary: Brand identity for a specialty coffee roaster launching in three cities. Needs logo, color system, and applied assets for packaging and signage.
- Out of scope: website, photography, print production, trademark filing.
- Deliverables: primary logo, secondary mark, color palette with hex + Pantone, type system, usage guide, packaging templates for 250g/500g bags, social avatar pack.
- Milestones: moodboard week 1, three concept directions week 2, refinement week 3, delivery week 4.
- Revision terms: two refinement rounds on the chosen direction. New directions after week 2 are new work.
Example B: Mobile App MVP ($18,000, 10 weeks)
- Summary: iOS + Android MVP for a habit-tracking app aimed at university students. One core loop: create habit, check in daily, see streak.
- Out of scope: Apple Watch, web app, social features, push notification campaigns, paid acquisition funnels.
- Deliverables: Figma design system, Flutter app with offline-first sync, Firebase backend, onboarding flow (3 screens), basic analytics.
- Milestones: design sprint weeks 1-2, core development weeks 3-7, beta testing week 8, store submission week 9, launch week 10.
- Acceptance criteria: app approved on both stores, core loop works offline, crash-free rate above 99% during beta week.
Example C: Webflow Marketing Site ($5,800, 5 weeks)
- Summary: 6-page Webflow site for a B2B logistics SaaS, replacing an outdated WordPress site. Marketing team must be able to edit all content without a developer.
- Out of scope: copywriting (client's marketing team provides final copy by day 14), blog migration beyond the 10 most recent posts, custom code beyond Webflow-native interactions, ongoing retainer support.
- Deliverables: 6 static pages, CMS collections for blog + case studies, 10 migrated posts, responsive breakpoints, Webflow Editor training call (60 min, recorded).
- Technical: Webflow CMS plan billed directly to client; client owns the workspace; DNS cutover handled together on a scheduled call.
- Acceptance criteria: marketing team publishes a test post unassisted during the training call.
Note what all three share: the exclusions name the exact things this client type tends to assume. That's not pessimism, that's how effective briefs are written.
Before You Fill It In
The template can't tell you what the client never said. Before writing, list what's missing from their message: budget, deadline, decision-maker, content ownership, platform. If more than two or three core slots are empty, you're not ready to fill the template, you're ready to ask better questions.
Try the free tool
This article walks through the problem; the free tool turns the answer into a copy-pasteable output in 30 seconds. No account, no signup. Paste the client's message and see which template sections you can't fill yet.
→ Use the Client Brief Checker
Want this across every project?
Briefance saves every brief, scope check, change order, and revision counter against the client and project. Free plan: 3 briefs/month.