Chapter 1
Define whom you are looking for
first-customer fit statement is the practical output of this chapter. Complete it in one focused work session so you can decide the urgent problem, current trigger, and observable fit signals that define a relevant prospect, without targeting a broad demographic instead of people with current intent.
What you’ll get
- A completed first-customer fit statement ready for the next chapter.
- A documented decision about the urgent problem, current trigger, and observable fit signals that define a relevant prospect.
- A pass or fail signal: another person can qualify or reject a prospect using the same four signals.
- A first implementation move: Describe the ‘now problem’ in the buyer’s words and write four signs that the person is actively trying to solve it.
Write a “now problem,” not a demographic
“Female creators aged 25–34” does not tell you what to say. “Freelance designers who lose time building a new client-onboarding process every month” gives you a problem, moment, and product direction.
Complete this sentence:
Example:
If the sentence contains “anyone,” split it into narrower versions. Your first-customer message needs recognition more than reach.
Qualify with four signals
| Signal | Question | Strong evidence |
|---|---|---|
| Problem | Are they experiencing the problem? | They describe it in their own words |
| Timing | Do they need a solution soon? | A current project, deadline, or repeated task |
| Fit | Can your product produce the promised outcome? | Their workflow matches the use case |
| Access | Can you contact them appropriately? | Existing relationship, opt-in, community permission, or introduction |
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: Describe the ‘now problem’ in the buyer’s words and write four signs that the person is actively trying to solve it.
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 urgent problem, current trigger, and observable fit signals that define a relevant prospect is written clearly | Remove competing goals and choose one priority |
| Verification | another person can qualify or reject a prospect using the same four signals | Rework the weakest boundary, then retest it |
Common failure mode
Calling everyone in an industry a prospect even when they have no immediate problem. 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 first-customer fit statement.
- 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.
