Chapter 1
Decide whether the need is recurring
Finish this chapter with a recurring-need scorecard you can use immediately to decide whether the need is recurring, while avoiding selling recurring access before proving recurring value.
What you’ll get
- A completed recurring-need scorecard, not a list of abstract ideas.
- One explicit decision rule for decide whether the need is recurring.
- A 45-minute execution sequence you can repeat yourself or hand to a teammate.
- A quality gate that tells you whether to move forward, run one small test, or revise the input.
Use this chapter as a working session
Open the document, spreadsheet, or Tapmy workspace where this decision will live. Replace sample language with the exact offer, buyer, channel, price, and evidence you have today. If a fact is missing, label it as an assumption and assign the smallest test that can resolve it.
| Time | Work | Concrete output |
|---|---|---|
| 0–10 min | Collect buyer words, traffic data, sales conversations, support questions, and current page copy. | A short evidence list with source and date. |
| 10–20 min | Make the single decision this chapter is designed to resolve. | A one-sentence decision and reason. |
| 20–35 min | Build the recurring-need scorecard with real names, numbers, links, and owners. | A usable operating asset. |
| 35–45 min | Review it from the buyer’s point of view and run the quality gate. | A keep, test, or revise decision. |
Run the repeat-need test
A membership is a better fit when customers repeatedly need one or more of the following:
- fresh information or resources;
- ongoing practice and feedback;
- accountability toward a continuing goal;
- access to peers with a shared job;
- access to the creator or specialists on a defined cadence;
- maintained tools, updates, or opportunities.
A one-time need—such as setting up one document—may be better served by a product or service.
Look for evidence
Interview people who fit the intended audience. Review repeat questions, ongoing-support requests, usage patterns, and what customers do after completing your current offer. Avoid treating “a community sounds nice” as validation.
| Evidence | What it may indicate | What to verify |
|---|---|---|
| Customers ask for regular feedback | Accountability or expert-access value | Frequency and capacity |
| Buyers request updated assets | Resource-library value | Update cadence and production effort |
| Peers help each other repeatedly | Community value | Moderation and shared identity |
| Customers finish once and leave | One-time product may fit better | Whether a new recurring job exists |
| Interest depends on your daily presence | High creator dependency | Sustainability and coverage |
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The recurring-need scorecard is ready to use. | Put it into the Tapmy journey and measure the next observable behavior. |
| One important input is assumed | The direction is testable, not yet proven. | Run the smallest test that can confirm or reject that assumption. |
| The asset serves several audiences, offers, or goals | The scope is too broad. | Narrow to one buyer, one job, one offer, and one reporting window. |
| The result depends on a claim you cannot show or deliver | Trust and delivery risk are higher than the upside. | Rewrite the promise around a supportable outcome. |
Quality standard
- The recurring-need scorecard names one buyer and one job.
- Every number has a timeframe, currency, or denominator where needed.
- Every link and handoff has an owner.
- The next action is visible without rereading the chapter.
- The decision can be measured through customer behavior.
- No claim is stronger than the evidence.
