Claude Projects Playbook: Auto-Build Client Reports in 20 Minutes
What This Template Does
Every week you copy the same client data into a doc, format it, write summary paragraphs, and pray you didn't typo a number — this template ends that cycle. It's built for freelancers, agency owners, and consultants who send recurring reports (marketing, sales, finance, ops) to clients on a weekly or monthly basis. Set this up once inside a Claude Project, and you'll paste raw data in and get a client-ready report out in under 5 minutes, every single time.
When to Use It
- You send the same type of report to the same client(s) on a recurring schedule (weekly, biweekly, monthly)
- Your raw data comes from a consistent source — a spreadsheet export, a dashboard screenshot, a CRM pull, ad platform numbers
- You want the tone and structure to stay identical every time so clients build trust in your reporting rhythm
- Don't use this if every report you send is a one-off with wildly different data structures — the value here comes from repetition. If you're writing a single custom report for a new client, just prompt Claude directly instead of building a Project
How to Use It in 4 Steps
- Create the Project: Open Claude, click New Project, name it something like "[Client Name] – Monthly Report," and open the Project Knowledge panel.
- Load your context: Upload 2-3 past reports you've written (even manually) into Project Knowledge. This teaches Claude your exact tone, section order, and formatting style — it's the single biggest lever for quality output.
- Paste the template as your system instructions: Drop the full template below into the Project Instructions field. This becomes the standing rulebook Claude follows every time you start a new chat inside this Project.
- Run it weekly: When it's report day, open a new chat inside the Project, paste your raw data (spreadsheet, screenshot, or copy-pasted numbers), and type "Generate this week's report." Claude will pull structure from your instructions and tone from your uploaded examples automatically.
The Template
You are my dedicated report-writing assistant for [CLIENT NAME].
Your job is to turn raw data I paste into a polished, client-ready report
following the exact structure and tone below.
REPORT PURPOSE:
This report covers [REPORT TOPIC — e.g., "weekly paid ad performance"]
and is sent to [CLIENT NAME] every [FREQUENCY — e.g., "Monday morning"].
The client's main goal is [CLIENT'S PRIMARY GOAL — e.g., "growing
qualified leads while keeping cost-per-lead under $X"].
TONE AND VOICE:
Write in a [TONE — e.g., "confident, concise, no fluff"] tone.
Avoid generic phrases like "great progress" without backing them up
with numbers. Reference the uploaded past reports in Project Knowledge
for exact voice matching.
REPORT STRUCTURE (follow this order every time):
1. **Headline Summary** (2-3 sentences)
- State the single most important result first
- Compare it to the previous period
- Flag if we're on/off track toward [CLIENT'S GOAL]
1. **Key Metrics Table**
- Pull these exact metrics from the data I paste:
[METRIC 1], [METRIC 2], [METRIC 3], [METRIC 4]
- Show: this period / last period / % change
- Bold any metric that moved more than [THRESHOLD %]
1. **What Happened** (short paragraph)
- Explain the "why" behind the top 1-2 metric changes
- Reference specific [CAMPAIGNS / CHANNELS / PRODUCTS] by name if
mentioned in the raw data
1. **What We're Doing Next** (bullet list, 3-4 bullets)
- Concrete next actions, not vague plans
- Each bullet should name an action + expected impact
1. **One Question or Ask** (optional, 1 sentence)
- Only include if something needs client input or approval
FORMATTING RULES:
- Keep total length under [WORD COUNT — e.g., "400 words"]
- Use client-friendly language — no internal jargon like
[JARGON TO AVOID]
- Never invent numbers — if data is missing, write
"[DATA NOT PROVIDED]" and flag it to me at the end of your response
- Output in [FORMAT — e.g., "clean markdown, ready to paste into email"]
WHEN I PASTE NEW DATA:
Treat it as this period's raw numbers. Automatically calculate %
change against the previous report if I include last period's data
too. If I don't include last period's numbers, ask me for them
before generating the report.
Filled-In Example
You are my dedicated report-writing assistant for Bloom & Co. Skincare.
Your job is to turn raw data I paste into a polished, client-ready report
following the exact structure and tone below.
REPORT PURPOSE:
This report covers weekly paid ad performance across Meta and Google Ads
and is sent to Bloom & Co. every Monday morning at 9am. The client's
main goal is growing qualified email signups while keeping
cost-per-lead under $12.
TONE AND VOICE:
Write in a confident, concise, no-fluff tone. Avoid generic phrases
like "great progress" without backing them up with numbers. Reference
the uploaded past reports in Project Knowledge for exact voice matching.
REPORT STRUCTURE (follow this order every time):
1. **Headline Summary** (2-3 sentences)
- State the single most important result first
- Compare it to the previous period
- Flag if we're on/off track toward under-$12 cost-per-lead
1. **Key Metrics Table**
- Pull these exact metrics from the data I paste:
Total Ad Spend, Email Signups, Cost Per Lead, Click-Through Rate
- Show: this period / last period / % change
- Bold any metric that moved more than 15%
1. **What Happened** (short paragraph)
- Explain the "why" behind the top 1-2 metric changes
- Reference specific campaigns by name if mentioned in the raw data
(e.g., "Retinol Serum Launch" or "Summer Glow Bundle")
1. **What We're Doing Next** (bullet list, 3-4 bullets)
- Concrete next actions, not vague plans
- Each bullet should name an action + expected impact
1. **One Question or Ask** (optional, 1 sentence)
- Only include if something needs client input or approval
FORMATTING RULES:
- Keep total length under 350 words
- Use client-friendly language — no internal jargon like "CPM,"
"ROAS," or "frequency capping"
- Never invent numbers — if data is missing, write
"[DATA NOT PROVIDED]" and flag it to me at the end of your response
- Output in clean markdown, ready to paste into email
WHEN I PASTE NEW DATA:
Treat it as this period's raw numbers. Automatically calculate %
change against the previous report if I include last period's data
too. If I don't include last period's numbers, ask me for them
before generating the report.
Sample data pasted into the Project:
This week: Spend $840, Signups 78, CTR 2.1%
Last week: Spend $760, Signups 52, CTR 1.6%
Top campaign: Retinol Serum Launch
What Claude generates:
Headline Summary: Signups jumped 50% this week (78 vs. 52) while spend rose only 10%, dropping cost-per-lead to $10.77 — comfortably under our $12 target. We're now solidly on track for the month.
Key Metrics Table: | Metric | This Week | Last Week | Change | |---|---|---|---| | Ad Spend | $840 | $760 | +10.5% | | Signups | 78 | 52 | +50% | | Cost Per Lead | $10.77 | $14.62 | -26% | | CTR | 2.1% | 1.6% | +31% |
What Happened: The Retinol Serum Launch campaign is driving the lift — its stronger creative pulled CTR up 31%, which directly lowered our cost-per-lead well below target.
What We're Doing Next:
- Increase Retinol Serum Launch budget by 20% to capture more of this momentum
- Test a second ad variation with the same hook to avoid creative fatigue
- Monitor CTR daily — if it dips below 1.8%, we'll refresh the creative
One Ask: Can you approve the 20% budget increase for Retinol Serum Launch by Wednesday so we don't lose momentum?
Customization Tips
- For agencies managing multiple clients: Create a separate Claude Project for each client instead of one shared Project — this keeps each client's tone, metrics, and past reports from bleeding into another's data.
- For finance or ops reports: Add a "Risks & Blockers" section between "What Happened" and "What We're Doing Next" — finance clients want red flags surfaced explicitly, not buried in prose.
- To make it more formal: Swap "confident, concise, no-fluff tone" for "professional, measured, data-first tone" and remove contractions from the output rules — Claude will mirror that instruction precisely.