Agent Skills · ZIP download
SaaS Growth & Operations
Follow a SaaS customer journey through acquisition, activation and retention, then review operational signals.
You’ll review the offer on Whop before paying.

What’s included
In the download
- 23 task Skills and one router
- Instrumentation and cohort checks
- Support, incident and experiment reviews
What you can produce
- A record of known and unknown sources, with identity and consent handling for the cases supplied.
- Funnel losses and comparable retention results that identify mature and pending cohorts.
- An operating review that ties thresholds and outcomes to the next review date.
How to use it
Pick a journey or review
Open README.md and list the measure, distribute or operate route. Start with one source of traffic and one action that counts as activation.
Check the measurement
Use the browser runner or your host browser to observe the destination and event behavior. Map those observations and your exports into the selected task’s input.
Read the gaps and decisions
Save JSON with --out artifacts/project. Review attribution buckets, step denominators and retention windows before choosing the next investigation or experiment.
Before you buy
Pick this edition if
- Teams with live acquisition that need to verify the path from arrival to first value and return.
- Operators bringing campaign results, experiments, support and incident evidence into the next review.
What you’ll need
- Campaign destinations, an activation event definition, event or cohort exports, and a comparable time window.
- Replay evidence, experiment thresholds, support records or incident details for the decision you want to make.
Attribution and retention use your approved exports and recorded observations. Losses describe the measured journey. A causal conclusion needs separate evidence.
Questions
Do I need one specific analytics platform?
Use the relevant task’s example to map fields from the sources you can access. Check that the windows, event definitions and denominators agree.
How do I separate unknown traffic from zero traffic?
S60 records unknown attribution and missing measurements separately from an observed count of zero.

