From the Lab

So What?

Changelog to customer copy, made easier.

grok-botproduct-communicationtested-prompts
$ cat problem.md

Shipped features, explained for customers

A technical release note can explain exactly what engineering changed and still leave customers wondering whether it affects them.

So What? helps the person writing that explanation: a product manager, engineering lead, founder, or customer-facing lead at a technical B2B team.

$ cat how-it-works.md

Bring a release note. Leave with a draft.

Paste a ticket, release note, or rough announcement. So What? drafts the customer version, covering who's affected, what changes for them, what's available where, and what (if anything) they need to do.

It keeps limits and required actions visible instead of burying them, and won't invent benefits that aren't there. If nothing customer-facing actually changed, it'll tell you that instead of padding a draft.

When an important fact is missing, it gives you a partial draft from what is known, flags what's open, and asks the question that would change the message. You still review and send.

$ cat try-it.md

Try So What?

Open the shared template in Grok Bot and add your own copy. It runs in Grok Bot; the example below is here to explore before you try it.

Bring a release note or rough update you're allowed to share. Check the draft against your product's actual availability and requirements before sending it.

Read why I built it, or tell me what you tried and what you still had to fix.

THE RECEIPTS

A rollout with limits

Synthetic example. Meridian Vault is a made-up product. This shortened example illustrates the behavior being tested; it is not a transcript of a customer interaction.

The release note

Added directory provisioning for Enterprise workspaces in the United States and Canada starting October 6. Business and Starter plans and other regions aren't included. An administrator must configure the identity-provider endpoint and bearer token under Settings → Identity → Directory provisioning.

An illustrative customer draft

If your Meridian Vault workspace is on the Enterprise plan in the United States or Canada, you can set up directory provisioning starting October 6. Your administrator needs to configure the identity-provider endpoint and bearer token in Settings → Identity → Directory provisioning. This rollout doesn't include Business or Starter workspaces, or workspaces in other regions.

The plan, location, date, and setup requirement stay visible because they change who can use the feature and what they need to do.

Five initial cases

The first test set covered:

  • Implementation details with no customer context.
  • A feature restricted by plan and region.
  • A performance capability without measured results.
  • A migration with a deadline and required customer action.
  • An internal refactor with no customer effect.

The saved test results recorded a pass for all five. A separate check with sparse public release notes led to a change: when information is missing, return a partial draft and a concrete next step alongside the question.

These are early tests of a v0 bot. They don't establish that it beats another writing tool, and the competitor comparison hasn't been run. I'm looking for feedback on where it helps and what people still have to fix.

← Back to the Lab