Playbook Coming soon

Case studies, in the customer's own words

Start with an approved customer interview and the outcomes you're cleared to share. Paragraph turns it into a case study that leads with the customer's problem and their results. It also drafts the X post and the LinkedIn post to carry it, all for your review.

This Playbook is in development. It isn't available to run yet, and its scope may change before it launches. See the Changelog Playbook, which runs today.

Trusted by teams at

  • Coinbase
  • Farcaster
  • Stable
  • Base
  • Nodle

From a 45-minute call to a story the next customer recognizes

Paragraph keeps the customer's phrasing, leaves out the small talk, and opens with the problem rather than with your product.

Customer interview Northwind · 45 min call
  • We were rebuilding the same report every Monday. Four hours, every week.
  • Rollout took about two weeks across three regional teams.
  • [crosstalk] left out
  • In the first month we caught a billing error that would've cost more than the subscription.
  • Can you send me the invoice thing after this? left out
  • Now the report's just there. Monday morning, done.
Case study draft Waiting for your review

How Northwind got Monday mornings back

  • Opens with the four-hour weekly report, in the customer's words.

  • Covers the two-week rollout across three regional teams, and what made it stick.

  • Closes on the billing error caught in month one, with the quote that says it best.

Drafts for review Case study X post LinkedIn post

How it will work

Set it up once. After that, the drafts are waiting for you.

  1. 1

    Give it the interview. Upload the recording or transcript, and list the outcomes you're cleared to share. Anything you leave off stays out.

  2. 2

    Read the outline. Paragraph proposes the problem, the rollout, the result, and the quotes it plans to use, before it writes the full draft.

  3. 3

    Review the drafts. The case study, the X post, and the LinkedIn post open in the editor. Send the draft to the customer for their read before you approve.

  4. 4

    Approve it. The case study publishes to your site, and the social posts go out when you say so.

One story, told where your next customer is

The case study carries the full account. The X post and the LinkedIn post carry the result and the quote, each written for its feed.

X

@acme

Northwind was rebuilding the same report every Monday. Four hours, every week. Two weeks after rollout, it's just there when they open the laptop. In month one they caught a billing error worth more than the subscription. Full story:

acme.com/customers/northwind

LinkedIn

Acme · Company page

"We were rebuilding the same report every Monday. Four hours, every week." That's how Northwind's finance lead described the problem before rollout. Two weeks and three regional teams later, the Monday report builds itself. In the first month it surfaced a billing error that would have cost more than the subscription. We wrote up how the rollout went, what made it stick, and what they'd tell a team starting today:

acme.com/customers/northwind

Why teams will keep it running

Proof, in the customer's voice

A story told in the customer's own words does what a feature list can't. The next customer hears someone like them, not you.

Faster from call to published

The interview you already recorded becomes a draft the same day. Stories ship while the result is still fresh instead of sitting in a folder.

A library, not a one-off

Every story follows the same shape on your own domain. A reader, a prospect, or your sales team can find the one that matches them.

The customer tells the story. You decide what gets published.

See how approvals work

More Playbooks

Each one starts from something you already have, drafts the work, and waits for your approval.

Frequently asked questions

What people ask before they plan around the Customer stories Playbook.

Customer stories is in development and isn't available to run yet. Its scope may change before it launches. In the meantime, Paragraph's agent can already draft a post from a transcript you give it in chat, and the Changelog Playbook is live today.

An interview the customer has agreed to, as a recording, a transcript, or written answers, plus the outcomes you're cleared to share. The more of the customer's own phrasing you give it, the better the story reads.

It's designed not to. Outcomes stay as the customer stated them, quotes stay as said, and anything you haven't listed as shareable is left out. You check every number before it publishes.

Yes. Nothing publishes until you approve it. Send the draft to the customer, make their edits in the editor, and approve once they're happy.

No. Every draft waits for your approval before it publishes to your site or posts to a social account. That's how every Playbook works.

On your Paragraph site, at your own domain, alongside your other posts. Readers can subscribe by email or RSS, and every story is built to be found in search and by AI assistants.

Start with Paragraph today

Paragraph's agent already drafts, distributes, and waits for your approval. Start for free, and you'll see this Playbook in your catalog when it's ready.