Implementation worksheet · 5 min read
A Signup-to-First-Value Lifecycle Campaign Specification
Specify the journey in five parts before building anything: the first-value event (one product action that predicts retention, chosen from data or founder conviction — not 'logged in'), the eligibility window (typically days 0-14), the intervention ladder (day-0 welcome with one action, day-2 nudge if the value event hasn't fired, day-5 different-angle attempt, day-9 human-or-highest-card offer), exit conditions (value event fires, or window ends, or user opts down), and the holdout (5-10% receiving nothing, so you measure the campaign rather than the cohort).
Every SaaS builds this journey; few specify it, and unspecified journeys accrete steps until nobody knows what's firing or why. One page of spec prevents a quarter of archaeology.
Put it into practice
1. Choose ONE first-value event
The product action after which retention visibly bends — imported data, invited teammate, shipped first thing. If analytics can't tell you yet, pick by conviction and mark it for revisit. 'Session started' is activity, not value; specifying it guarantees a campaign that optimizes noise.
2. Set the eligibility window honestly
When does signup-to-value realistically happen for users who make it? Days 0-14 is common; B2B with procurement can be 30. Past the window, users exit to a different journey (long-term nurture), not to more of the same nudges.
3. Write the intervention ladder with exits between rungs
Each message fires only if the value event still hasn't. Every rung takes a different angle — repeat nudges teach users to ignore you. Cap the ladder; four touches unanswered is an answer.
4. Define every exit explicitly
Value fired → exit to post-activation. Window closed → exit to nurture. Unsubscribed or opted-down → exit, honored globally. Journeys without written exits are how users get day-40 'finish setting up!' emails after churning.
5. Reserve the holdout before launch
5-10% eligible-but-excluded, assigned at entry. Compare value-event rates at window close. Without it, seasonal cohort quality gets booked as campaign performance — in both directions.
Specification worksheet
Copy this structure into your review document and record your observed result for each row.
| Element | Your value | Notes |
|---|---|---|
| First-value event | one event, product action | |
| Eligibility window | days from signup | |
| Ladder (touch : condition : angle) | max 4 rungs | |
| Exit conditions | value / window / opt-down | |
| Holdout % | assigned at entry |
A failure worth checking
The activity-metric failure: defining first value as logins or sessions because the real value event wasn't instrumented yet. The campaign then 'succeeds' at generating opens and logins while retention doesn't move — months of optimization spent on a proxy. Instrument the real event first; the campaign can wait two weeks.
Common questions
What if my product has multiple first-value paths?
Pick the dominant one for v1 and route by intent signal later (role, stated goal at signup). One spec shipped beats three specs debated — the branching earns its complexity only after the main path measures well.
Should sales-assisted signups enter this journey?
Only the self-serve rungs that don't collide with a rep's outreach — which means the spec needs a suppression rule for accounts with active sales ownership. That one line prevents the classic double-touch embarrassment.
Basis and scope
This is a proposed implementation method using illustrative examples, not a measured benchmark or a customer case study. Prepared with AI assistance. Validate product-specific behavior against current documentation and your own test environment.