· 10 min read
Lifecycle marketing for flat products
Almost every lifecycle guide assumes you're working on a product where users engage daily or weekly, move through obvious stages, and reward optimisation at every step. Most products aren't like that. Tax software gets used once a year. Travel booking is lumpy and seasonal. Insurance is almost entirely passive. Lifecycle work on these products has to do something different — and applying the standard playbook usually makes them worse.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
The mismatch between textbook and reality
The standard playbook assumes a product whose usage gives you something to work with constantly. A flat product doesn't.
The standard lifecycle playbook is built around high-frequency consumer products. Users engage multiple times a week, move from new to activated to engaged in a predictable arc, and leave signals frequently enough that behavioural segmentation is always fresh. Onboarding is a first-week job. Retention is a weekly metric. Win-back fires at 30 or 60 days. The model assumes a product whose usage gives you something to work with constantly.
A flat product — one with annual, seasonal, transactional, or otherwise infrequent usage — violates all of those assumptions. Users engage rarely, so behavioural signals are sparse. Stages blur because the product doesn't offer enough events to separate them. Onboarding isn't a first-week job because there's nothing to activate into; there's just the next use. Retention is a yearly metric, and by the time you can measure it, the levers that influenced it are long gone.
Applying the standard playbook to this reality usually produces noise. A week-one onboarding sequence for a product used once a year converts poorly — the user isn't coming back this week regardless. A 30-day win-back for a product with a 9-month cycle is just noise, and a user who got one reads you as out of touch with how they actually use the product.
Start from the usage shape, not the playbook
The first step for lifecycle work on a flat product is an honest description of the product's usage shape. Four questions determine most of what the program should look like:
What is the natural usage cycle? A tax product has an annual spike. Travel booking has seasonal bursts. Insurance has event-driven engagement. Gift cards are pulsed around holidays. The cycle shape is the single most important input into lifecycle design — everything else follows from it.
What non-usage signals do users leave?Login without transaction. Support ticket. Settings change. Reading docs. These are weaker than transaction signals but frequently the only behavioural data available between transactions, and they're worth instrumenting carefully because they're what your segmentation will actually run on.
What's the decision window before a usage event?Users typically don't decide to use an infrequent product on the day of use. They decide in a window that can be days, weeks, or months wide. Lifecycle leverage lives in that window — messages during the decision window are the ones that actually change behaviour.
What signals the start of a new cycle? Annual renewal date. Seasonal trigger. Post-transaction satisfaction. Some products have explicit cycle starts; others need them inferred. Either way, the cycle start is the natural re-engagement moment and deserves disproportionate lifecycle attention.
The Orbit Lifecycle Program Design skill starts with exactly these questions for any program — the output shape of the program falls out of the usage shape rather than being imposed by a textbook template.
Build for the cycle, not the week
For a flat product, the lifecycle program is organised around the cycle, not the week. The canonical stages aren't new / activated / engaged / at-risk / lapsed — they're pre-cycle / in-cycle / post-cycle / off-cycle. Each has a different purpose:
Pre-cycle.The decision window. Messages here are about making the case for use when the next cycle rolls around — product updates, reminders of last use, preparation content. This is where most of the genuine lifecycle leverage lives, and it's where most flat-product programs underinvest.
In-cycle. The transactional moment. Messages here are usage-enabling — reminders to finish, cross-sell of adjacent products, handoff to support. Short, high-intent, tolerates more frequency because the user is actively in the product.
Post-cycle.Immediately after a use event. The single highest-engagement moment in a flat product's lifecycle — users are most willing to provide feedback, set preferences, subscribe, share. Most flat-product programs waste this moment on a confirmation email and then fall silent.
Off-cycle.The long period between cycles. Content is the dominant channel here — helpful, periodic touches that keep the brand present without demanding usage the user isn't ready for. The mistake to avoid: frequent transactional-style messaging during off-cycle, which reads as noise and trains the user to ignore you.
Measurement has to adapt to the cycle
Weekly open rate is a noisy metric on a product that doesn't expect weekly engagement. Month-over-month retention is meaningless for a product with an annual cycle. A flat-product lifecycle program needs its own measurement shape, usually centred on two numbers: cycle-over-cycle return rate (users who completed the last cycle and also completed this one) and decision-window engagement rate (share of users engaging with the program during their specific decision window).
Neither of these appears on a standard lifecycle dashboard. Both are usually the most important numbers for the program. Building the reporting to surface them is a separate piece of work that most programs skip because the dashboard templates assume a high-frequency product.
The Retention Economics skill covers the LTV and payback modelling for products with long cycles specifically — where the standard monthly cohort curve shapes don't apply and you need cycle-aligned modelling instead. The cadence guide covers how frequency settings also have to shift for a flat product.
What to stop doing
Three common mistakes worth catching early on a flat-product lifecycle program:
Sending frequent messaging to fill a calendar. Weekly newsletters on a product users engage with annually train users to unsubscribe. If there's nothing cycle-relevant to say, silence is a feature.
Running win-back programs on standard thresholds. A 60-day no-engagement window is meaningless for a quarterly product. Define lapse on the cycle, not on the calendar.
Measuring against engagement metrics that don't match the cycle. If your leadership team is being shown monthly open rates for an annual-cycle product, the numbers are going to be terrible every month of the year except the spike month, and the program will look broken when it isn't. Agree the reporting shape before you have to explain it.
Frequently asked questions
- Does standard lifecycle advice apply to low-frequency products?
- Rarely without significant adaptation. The playbook assumes high-frequency engagement; a product used quarterly or annually violates almost every assumption it makes. Start from the usage shape and rebuild the program around it rather than trying to force the textbook pattern.
- What lifecycle stages work for a flat product?
- Pre-cycle, in-cycle, post-cycle, off-cycle is usually a better frame than the standard new / activated / engaged / at-risk / lapsed stages. Each has a different purpose and tolerates different message density. Most leverage is in pre-cycle (the decision window) and post-cycle (the highest-engagement moment).
- How often should I email users of a flat product?
- On cycle, not on calendar. Messages during the decision window, at the transaction moment, and immediately after a use event. Off-cycle messaging should be sparse, content-oriented, and tolerant of long silences. Filling a calendar with weekly sends to an annually-used product trains users to unsubscribe.
- When should I define a lapsed user on a flat product?
- At a threshold derived from the natural cycle, not a round calendar number. For an annual product, that might be two full cycles missed. For a quarterly product, two or three cycles. The right threshold is the point where cycle-over-cycle return probability drops significantly.
- Should I still run a win-back program?
- Yes, but triggered by cycle signals, not calendar elapsed time. A win-back that fires 60 days after last engagement is noise on a quarterly product. A win-back that fires when a user misses a natural cycle-start trigger (annual renewal window opens and no engagement) is meaningful.
- What metrics should I report for a flat-product program?
- Cycle-over-cycle return rate and decision-window engagement rate are usually the two that matter most. Neither appears on a standard lifecycle dashboard. Building the reporting to show these is a separate workstream worth doing early.
- How do I handle onboarding for a product that's used annually?
- First-use completion is the equivalent of activation. Week-one onboarding loses to a program that activates users through their first cycle, which may span months. The success metric isn't 'activated within seven days' but 'completed a first successful use event' even if that takes six months.
This guide is backed by an Orbit skill
Related guides
Segmentation strategy: beyond RFM
RFM (Recency, Frequency, Monetary) is the floor of audience segmentation, not the ceiling. This guide shows how to design a segmentation model that actually drives lifecycle decisions — lifecycle stage, behavioural intent, and predictive tiers.
Retention economics: proving lifecycle ROI to finance
Lifecycle programs get deprioritised when they can't defend their impact in dollars. This guide covers the four models every lifecycle leader should know — LTV, payback, cohort retention, and incrementality — and how to present them to a CFO.