Menu

Individual skill

saas-lifecycle

0upvotes

Use this skill when a subscription product's messaging needs to be designed, audited, or rebuilt across the whole customer journey — activation, onboarding, trial conversion, adoption, retention, expansion, failed-payment recovery, and win-back. Produces either a findings report ranked by leverage, or a staged build roadmap with the trigger, touches, and data prerequisites for each program. Trigger phrasings: "design our lifecycle", "why are we churning", "review our lifecycle emails", "trial conversion is low", "build a win-back flow", "dunning", "onboarding emails", "our activation rate is bad", "where do we start with lifecycle".

skills/tanyo-gochev/saas-lifecycle/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Applies to any subscription product with usage data. Produces an audit ranked by leverage, or a staged roadmap with data prerequisites named.

## Audit the data layer before anything else

The most common finding is not a missing campaign. It's that the events and attributes the messaging would need are not being tracked, are tracked inconsistently, or never reach the messaging platform. Design a beautiful behavioural program on top of that and it silently sends the wrong thing to everyone.

So the first move in any engagement is: what events actually exist and are populated? Are plan, usage, and subscription attributes flowing through? Where's the gap between what the messaging needs and what the data provides? **If the pipes are broken, fixing them is the first deliverable — say so plainly, even when the ask was for a campaign.**

## The eight stages

Locate the user on this map, then ask: what's the single next value moment, and what message helps them reach it?

1. **Acquisition** — signup created → set expectations, drive first login
2. **Activation** — first login → reach the aha moment
Back to top