The problem this solves
Every team is sitting on customer wins that never became assets. The story exists - in a thread, a call note, a renewal conversation - but turning it into a one-pager means someone writing it up, someone checking the claims, someone producing a visual so it does not look like a memo, and someone formatting the result. Four small jobs, none urgent, so the win stays folklore while sales keeps asking for proof points and the strongest evidence the company owns goes unused.
When one-pagers do get made, two failure modes dominate. The first is inflation: results drift upward in the retelling, quotes get polished into marketing language, and the asset stops being credible to the exact skeptical buyer it exists for. The second is visual poverty: a wall of text with a logo, indistinguishable from an internal document, that nobody forwards. The rare one-pager that works keeps the customer's actual words and looks like something worth handing to a prospect.
This playbook takes the win as described in your thread and produces the finished asset: the story structured as challenge, approach, and results, the customer's language preserved rather than improved, a branded hero visual generated for the page, and the whole thing delivered ready to use. The discipline about words and the quality of the visual are the same feature - both exist to make the asset believable.
How the mission runs
- Extract the story from the thread. The agent works from the win as you describe it: the customer, the situation, what was done, and what happened. It structures this into challenge, approach, and results, flagging any gap where the story needs a fact you have not provided rather than inventing one to fill it.
- Ground the claims. Web Research adds verifiable context - the customer's industry, scale, and public footprint - so the framing is accurate, while every result claim stays exactly as sourced from your thread. Anything unverifiable is flagged for your confirmation, because a case study's value collapses at the first overstated number.
- Write in their words. The one-pager is drafted with the customer's language carried through: their phrasing for the problem, their description of the outcome, quotes preserved verbatim where you provided them. Marketing polish is applied to structure and flow only, since the customer's own words are the asset's entire authority.
- Generate the branded hero visual. Image Generation produces the hero image in your palette and visual language, themed to the story. Its job is to make the page unmistakably a designed asset - something a rep forwards and a prospect keeps - while staying appropriate for a document the customer may also see.
- Deliver the page in Google Docs. The finished one-pager lands in Google Docs with the hero visual linked in place: challenge, approach, results, and quote, formatted for both sending and printing. Review it, clear it with the customer if your agreement requires that, and it is ready for the sales floor.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A finished case-study one-pager in Google Docs: the win structured as challenge, approach, and results, the customer's own language preserved throughout, verified contextual framing, and a branded hero visual generated in your palette and linked in place. Result claims trace to what you provided, flagged wherever confirmation is needed, so the asset is ready for customer sign-off and then for every deal it belongs in.
Make it yours
- Run it against three or four wins in one batch to seed a proof-point library, holding the visual style constant so the set reads as a family of assets.
- Ask for a short social cut alongside the one-pager - the same story compressed to a post-length version - so the win works both channels from one mission.
- Produce an anonymized variant in the same run for prospects in competitive situations where the customer's name stays confidential until later in the deal.
Frequently asked questions
Will it exaggerate the results?
No, and the guardrails are structural: result claims come only from what you provided, quotes stay verbatim, and anything the agent cannot verify is flagged for your confirmation instead of smoothed over. A case study's power is credibility with skeptical readers, and inflation is the one edit that destroys it.
What does the customer need to approve?
That depends on your agreement with them, and the deliverable is built for that pass: their words are preserved and claims are traceable, so customer review is a quick confirmation rather than a negotiation. Most teams send the finished Doc for sign-off before the asset enters circulation.
How does the visual stay on-brand?
The hero image is generated from the palette and visual direction you specify, and the first one-pager calibrates the style. If you batch several wins, the style holds across the set, which is what turns individual assets into a recognizable proof-point library rather than a folder of one-offs.