Grow the customer: lifecycles, funnels, and the math

A lifecycle is only as good as its transition definitions. Every stage needs an entry/exit criterion sharp enough to count clients against - otherwise "adoption" becomes a feeling that CS and product argue about.

• Acquire → onboard: contract signed. Easy. Health today: win rate 22%, down from 31%.
• Onboard → adopt: Himalaya's definition from Session 5's canvas: second module activated within 30 days. This is THE transition - single-module clients stuck here are tomorrow's churn number, and Session 3 traced exactly why (partner-reseller onboarding gap, no activation playbook).
• Adopt → retain → expand: renewal is the retain gate (churn 14%); an additional paid module or seat growth is the expand gate (NRR 98% means expansion no longer covers churn).
• Advocate: referral or reference given - and Himalaya does not measure it at all. An unmeasured stage is a free growth lever nobody has pulled.

Himalaya's 8M end consumers walk their own road: discover → use → return → advocate. They are acquired FOR clients - and then never nurtured, never measured, never spoken to. That is the strategic blind spot and the opportunity in one.

• The dependency: consumer retention drives client retention. A business whose customers keep coming back through Himalaya does not churn - the platform is earning its renewal every day at the consumer layer.
• The instrumentation gap: Himalaya can tell you a client's module count instantly and cannot tell you whether that client's consumers returned last month. The metric that predicts churn best is the one not on any dashboard.
• The H3 link: Session 6's consumer-side option and flywheel both spin on this second lifecycle. You cannot monetize a road you have not mapped.

The lifecycle counts people at each stage; a journey map walks one person through the same spine and records what they touch and how they feel. Service-design practice, and the perfect diagnostic partner to the numbers.

• Same spine, different lens: for each stage, list touchpoints (emails, portal, partner reseller, support), the customer's goal, and the emotional temperature. Frustration clusters ARE the leak, seen from inside.
• Himalaya's onboard stage mapped: a client signed by a partner reseller meets a handoff email, a generic setup guide, and silence - no playbook, no second-module nudge. The map shows WHY the 30-day activation transition fails; the lifecycle shows HOW MUCH it costs.
• Do it cheap: one whiteboard, one real recent customer, sticky notes per touchpoint. Two hours. Resist the urge to buy software for this.

• Pick ONE metric per level, the one that moves the business, and instrument it properly. Ten metrics per level is a dashboard; one is a decision. Himalaya's picks: win rate, 30-day second-module activation, logo churn, referrals given, NRR.
• Weekly review, same numbers, same order. The power is longitudinal - the third week you look at the same five numbers, trends start talking.
• Levels are conversion gates: the question at each boundary is "what fraction makes it through, and what would move that fraction 5 points?" That phrasing turns metric review into action review.

Two leaks show on Himalaya's funnel: acquisition (win rate 22%) and activation (single-module stall). The rule: fix the biggest leak CLOSEST to revenue first.

• Downstream fixes compound upstream: every client saved at activation multiplies the value of every future win. Fix acquisition first and you pour more leads into a funnel that still leaks them out at month six.
• The classic error has a name: "we need more pipeline." More acquisition into a leaky funnel is buying water for a bucket with a hole - the most expensive possible way to stay the same size.
• It also sequences the org: activation is CS + product work (playbook, starter tier, partner enablement); acquisition is sales + marketing spend. Himalaya's Session 2 verdict - activation fix first - lands in the same place from a third direction.

Brian Balfour and the Reforge school push past the funnel: funnels CONSUME inputs (every lead is bought or earned once), loops COMPOUND (the output of one cycle becomes the input of the next). Mature growth strategies run both and know which is which.

• Himalaya's candidate loop: consumer data improves platform recommendations → better client results → stronger case studies and referrals → more clients → more consumers → more data. Session 6's flywheel, now with metrics attached at each link.
• The test: ask of any growth motion, "if we stopped feeding it, would it keep turning?" Paid acquisition stops dead - funnel. Referrals from delighted advocates keep arriving - loop.
• Where AARRR fits: Referral is the funnel level that hints a loop is possible. Himalaya's "unmeasured" there means the loop is not even being watched, let alone engineered.

Lifetime value = yearly contribution × average lifetime, and average lifetime is just 1 / churn rate. Walk Himalaya's numbers:

So moving ONE client from single- to multi-module is worth roughly $150k of lifetime value. That single line prices the activation playbook: if it costs $500k to build and converts just four clients, it has paid for itself - and Session 3 found hundreds stuck at single-module.

• CAC payback = CAC / monthly contribution: how many months until a new client has covered their own acquisition cost. Under 12 months is comfortable for SaaS; past 24, growth eats cash.
• The 3:1 rule of thumb: LTV should be at least 3× CAC. Below it you are buying customers at a loss; far above it (8:1+) you are probably under-investing in growth.
• Its abuse: it is a ratio, not a strategy. Denominators get gamed - exclude sales salaries from CAC, assume yesterday's churn forever in LTV, blend cohorts until the sick one disappears. Himalaya blended is ≈ $176k LTV; the single-module cohort inside it is ≈ $62k. Same company, one healthy-looking average, one cohort quietly bleeding.
• The honest version: always compute LTV:CAC per segment or cohort, never blended-only. The blend is where problems hide.

Philip Kotler's STP is marketing's oldest spine: Segment the market into distinct groups, Target the segments worth winning, Position the offer in the target's head. The starter tier from Session 5 needs all three before launch.

• Segment: smaller consumer businesses currently priced out of the ~$33k median - split by vertical, digital maturity, and transaction volume.
• Target: the slice with high transaction volume but low software budget - usage pricing fits them structurally, not just cheaply.
• Position: "start free of risk, pay as your customers actually use it" - against both the AI-natives' cheap seats and Himalaya's own heavyweight image. Positioning against your own flagship is the delicate part.

Recency, Frequency, Monetary - direct marketing's ancient workhorse. Score every one of Himalaya's 8M consumers on how recently, how often, and how much they transact, and the invisible second lifecycle becomes segmentable overnight.

• Why it fits here: RFM needs only transaction logs - which Himalaya's payments module already has. No surveys, no new instrumentation. The cheapest possible first light on the consumer road.
• The killer application: aggregate RFM per client. A client whose consumers' recency scores are collapsing is a churn risk months before renewal - the early-warning system Part 1's twist card asked for.

Fred Reichheld's Net Promoter Score (Bain, 2003): "how likely are you to recommend us?" - promoters minus detractors. It would give Himalaya's unmeasured advocate stage its first number.

• Trend, not absolute: NPS varies wildly by industry and survey mechanics. A score of 30 means little; a slide from 45 to 30 over three quarters means everything.
• Always pair with "why": the follow-up free-text question is where the value lives. The score gets attention in the boardroom; the verbatims tell you what to fix.
• Run it on BOTH lifecycles: client NPS and consumer NPS will disagree, and the gap between them is a strategy document in itself.