Find the revenue your lifecycle is losing
Perennus finds where customers drop between signup and renewal, and why. Then our studio builds the fix.
- Acquire
- Activate
- Convert
- Retain
- Recover
- Expand
Under investigationActivate → Convert
- ObservedWho is in this transition?Accounts that activated and haven’t converted.Counted from your events
- DerivedWhere does it break?The behaviour that separates those who converted from those who stalled.Computed from what’s observed
- InferredWhy does it break?A hypothesis about the cause, and the fix it points to.Untested until measured
- UnknownWhat is it worth?The revenue tied to moving this transition.Withheld until the evidence supports a figure
Measured in client engagements
See the case studies13.3%→60.2%of onboarding recipients reaching activation
AI companion app
28% peak→0%Gmail spam-report rate, over the eight send days after the fix
AI companion app
36.9%→0.0%failed sends: the same newsletter to everyone, then to a behaviourally defined audience
Realworld
56.3%→2.1%Gmail bounce rate, after authentication and list fixes
AI companion app
1.0%→8.4%re-engagement conversion on a corrected trigger
AI companion app
Revenue doesn’t disappear.
It gets lost between states.
Your dashboards report the moments: sent, delivered, opened, paid. The revenue goes missing in the transitions between them, where nobody is measuring.
What the dashboard says
- Campaigns sent
- Emails delivered
- Sequences live
All green
What the account shows
~174,000
Around 174,000 sends queued by one misconfigured entry condition, against a list of 66,000. It appeared in no campaign report.
Found by reading the trigger logic
How Perennus works
Find it. Understand it. Fix it.
The product finds where your lifecycle breaks. The studio builds the fix.
The studio
When the scan finds it, we fix it.
Done-for-you lifecycle work, built inside the tools you already run and handed back documented. Every engagement starts with an audit, not a proposal.
- 01 · Diagnose Lifecycle Diagnostic Find where your lifecycle breaks, and what the evidence says to fix first. Standalone engagementLearn more
- 02 · Build Lifecycle Build Rebuild the broken transitions, or build the system from zero. Standalone projectLearn more
- 03 · Run Lifecycle Partnership Run and improve your lifecycle with us, month after month. Recurring engagementLearn more
Two or three engagements at a time.
Case studies
Results you can check.
Every figure says where it comes from. Where nothing was measured, the case says so.
- NotionIndependent · not a client Four signals collected at signup. None used in the lifecycle. Read the case study
- AI companion subscription app Every report said “delivered”. Gmail disagreed. Read the case study
- Realworld They asked for five campaigns. First, we decided who owned the user. Read the case study
Clients
In their words.
Research
We take products apart in public.
Their teams read it.
Independent teardowns of products we weren’t hired to work on: what we noticed, how we checked it, and where the evidence stops. Kit’s founder replied in public; Notion’s Head of EMEA Marketing reached out.
- The lifecycle autopsy: how a product at that valuation fumbles activation. “…led to a genuinely insightful discussion on customer lifecycles, production adoption, and AI.”Áine Dundas, Head of EMEA Marketing at Notion, on the conversation that followed. Notion has not commented on the findings. Read the teardown
- Six questions in. One email out. “We could definitely do more with that data! It does personalize things in the app to make it more seamless to migrate from a specific provider. But you’re right it should change the emails as well.”Nathan Barry, Founder of Kit, replying in public Read the teardown
- Ten million orders. 2.1 million users. FindingDivide the two public numbers and you get roughly one order every 2.5 months per registered user. The milestone hides the frequency question. Read the teardown
- Fourteen months of going quiet. FindingWe stopped ordering on purpose and stayed subscribed. Glovo sent 35 reactivation emails, plus push notifications. The other delivery services we tracked never did. Read the teardown
Who you’ll work with
Every engagement is led by Isaac Olukoya, founder of Perennus.
Isaac works on the layer that decides whether acquisition ever pays for itself: everything after someone signs up. He built Perennus after finding the same leaks by hand, account after account, for teams in the US, the UK and across Africa. The person you talk to is the person who does the work.
More about Isaac and PerennusQuestions, answered.
What is Perennus?
Two things that work together. Perennus the product reads your lifecycle and shows where customers drop between states and what the evidence points to. The Perennus studio builds the fix: onboarding, deliverability, conversion, re-engagement and measurement.
Is the scan really free?
Yes. Connect your workspace and run a scan. No card required and nothing is gated: you see everything it finds.
What access does Perennus need?
Read-only API access to your messaging workspace. Perennus never sends, edits or deletes anything in your account. Customer.io is supported today; Klaviyo and HubSpot connections are built but not yet proven on live workspaces.
Do I need the studio to use the product?
No. You can run the scan and fix what it finds yourself. When a finding needs a rebuild rather than a tweak, that’s where the studio comes in.
How does a studio engagement work?
It starts with a call, then an audit of your account, not a proposal. We scope the engagement around what the lifecycle actually needs, build inside the tools you already use, and hand back a documented system your team can run.
Something else? isaac@isaacolukoya.com
Find the revenue you’re losing.
Tell us where you think it breaks. We’ll show you what the evidence says.