Industries / SaaS · The relay, run properly
You built the product. Nobody told you about the relay.
SaaS growth isn't one funnel — it's a relay with five handoffs: stranger to visitor, visitor to trial, trial to activated, activated to paying, paying to staying. Your product is only as alive as its weakest handoff, and every founder is currently dropping at least one baton without knowing which. Here are all five, named — and what it looks like when something runs the whole race.
The relay · five handoffs, honestly named
Your growth is exactly as strong as your weakest handoff.
Handoff 1 · Stranger → Visitor
Launch day was a mountain. Every day since has been the flat line.
You know the chart — the Product Hunt spike, then the plateau that quietly says nobody new is finding you. The fix isn't another launch; it's a steady supply line: the problem-words your buyers actually type, the comparison pages they read on decision day, the founder's voice in the places your users already gather — published on a rhythm that doesn't care how your sprint went.
Handoff 2 · Visitor → Trial
Your site offers strangers a binary: start a trial, or leave forever.
Most visitors aren't ready to evaluate software today — and your site gives them nothing else to say yes to, so they leave and forget you existed. The system builds the middle door: the outcome-first pages that sell what the product does to their week, and capture that trades real value for an address — so the 95% who don't trial today become a list that trials eventually.
Handoff 3 · Trial → Activated
The signup graveyard: they came, they clicked twice, they never came back.
The most expensive silence in SaaS. Most trials don't die from disliking the product — they die before experiencing it, stuck at an empty state or a stubborn import, while generic onboarding emails wave cheerfully from a distance. The system watches where each trial actually stops and sends the letter that unsticks that person, at that step — which is the whole difference.
Day 2 · 09:30 · triggered by where he actually stopped
Handoff 4 · Activated → Paying
Day 14 arrives and your product screams like a parking meter.
The countdown-panic expiry email converts the desperate and burns everyone else. The system closes like a good account manager instead: the letter that knows what they used, names the plan that fits it, and offers a dignified exit with their data — because trust at the moment of payment is what the renewal is made of.
Handoff 5 · Paying → Staying
Churn never announces itself. Usage just gets quieter until the cancel email.
By the time someone cancels, they decided weeks ago — when the logins thinned and nobody noticed. The system notices: the check-in when usage dips below their own pattern, the feature note that fits how they work, the expansion conversation when their team grows — and the advocate ask at the moment they're winning. In a subscription business, the sale never closes; it just keeps being earned — by something that never forgets to earn it.
The engagement · what actually happens, in order
One package, positioning to relay. Here's the procedure.
Not a newsletter bolted onto a product — the whole arc in sequence, because traffic bought before activation works just measures the leak faster.
Step 1 · The product evaluation
Intelligence builds the dossier the way a buyer would: your product against every alternative in the search results — including spreadsheets and doing nothing — who actually converts and stays versus who you built for, and the answer technical founders rarely get from anyone they pay: what is the one job this does meaningfully better, and for whom exactly? “It's like X but better” is not a position; if that's where you are, you hear it first — repositioning costs a homepage, not a pivot.
Step 2 · The SaaS math
Software's unit economics, made explicit and honest: what a customer is truly worth given your actual churn — because churn sets the ceiling on everything; at high churn there is no acquisition strategy, only a treadmill — and therefore what you can pay for a signup, what activation rate makes the model work, and which handoff currently costs you the most MRR. Every budget and cadence decision afterwards answers to this arithmetic.
Step 3 · The assets
The relay's infrastructure, built: the site that sells the outcome and lets the feature list be evidence; the comparison and problem pages your buyers read on decision day; the middle door for not-today visitors; and the letter rails wired to behavior — onboarding, expiry, winback, check-in — each one written in your voice and triggered by what users actually do, not by day numbers.
Step 4 · The growth path
With the relay holding batons, the top gets fed: the compounding content library shipping weekly through your sprints, the founder's voice where your users gather, and paid spend — if the Step 2 math approves it — pointed only at the audiences that activate. Order matters: traffic scales after activation works, because that's when each visitor is worth multiples more.
Then · The engine, running
The cadence holds while you ship; trials get caught at the step they stall; expiries close with respect; quiet accounts get noticed before the cancel; and the Monday readout speaks MRR: which content starts trials that activate, where the relay leaks this month, what moved after last week's fix. You build the product. The relay finally has a runner. The working parts, below.
The working parts
The services, adapted to software — and what each does for a product.
Everything below exists to keep five batons in the air at once — without the founder having to stop building to catch them.
Traffic is the multiplier. Activation is the number it multiplies.
The loop, for software
From signup to expansion — one loop.
Asked before trusting
The three questions every SaaS founder asks.
Founding access
Put a runner on every handoff.
The one job named, the math made honest, the trials caught where they stall, the renewals earned weekly. Reserve founding access at your founding rate.
No agency markup · cancel anytime · built at EDMA Group