Chapter 1
Choose an audience promise
audience promise statement is the practical output of this chapter. Complete it in one focused work session so you can decide the specific useful change you want people to associate with your content, without growing around a broad identity that never creates product demand.
What you’ll get
- A completed audience promise statement you can use in the next chapter.
- A documented decision about the specific useful change you want people to associate with your content.
- A pass or fail signal: the promise naturally leads to a product category and filters out unrelated topics.
- A concrete first action: Complete the sentence ‘I help [person] move from [current state] to [useful state] through [approach].’
Be known for a useful change
An audience promise tells a prospective follower why returning will help them. It combines a person, problem, perspective, and recurring benefit:
Weak: “Tips for creators.” Stronger: “Practical product-launch systems for coaches turning one expertise topic into their first paid download.”
The promise should be broad enough for dozens of posts but narrow enough that a relevant person recognizes it. It is not a permanent identity; treat it as a focused season of publishing.
Connect the promise to an offer
Your lead product should solve a deeper or faster version of the problem your content addresses. If the content teaches audience growth but the store leads with unrelated meal plans, discovery will not become purchase intent.
| Audience layer | Question it answers | Example |
|---|---|---|
| Promise | Why follow? | Launch a useful digital product without a large team |
| Pillar 1 | What should I do? | Product idea and validation |
| Pillar 2 | How do I do it? | Building and packaging |
| Pillar 3 | How do I sell it? | Launch and conversion |
| Lead magnet | What can I use now? | One-page validation worksheet |
| Paid offer | What gets me to the full outcome? | Complete launch workbook and templates |
Apply this chapter to your store
Start with the evidence you already have: the current Tapmy setup, the exact customer path, the messages people see, and the records created after an action. Do not redesign the entire system while you are still trying to locate the constraint.
Implementation move: Complete the sentence ‘I help [person] move from [current state] to [useful state] through [approach].’
Write the decision beside the evidence that supports it. If a teammate cannot reproduce the conclusion from the same evidence, the work is not yet operational. The deliverable should be specific enough to hand to another person without a meeting.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Evidence | The current state is visible and reproducible | Capture the real route, screen, record, or message before changing it |
| Decision | the specific useful change you want people to associate with your content is written in one sentence | Reduce the scope until one owner can choose |
| Execution | Complete the sentence ‘I help [person] move from [current state] to [useful state] through [approach].’ | Assign a time and owner, then complete the smallest end-to-end version |
| Verification | the promise naturally leads to a product category and filters out unrelated topics | Return to the failed boundary and retest only after the cause is changed |
Common failure mode
Choosing a promise because it sounds inspirational rather than because it connects to a recurring problem. This hides the actual constraint and creates false confidence. Use the chapter output as a gate: do not move forward until the decision is explicit and the pass signal is visible.
20-minute implementation sprint
- Open the current Tapmy path and capture the starting state.
- Complete the smallest version of the audience promise statement.
- Record the decision, owner, and next review date.
- Test the pass signal once from the customer’s point of view.
- Save the evidence where the person running the next chapter can find it.