SaaS messaging document

Keep this reference compact enough to use when writing. Link to restricted source records rather than copying sensitive research material. The example is fictional.

Scope

• Owner, version, and date:
• Content or campaign this supports:
• Primary audience and buying situation:
• Secondary roles and relevant concerns:
• Next action:
• Positioning brief reference:

Core explanation

• What the product helps someone accomplish:
• How it helps:
• Conditions needed to understand the promise:
• One-sentence explanation:
• Category or familiar frame of reference:
• Wording that would imply unsupported scope:

Fictional explanation: “Investigate recurring API test failures with relevant test context in one view.” Compatibility and setup terms still need explanation. This wording requires verification against a real product before use.

Message hierarchy

Claim ledger

Do not turn a paraphrase into a quotation or a product demonstration into a quantified result. Use customer evidence only within its agreed scope.

Questions and objections

Format briefs

Copy for a launch page, email, demo, sales conversation, or another format.

• Format and audience:
• Reader's starting knowledge:
• Question to answer first:
• Main explanation:
• Relevant supporting point and proof:
• Limits that must remain visible:
• Next action:
• Draft wording:

Comprehension review

• What readers believe the product does:
• Whom they believe it serves:
• Expected next-step experience:
• Misunderstandings affecting fit or action:
• Preferences, recorded separately:
• Specific revision or test:
• Owner and review condition:

Change log