Content Engine
One brief in, a publishable content pack out: a long-form article and matched social posts, edited in your voice.
A publishable content pack, from one brief
A ready-to-publish content pack from one brief — a long-form article plus matched social posts, edited in your voice.
For the operator publishing regularly, or meaning to. One brief in, a publishable pack out: a long-form article and matched social posts, edited against your own voice reference so it reads like you, not a content farm. Value-first copy; no engagement bait.
Open it up. See how it works.
A playbook is the way you work, made runnable, built from four ingredients. Tap through each one. The one marked yours is what makes the output specifically about your business.
What every run must deliver
Turn one content brief into a publishable pack: plan the angle, write the long-form article, derive the social posts from it, then run an editorial pass over the lot — everything in the owner's voice, consistent across channels, ready to schedule.
A ready-to-publish content pack from one brief — a long-form article plus matched social posts, edited in your voice.
Straight from the template's own definition.
Your inputs in, a finished output out
You never touch a prompt. YAMO orchestrates the plays in order; you provide the inputs and read the result.
The same template, on your data
Left: the seed run on sample data. Right: the exact same playbook run on your data.
→ A publishable pack, but in a sample voice on a sample topic. Useful to see the shape.
→ Your idea, argued your way, in your voice, shaped for the channels you actually publish on.
See a finished run
An unedited artifact from a seed run on sample inputs. Your runs use your inputs, your references, and your voice.
Example output — produced by a real run of this template on sample inputs. Sample inputs: brief = how small service businesses can build a 20-minute client report that actually gets read · channels = LinkedIn, X · audience = owners of small agencies and service businesses
Content pack — The 20-Minute Client Report That Actually Gets Read
Pack summary
- The one idea: Client reports get ignored when they're built to prove effort instead of answering three questions — is it working, what did you do, what's next. Structuring around those questions cuts report time to 20 minutes and gets the report actually read.
- Audience: Owners of small agencies and service businesses who send recurring client reports.
- In this pack: One article (with a step-by-step 20-minute build) and six social posts — three for LinkedIn, three for X — covering why long reports fail, the three-question structure, and the timed build itself.
Article
The 20-Minute Client Report That Actually Gets Read
Most client reports are built to show effort, not to answer questions. That's why they get skimmed at best — a client opens the email, sees a wall of charts and screenshots, and closes it. Not because the work was bad, but because the report never told them what they actually wanted to know.
You can fix this without cutting the work you report on. You just have to change what the report is organised around.
The three questions every client actually asks
Strip away the dashboard exports and the metric definitions, and every client wants the same three things answered:
- Is it working? Not "here are 14 metrics" — a direct answer.
- What did you do? Not a task log — the handful of things that mattered.
- What's next? Not a vague "continuing to optimise" — a specific next action.
Everything else in a typical report is noise the client has to wade through to find these three answers. Build the report around these questions instead of around the data you happen to have, and you don't need less information — you need a different structure for the same information.
The 20-minute build, step by step
Once you know what the report needs to say, building it is fast. Three chunks:
Pull the numbers (5 minutes). Grab the handful of metrics that answer "is it working?" — not every metric available, just the ones tied to what the client cares about. If you're reporting on ad spend, that's cost-per-result and the trend line, not eight platform-native charts.
Write the plain-English summary (10 minutes). This is the part most reports skip. Take the numbers and say, in one or two sentences, what they mean. Not "CTR was 2.1%, up from 1.8%" — instead, "Ads are performing better this month; you're paying less per lead than last month." The number supports the sentence; it doesn't replace it.
Flag the next action (5 minutes). One line: what you're doing next and why. "We're testing two new ad variations next month to bring cost-per-lead down further." This is what turns a report from a summary into a plan the client is still attached to.
That's the whole build. No design pass, no extra charts, no narrative flourishes — the time goes into judgment, not production.
Why brevity is a feature, not a shortcut
The instinct when a client questions value is to add more to the report — more charts, more detail, more proof of work. This backfires. A longer report doesn't read as more thorough; it reads as more work to get through, and clients respond by skimming or skipping it entirely.
A short report that clearly answers "is it working, what did you do, what's next" gets read start to finish. A comprehensive report that requires the client to hunt for the answer gets opened once and ignored the next month. If the goal is a report that actually gets read, cutting content is what accomplishes that — not a compromise you make to save time.
What to do once, so it's 20 minutes every time
The 20-minute build only stays 20 minutes if the structure is already decided. Set up the format once — a template with three headed sections (Is it working / What we did / What's next) and blank space to fill in — rather than deciding from scratch each month what to include.
Once the template exists, you're not making decisions about structure every reporting cycle. You're filling in three sections with information you already have on hand. That's what gets a report-writing task down from an hour of assembling charts and captions to 20 minutes of judgment calls.
Close: what "getting read" actually buys you
A report that gets read solves a problem before it becomes a conversation. Clients rarely cancel because results were genuinely bad — they cancel because they couldn't tell, month over month, whether they were getting anything for their money. A report that's actually read answers that question before the client has to ask it out loud in a "what am I paying for?" call.
That's the return on the 20 minutes: not a nicer-looking document, but one less reason for a client to start wondering if they should leave.
Social posts
Most client reports don't get read because they're built to show effort, not to answer questions. A wall of charts and screenshots looks thorough — and gets skipped.
The fix: organise around what clients actually want to know. Three questions. Is it working? What did you do? What's next?
Everything else is noise. Strip it out, and you can build a report that gets read start to finish in 20 minutes.
The instinct when a client questions value is to add more to the report — more charts, more detail, more proof of work.
This backfires. A longer report reads as more work to get through. Clients respond by skimming or ignoring it.
A short report that clearly answers the three questions gets read. A comprehensive report that requires hunting for answers gets opened once and abandoned.
If the goal is a report that gets read, cutting content is what accomplishes that.
Here's what a 20-minute client report looks like:
Pull the numbers (5 min) — just the metrics tied to what the client cares about.
Write the plain-English summary (10 min) — say what the numbers mean in one or two sentences.
Flag the next action (5 min) — one line on what comes next and why.
No design pass, no extra charts. The time goes into judgment, not production.
X
Most client reports get skipped because they answer the wrong questions. Clients want three things: Is it working? What did you do? What's next? Everything else is noise.
Organise around those three answers instead of your available data, and you don't need less information — you need a different structure.
The longer the report, the less it gets read. Not because it's thorough — because it looks like work. Cut the content, answer the question, get it read start to finish.
20-minute client report: pull the metrics that matter (5 min), write what they mean in plain English (10 min), flag the next action (5 min). No extra charts. No narrative flourishes. Judgment, not production.
Editor's notes
- Standardised UK spelling throughout the article and both X/LinkedIn posts that referenced "organize" and "optimize" — changed to "organise"/"optimise" per the account's UK English rule.
- Cut a hedge ("This usually backfires" → "This backfires") and a filler lead-in ("In practice, this breaks into three chunks" → "Three chunks") in the article for directness; no factual change.
- Checked all six posts against the article: every claim (three-question structure, 5/10/5-minute breakdown, no design pass) is supported by the article text. No terminology drift found.
- No rhetorical questions, banned phrases, or engagement bait in any piece. Each social post stands alone without requiring the article.
- Open items carried forward from the draft stage — the owner should confirm before publishing:
- The piece treats "report" as format-agnostic (email, PDF, or dashboard). Confirm this is intended, or the advice may need to name a format.
- The 20-minute figure is the ongoing time cost once a template exists, not the time to build the first one. If the brief meant the first-ever report, this needs reframing.
- No downloadable template is included — this is a teaching piece, not a template hand-off. Flag if a lead-gen version with an actual template is wanted instead.
The same run also materialised the article and social-posts sections above as separate artifacts (outputs/article.md, outputs/social-posts.md).
This is an unedited artifact from a seed run on sample inputs.
Common questions
No. This template runs on a fresh account: nothing to connect before your first run.
Each run asks for: content brief, channels, audience. Swap the content-voice.md reference for your own doc and the output adapts to your language and priorities.
The template is free to copy and no card is required to sign up. When it runs, you pay for exactly what the run used: LLM calls passed through at cost plus the platform operations, itemised on a receipt every run.
Yes. It copies into your account as an editable draft: change the plays, swap the references, set the schedule. Your data and your recipe stay private to your account, and when you publish it as your own service the price is yours to set.
Make this playbook yours.
Copy it into your account as an editable draft, plug in your data, and run it.