| name | strat-acquisition-path |
| description | Chooses the correct next action for prospects based on offer readiness, awareness, trust, friction, price, urgency, and MVP maturity. Use after message-system to define CTA and acquisition path. |
Acquisition Path
Define whether the prospect should buy, test, join waitlist, book demo, apply, request diagnostic, DM, subscribe, or consume a lead magnet.
Workflow
- Load
../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
- Read
.ai/strategy/signal/*, .ai/strategy/offer/*, and .ai/strategy/gtm/message-system.md.
- Evaluate offer readiness, buyer awareness, trust required, friction level, price, urgency, and MVP maturity.
- Choose one recommended path and explain why not the others.
- Add a compact mapping table: Channel -> CTA -> Measurement Event.
- Define one next experiment with hypothesis and cutoff criterion.
- Save
.ai/strategy/gtm/acquisition-path.md.
Output template
# Acquisition Path
## Offer Readiness
## Buyer Awareness
## Trust Required
## Friction Level
## Recommended Path
Options: Direct checkout, Free trial, Freemium, Waitlist, Early access, Book demo, Diagnostic, Application, WhatsApp / DM, Newsletter, Lead magnet
## Primary CTA
## Secondary CTA
## Why This Path
## Why Not Other Paths
## Follow-Up Mechanism
## Measurement Events
## Conversion Risks
## Next Experiment
## Assumptions
## Open Questions
Decision rules
- Hot user: checkout, trial, or demo.
- Warm user: diagnostic, application, or early access.
- Cold user: newsletter, lead magnet, or content.
- SaaS validation: waitlist + demo, early access, or free trial.
- High-ticket: diagnostic, application, or call.
- Community: waitlist, application, or pilot cohort.
Output quality checklist
- CTA matches buyer readiness and trust.
- Primary vs secondary CTA are coherent.
- Measurement events are explicit.
- Channel/CTA/event mapping is included.
- Next experiment has hypothesis + cutoff.
Critical rules
Lead magnet is optional, not mandatory. Do not create downstream deliverables or implementation code.
