Chapter 1
Start with a product message brief
six-line product-message brief is the practical output of this chapter. Complete it in one focused work session so you can decide the buyer, urgent problem, desired outcome, mechanism, proof, and next step that anchor all content, without creating content before deciding what the product must be understood to do.
What you’ll get
- A completed six-line product-message brief ready for the next chapter.
- A documented decision about the buyer, urgent problem, desired outcome, mechanism, proof, and next step that anchor all content.
- A pass or fail signal: a teammate can create a relevant post without inventing a new promise.
- A first implementation move: Write the six lines using the customer’s language and keep them beside the product page.
Write the offer in six lines
Before producing content, complete:
- Buyer: who faces this problem now?
- Trigger: what happened that made it important?
- Problem: what are they trying to stop or improve?
- Outcome: what usable state will the product help create?
- Mechanism: what is inside and how is it used?
- Boundary: what does the product not do?
Example:
Boundaries increase credibility and reduce poor-fit purchases. They also generate strong comparison and FAQ content.
Mine real questions
Use exact language from customer conversations, comments, support, product-page searches, reviews you are allowed to analyze, and your own sales calls. Tag each question by the decision it blocks.
| Content pillar | Buyer question | Useful format | Natural CTA |
|---|---|---|---|
| Problem | “Why does this keep happening?” | Symptom checklist or teardown | Diagnose your workflow |
| Method | “How would I fix it?” | Tutorial or framework | Use the free starter tool |
| Proof | “Will this work in practice?” | Demonstration or worked example | See the complete example |
| Product | “What exactly do I get?” | Walkthrough or preview | View the product page |
| Objection | “Will it fit my situation?” | FAQ, comparison, limitation | Check fit and contents |
Apply this chapter to your store
Start with the live customer path, not a hypothetical version. Open the relevant content, profile, Tapmy page, email, or operational record and capture what a buyer sees now. Keep the scope to one campaign and one decision so the result can be measured.
Implementation move: Write the six lines using the customer’s language and keep them beside the product page.
Connect the decision to evidence: customer language, transition counts, questions, observed behavior, or a completed end-to-end test. If another person cannot understand why you chose the action, add the missing evidence rather than more strategy language.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Scope | One buyer, one campaign, and one next action are named | Narrow the work before creating more assets |
| Evidence | The current state is visible in a live route or record | Capture the source, destination, and decision point |
| Decision | the buyer, urgent problem, desired outcome, mechanism, proof, and next step that anchor all content is written clearly | Remove competing goals and choose one priority |
| Verification | a teammate can create a relevant post without inventing a new promise | Rework the weakest boundary, then retest it |
Common failure mode
Starting from format ideas instead of a stable product message. It creates activity without reliable learning. Use the chapter deliverable as a gate: the work is complete only when the decision is written, applied to the live path, and verified with the stated signal.
20-minute implementation sprint
- Open the live route or record and capture the starting state.
- Complete the smallest useful version of the six-line product-message brief.
- Apply the decision to one campaign or Tapmy path.
- Test the pass signal from the buyer’s point of view.
- Save the evidence and the next review date.
