saranskumar Goal
Identify sustainable growth mechanisms grounded in product behavior.
When to use
- The MVP is clear and the team wants adoption or expansion loops.
- Activation or retention is a bigger risk than pure feature scope.
- Sharing, collaboration, outputs, or usage habits could drive growth.
Instructions
- Define the activation event and time-to-value target.
- Identify what user action or artifact can naturally create repeat usage or expansion.
- Design one primary loop and one supporting loop at most.
- Explain how the loop helps users, not just the company.
- Specify what must be measured to validate the loop.
Constraints
- Do not add viral mechanics that feel extractive or off-brand.
- Do not design loops that depend on a weak core product.
- Keep growth recommendations compatible with privacy and consent rules.
Output format
- Activation definition
- Growth loop design
- Measurement plan
- Risks and prerequisites
Examples
- "Design a collaboration loop for this analytics product."
- "How can this AI workflow tool retain teams after first value?"
Output expectations
The loop should feel like a natural extension of the product, not a marketing graft.