Name the client and the headline result, and Juma writes a full customer case study: the challenge, the solution, a before-and-after results table, and attributed pull quotes, ready to publish.
Name the client, the product they adopted, and the headline result, and Juma researches the brand's site, positioning, and market before drafting the customer case study. The Flow structures the story the way buyers read it: an About section, the challenge with the symptoms that led to it, why the team chose the product, a phased solution, a before-and-after results table, and pull quotes attributed to named roles. It comes back as a branded document and a PDF, ready to publish on the site or send to the client for sign-off. More than 400 marketing teams use Juma to turn a rough brief and a few numbers into finished assets, and the customer case study is the proof asset that usually stalls for weeks waiting on someone to write it.
Real customer words carry more weight than a marketer's paraphrase, so build the case study straight from the interview. Paste the transcript and Juma pulls the strongest lines as attributed pull quotes, then uses what the customer actually said to shape the challenge, the turning point, and the results. Instead of guessing which moments mattered, the story stays anchored in the customer's own account of what changed. The team gets a full case study where every quote is verbatim from the call, placed next to the result it backs up. Confirm the final quotes with the client before publishing.
Here's the transcript from our call with Figma's design lead. Rewrite the case study around their own words: pull the strongest lines as quotes, and let what they said shape the challenge and the results.
Not every stakeholder reads a full case study, so give the sales team a version that fits on one slide. The one-page results snapshot keeps the client logo, one line of context, a before-and-after table, and the two or three numbers that moved, and drops everything else. It's the asset an account executive pastes into a deck or sends ahead of a call, where a three-page narrative would never get read. Juma builds it from the same facts as the long version, so the numbers stay consistent across both. Ask for it sized for a single page or a single slide.
Turn the Figma case study into a one-page results snapshot: the client logo, one line of context, a before-and-after table, and the three numbers that moved. Size it for a single slide we can drop into a deck.
Case studies often stall because the final numbers aren't confirmed yet, so write it with the rough ones and mark what's still open. Give Juma the approximate figures the team has, and it writes the results section with clear ranges, labels anything estimated, and lists exactly which numbers the client needs to verify before the study goes live. The draft is complete enough to send for review, and the open figures sit in one place instead of buried in the copy. When the confirmed numbers come back, drop them in and the ranges become hard results. Nothing gets published more precise than the data supports.
We only have rough numbers for Figma so far: roughly 30% faster shipping and about half the review rounds. Write the case study with clear ranges, label anything estimated, and flag which figures we need the client to confirm.
One approved case study can feed a week of content, so turn it into the formats each channel needs. From the finished study, Juma writes a one-page sales sheet for the account team, a LinkedIn post in the founder's voice, and a few short social posts built around the best quote and the headline stat. Every version pulls from the same approved facts, so the numbers and the quotes stay identical wherever they appear. The team publishes across the site, the sales deck, and social without rewriting the story four times. Keep each version in the client's project so nothing goes out off-message.
Repurpose the Figma case study: a one-page sales sheet for the account team, a LinkedIn post from our founder, and three short social posts built around the best quote and the headline stat.
A Juma Project is a shared space where the team keeps everything Juma needs to write for a client. Build one project per client, add these items once, and every case study comes out in the right format and the right voice without re-briefing. The more the team adds over time, the less each new case study needs explained from scratch.
Case Study Template
The structure the team's case studies follow: section order, length, and where the quotes and the results table sit. With this in the project, every case study matches the format the client and the site already use instead of Juma's default layout.
Brand Voice Guide
How the client sounds across channels: tone, vocabulary, and the words to avoid. Every draft, from the About section to the pull quotes, comes out in the right voice from the first pass.
Results & Metrics
The confirmed numbers behind the win: before-and-after figures, the time period, and where each figure came from. Juma builds the results table from real data and sources each claim, so nothing in the study is invented.
Customer Quotes & Interviews
Approved testimonials, interview transcripts, and any quotes the client has already signed off on. Juma places verbatim quotes next to the results they support instead of drafting new ones the client still has to approve.
Add a short description to each knowledge item in the project's info field so Juma knows what each file is and when to use it. For example:
A polished customer case study usually takes a marketer four to eight hours across drafting, chasing quotes, and formatting, and often waits weeks on a busy calendar. Juma returns a full first draft in a few minutes: challenge, solution, results table, and pull quotes, structured and ready for the team to review and send to the client.
The saving compounds because the structure stays identical from one case study to the next, so a story that used to sit half-written in a doc actually ships. Strategy, taste, and judgment stay human: the team edits the narrative, confirms the numbers, and gets the client's sign-off before anything goes live. Juma handles the blank-page problem, not the final call.
The case study includes an About section, the challenge with the symptoms that led to it, why the customer chose the product, a phased solution, a before-and-after results table, attributed pull quotes, and a short What's Next. It comes back as a branded document and a PDF, ready to publish or share.
Every number in the results table is tied to a source, and the pull quotes are attributed to named roles rather than floated anonymously. When the team hands over a real metric, like cycle time down 30% or review rounds down 62%, it anchors the results section. When a figure is still an estimate, Juma labels it so nothing reads as more precise than the data supports.
That's enough to start. Give Juma the approximate figures and it writes the results with clear ranges, labels anything estimated, and lists which numbers the client still needs to confirm. The draft is complete enough to review, and nothing is presented as more precise than the data supports.
This is what usually keeps a case study from shipping: the story is ready but two figures are still pending. The Flow lets the team draft now and lock the numbers later. When the confirmed data comes back, drop it in and the ranges become hard results, with the flagged list showing exactly what changed.
Yes. Add the team's case study template and brand voice guide to the client's Juma project, and every study follows that structure and tone instead of a default layout. Upload a past case study as a reference and Juma matches its section order, length, and level of detail.
This matters most for agencies producing case studies across many clients, where a consistent format is part of the deliverable. One Project per client keeps each brand's template and voice separate, and unlimited seats on every plan mean the whole team can run the Flow without a per-user charge. Juma remembers the format so no one rebuilds it for each new win.
Juma handles the first draft, the structure, and the formatting; the team owns the story. It researches the brand, organizes the numbers into a results table, and drafts quotes in the customer's voice, then hands the team a document to shape. Strategy, taste, and judgment stay human, and human review sits on every case study before it's published.
The difference is where the hours go. Instead of spending them on the blank page and the formatting, the team spends them on the parts that need judgment: which result to lead with, which quote lands, and what the client is comfortable putting their name to. Juma delivers a finished asset, not a chat response, so the starting point is a draft to edit rather than an outline to fill in.
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
.webp){kind=icon}
