Three docs, one paste: why launch week needs a different tool

The week a feature ships, a PM usually writes three documents: a battle card for sales, a brief for marketing, and a changelog for customers. Each one starts from the same source — the Jira ticket, the Slack thread, the decision doc — and each one re-reads that source with a different head on.

The head on the changelog reader is *"what do I do now?"*. The head on the battle card reader is *"what do I say when the customer asks?"*. The head on the marketing brief is *"what's the story?"*.

If you write all three by hand, you pay the context-switching tax three times. If you write them from a template, you get a template. Supabrief does one thing: one paste, three audiences, all in the same voice.

The three-document cut is deliberate. A launch kit that promises "everything" falls apart — you end up with a 14-page document no one reads. Three docs is the least you can ship. Everything else (tweet, internal Slack, FAQ) is a derivative of one of the three.

The rule: if it's not a battle card, a marketing brief, or a changelog, it's a derivative. Draft the three first. Derive the rest.