The Claude Project Brief Template That Turns a 15-Minute Call Into a 1-Page Deliverable

The single highest-leverage move for any solo consultant, agency owner, or freelancer is writing the project brief BEFORE the work starts. Most don't. They take notes during the call, start the work on vibes, and discover at week 3 that what they're building isn't what the client thought they were buying.

The reason most operators skip the brief is friction. Writing one feels like overhead. With Claude and a tuned project-brief skill, the friction collapses to about 90 seconds of model time + 5-10 minutes of editing. Below the friction threshold where it stops getting skipped.

This article is the exact template, the Claude skill that generates it, and the operator workflow that makes briefs a 24-hour deliverable instead of a 3-day chore.

The Six-Section Brief

The brief that works for 90% of solo-operator engagements has six sections, fits on one page, and gets to "good enough" in the first draft:

1. Goal. What outcome are we producing? One sentence. Specific, measurable where possible. "Launch a custom-trained AI chatbot on Acme Dental's website that captures after-hours leads" beats "improve Acme Dental's website."

2. Scope. What's specifically included. 3-7 numbered items. Each item is a concrete deliverable, not a vague capability.

3. Out of Scope. What's specifically NOT included. This is the section most operators skip. It's the scope-creep firewall. List 3-5 things explicitly excluded so they can't surprise you later.

4. Deliverables. The exact artifacts the client receives. "A working chatbot installed at /chat on acme-dental.com, plus a monthly performance report PDF." Specific, countable.

5. Timeline. Start date, milestones, finish date. Two or three milestones is enough.

6. Owner. Who owns what. Your responsibilities. Their responsibilities. Decision-maker on their side.

That's it. One page. Six sections. Most briefs run 350-500 words.

The Capture Workflow

The trick is making the brief writeable in 5-10 minutes after the discovery call. The workflow:

Step 1 — Record the discovery call. Fathom, Otter, Granola, Apple Voice Memos. Tell the client you're recording. Most won't care.

Step 2 — Transcribe. Most recording tools transcribe automatically. If yours doesn't, paste the audio into OpenAI Whisper or ElevenLabs Scribe.

Step 3 — Paste into Claude with the Project Brief skill. The skill does the structure work.

Step 4 — Edit for 5-10 minutes. Fix misheard names, confirm dollar amounts, tighten language.

Step 5 — Send within 24 hours of the call. "Here's what I heard. Confirm and I'll start."

The 24-hour turnaround signals operator-tier execution. Clients accept faster than for slower turnarounds.

The Claude Project Brief Skill

Save this as a Claude Project Custom Instruction or a Skill file:

You are a Senior Engagement Manager with 15 years of experience writing project briefs for service businesses. Your job is to convert a discovery-call transcript into a 1-page client-ready project brief.

Output structure (exactly six sections, in this order):

Goal: One sentence describing the outcome.

Scope: 3-7 numbered concrete deliverables.

Out of Scope: 3-5 specifically-excluded items.

Deliverables: The exact artifacts produced (with file types and locations where applicable).

Timeline: Start date, 2-3 milestones, finish date.

Owner: Operator responsibilities + Client responsibilities + Decision-maker name.

Style rules:

• Imperative voice ("Install the chatbot" not "We will install the chatbot")
• Specific over general (name the URL, the tool, the date)
• No marketing fluff
• Total length under 500 words

If the transcript is missing information for any section, mark it [TBD: ] and ask one consolidated clarifying question at the end. Do not invent details.

Paste the transcript after this skill prompt. Output is a structured brief in 60-90 seconds of Claude time.

A Real Example

Discovery call transcript (excerpt):

"...so we need the chatbot live by the end of June. It should answer the most common questions — hours, services, insurance. Don't need it to handle appointment booking directly, we'll keep that on the calendar tool. Total budget is around $800 setup plus monthly. Dr. Patel is the decision-maker. I'm the day-to-day contact, my name's Sarah..."

Claude output:

Goal: Install a custom-trained AI chatbot on Acme Dental's website to capture after-hours leads and answer common patient questions by end of June 2026.

Scope:

1. Install Claude-powered chatbot on www.acmedental.com (widget bottom-right)
2. Knowledge base covering: hours, services, insurance plans, location, common FAQs
3. Lead-capture flow for low-confidence questions (name + phone collection)
4. Time-aware after-hours messaging
5. Monthly performance report email to Sarah

Out of Scope:

1. Direct appointment booking (calendar tool handles this)
2. Patient portal integration
3. SMS or two-way text messaging
4. Custom design beyond brand color matching
5. SEO or website content updates

Deliverables:

• Live chatbot at acmedental.com (chat widget bottom-right)
• Knowledge base document (Notion link)
• Monthly performance report (PDF, emailed first Monday)

Timeline:

• Kickoff: Monday June 2
• Knowledge base draft: Friday June 13
• Install + test: Friday June 20
• Go live: Monday June 30

Owner:

• Operator (Cameron): all technical implementation, knowledge base draft, install, monthly reports
• Client (Sarah): review knowledge base draft, provide updates as services/hours change
• Decision-maker: Dr. Patel

Pricing: $499 setup + $99/month (per separate conversation — confirm in approval reply).

That's a complete brief. ~310 words. The client can sign off in one read.

The "Out of Scope" Section Is The Money

Most operators skip Out of Scope because it feels negative. It's the most important section.

Every project has implicit assumptions that aren't included. The client assumes appointment booking is included. The operator assumes it isn't. Without explicit Out of Scope, that assumption gap becomes a scope-creep argument at week 4.

The discipline: list 3-5 things that a reasonable person might assume are included but aren't. Examples:

• Custom branded design beyond color matching
• Integration with [specific tool the client uses]
• Training their internal team to update the system
• Monthly meetings (after the initial install)
• Modifications to their existing infrastructure

If the client wants any of those, the brief makes the conversation easy: "That's outside the original scope. Want to add it as a separate item at [price]?"

The Brief As Living Document

After sign-off, the brief becomes the project's reference document. Whenever questions come up ("Did we agree to do X?"), the brief is the answer.

Operators who treat the brief as a one-time deliverable lose this benefit. Operators who treat it as living (updated when scope changes are agreed) keep the firewall intact through project close.

A simple version-control approach: keep the brief in a shared doc (Google Docs, Notion). When scope changes, add an addendum at the bottom dated with the change. Original brief stays intact at the top.

The Compounding Benefit

Operators who write briefs for every engagement build a library of past briefs. Year 1: write every brief from scratch. Year 2: most briefs reuse 60-70% of patterns from past briefs (the same scope items, same out-of-scope items, same milestone structures).

By year 3, brief writing takes 5 minutes per engagement because the templates are mature. That compounding only happens for operators who started writing briefs in year 1.

The Cross-Sell

The Project Brief Generator is one of ten skills in Claude Skills for Operators ($7.99). The other nine cover the rest of the recurring solo-operator workflows: email triage, SOP builder, RFP responder, hiring filter, investor update, customer reply, vendor negotiation, weekly review, meeting notes.

Each skill is a markdown file. No subscription beyond Claude Pro. No Discord. No cohort.

The actionable next step: at your next discovery call, record it (with permission). Run the Project Brief skill on the transcript within 24 hours. Send the brief to the client. Watch how much faster they sign off compared to your usual proposal cadence.