Client reporting eats a particular kind of afternoon. The numbers live in four tools that don't agree, half the context is in an email thread, and the actual writing is the last twenty minutes of a three-hour job.

Strawberry works in the browser, so it can go into the project tool, the analytics account, and the ad platform you already have open, line up what they're each measuring, and bring back something you can edit rather than assemble.

Start from the report you already send

You almost certainly have a format that works. Rather than describing it from scratch, point your companion at a previous report you were happy with. It picks up the structure, the depth, the tone, the field definitions, and where it ends up.

Then agree the client, the period, and what this particular report is for. A weekly snapshot for live paid media and a quarterly strategic review are different documents, and knowing which you're writing changes what belongs in it.

Want to try it?

Ask your Strawberry companion: “Help me reconcile one client's project, analytics, advertising, and communication context into a reviewable performance report. Keep this client's accounts and data separate from every other account.”

Skill

Build one client’s marketing performance report

Build this client's report for the period, from our usual sources.

Reconcile before comparing anything

This is where client reports quietly go wrong. Two tools report the same campaign differently, and the difference isn't an error, it's a definition:

  • Date ranges that start on different days of the week.
  • Attribution windows that credit a conversion to different touches.
  • Currencies converted on different days, or not at all.
  • Metrics that share a name and count different things.

Those get lined up before any comparison is drawn, and where two sources genuinely disagree, you're told rather than handed a reconciled number that hides it. Missing or delayed data is flagged as missing, not quietly treated as zero.

Written for the client, not for the dashboard

A metric dump makes the client do the work. What they want is what changed, why it matters, and what happens next, in the language you'd use on a call.

So the report leads with the summary and keeps the detail underneath: progress against goals, work completed, performance with comparisons that are actually comparable, risks and decisions needed, and clearly owned next actions. Recommendations stay visibly separate from results, and the strategic call stays yours.

One client at a time, deliberately

Each client's accounts, evidence, calculations, and output stay strictly separate. No client is ever used as an unstated benchmark for another, and a cross-client roll-up only happens where you have permission to compare those accounts.

Build one report first and correct it before the process goes near the rest of the book. Once it's right, it can be saved per client with that client's sources, definitions, format, and destination, and prepared on a cadence that matches the work.

Nothing gets sent to a client, and nothing gets written back to their systems, without your approval.

Run an AI-native ops teamStatus updates, open commitments, and the coordination around the reporting. Your AI analyst for every numberGo deeper on reconciling definitions and getting a defensible number.
Official Strawberry skill
Copy skill file Download skill file
name
build-client-progress-report-project-tools
description
Build a reviewable client report from approved project, account, analytics, and communication context.

Build a client progress report from your project tools

Context, setup, and planning

  1. Identify the client, reporting period, cadence, audience, and decision the report should support.
  2. Offer to learn the reporting process from the user, inspect an approved prior report, or combine both. A prior report can reveal the expected format, depth, tone, field definitions, and destination without making the user repeat them.
  3. Learn which approved sources are useful. Project tools, analytics and advertising accounts, CRM records, shared documents, meeting notes, and email can help when available, but they are not prerequisites.
  4. Keep every client's accounts, calculations, evidence, and output strictly separated.
  5. For a new reporting process, build one client's report first so the user can correct it before applying the process across the book.
  6. Present a concise plan before gathering substantial data. Confirm the sources, comparisons, and output shape, such as a document, deck, dashboard, email summary, or another format the user already prefers.

Reconcile the evidence

  1. Pull independent sources in parallel when that saves time, with a clear and separate task for each source so work does not overlap.
  2. Align date ranges, currencies, attribution windows, and metric definitions before comparing sources or periods.
  3. Preserve source links and state where each important figure came from.
  4. Flag missing, delayed, or conflicting data rather than forcing the numbers to reconcile.
  5. Compare performance only where the underlying definitions are compatible.
  6. Use plain client language. Lead with what changed, why it matters, and what should happen next rather than presenting a metric dump.

Draft the report

Include only sections useful for this client:

  • concise executive summary;
  • progress against goals and KPIs;
  • completed work and important changes;
  • performance with relevant comparisons;
  • risks, blockers, or decisions needed;
  • recommendations and clearly owned next actions;
  • source notes and unresolved data issues.

Keep recommendations distinguishable from observed results. Match the accepted client voice and presentation style without inventing a conclusion the evidence does not support. Draft the highlights and useful options, but leave the strategic decision to the user.

Scale carefully

  1. Let the user review the first report before producing other client reports.
  2. Run the accepted process separately against each client's own connected accounts. Reports may be prepared in parallel only while maintaining strict client and account separation.
  3. Match cadence and depth to the work. Useful examples include a weekly snapshot for active paid media, a fuller monthly report for a retainer, or a quarterly strategic report for SEO and content.
  4. A cross-client roll-up may highlight overspend, sudden drops, or accounts needing attention, but use it only when the user has permission to compare those accounts.
  5. After the report has worked several times, offer to save one reporting skill per client. Preserve its accepted sources, definitions, output format, destination, review behavior, and per-client boundaries. When useful, prepare it on the agreed Routine.
  6. Never send the report or update client systems without approval.

Suggested outcome

Produce a clean client report in the accepted format. Keep sources, definitions, and uncertainty visible, and explain what changed, why it matters, and which decisions or actions follow.