Most SaaS growth conversations start with acquisition. CAC, channel performance, funnel conversion, paid efficiency. These are the metrics that fill the investor deck and dominate the Monday growth meeting.
They are also, with few exceptions, the wrong starting point. Acquisition metrics are outcome metrics. Product analytics metrics are the leading indicators that predict them, months in advance. The teams that understand this distinction — and build their operating cadence around leading indicators — consistently outperform the ones who are optimising acquisition while the product is still leaking.
This is true globally. It's especially true in African SaaS, where the unit economics are thinner, the runway is shorter, and the cost of acquiring a user who doesn't retain is higher relative to the available capital.
The difference between a leading and lagging indicator.
A lagging indicator tells you what happened. Revenue, churn rate, CAC — all lagging. They describe outcomes. They're essential for reporting and valuation, but they're backward-looking: by the time they show a problem, the problem has been building for months.
A leading indicator tells you what is going to happen if nothing changes. Activation rate, DAU/MAU, 30-day retention cohort — these are the numbers that predict, 90 to 180 days in advance, whether your revenue line will grow or contract. They're forward-looking. And they're entirely a function of product behaviour — which means they're actionable in a way that revenue growth rate isn't.
The practical significance: if your Day-30 retention is 8% and you're spending on acquisition, you're pouring into a leaking bucket. Every pound, dollar, or shilling you spend on acquiring users who will churn by Day-30 is value destroyed, not created. The product analytics signal tells you the bucket is leaking. The acquisition metric just shows you a growing spend line.
The metrics that matter, in the order they matter.
Not all product metrics are leading indicators. Here are the five that consistently predict revenue outcomes in the SaaS businesses I've observed:
Activation rate. The percentage of new users who reach the "aha moment" — the first point of genuine product value — within a defined window (usually 7 days). Target: above 25% is table stakes; above 40% is strong. This metric predicts everything downstream. A user who doesn't activate in the first week almost never becomes a retained user. Improving activation rate is the highest-leverage product investment at the seed stage, and it's the first thing I look at in any Traction Engine diagnostic.
Day-7 and Day-30 retention. The cohort curve. Plot the percentage of users from a given signup cohort who are still active at Day-7 and Day-30. The shape of this curve tells you three things: whether you have PMF (the curve flattens rather than continuing to decline), where the churn is happening (a steep Day-1 to Day-7 drop means the first-week experience is broken), and how your retention varies by acquisition source (which channels bring the cohorts that actually stay). Target: Day-30 cohort retention above 40% for a strong signal of early PMF.
DAU/MAU ratio. Daily active users divided by monthly active users. For habit-forming B2C products, the target is above 50%. For B2B SaaS with a weekly usage pattern, the equivalent weekly/monthly ratio is more relevant. This metric predicts net revenue retention — the degree to which existing customers grow their contract value over time. High DAU/MAU predicts high NRR. Low DAU/MAU predicts churn.
Active-to-registered ratio. The percentage of registered users who are genuinely active in a given period. This catches the vanity in user count metrics. A business with 10,000 registered users and 400 actives has very different economics to one with 10,000 registered and 3,000 actives, even though both can report "10,000 users" to investors. Target: above 25%.
Feature adoption rate for core vs. peripheral features. Which features are used by retained users that aren't used by churned users? This is the leading indicator of product strategy. The features that predict retention are the ones to double down on. The features that don't correlate with retention are candidates for deprioritisation, regardless of how much users say they want them.
Building the metrics-first operating cadence.
The teams that consistently improve these metrics share a discipline that has nothing to do with engineering skill or product intuition. It's the discipline of looking at the same numbers every week and committing to one initiative that will move one of them.
The operating loop is simple, borrowed from the Growth-as-Process framework I use with portfolio companies:
- Analyse. Every Monday, pull the five metrics above. Note the week-over-week change. Note any anomaly — a step change in activation, a cohort that retained better than baseline, a feature that saw unusual adoption.
- Hypothesise. For each anomaly or underperformance, generate one hypothesis about the cause. Not ten hypotheses — one, the most likely. Write it down.
- Experiment. Design the simplest possible test of the hypothesis. Not a three-month roadmap item — a change you can ship this week.
- Measure. After the test runs, pull the metric again. Did it move? If yes, keep the change and roll it forward. If no, kill it and generate the next hypothesis.
- Systematise. When something works consistently, codify it. Update the onboarding flow. Add it to the activation checklist. Write it into the product brief template. The learning compounds only if it's encoded.
The cadence is weekly. Not monthly, not quarterly. In a seed-stage SaaS business, a month of bad activation rate is 30 days of users who didn't retain. You can't afford that lag. Weekly is the minimum resolution at which the leading indicators are actionable.
What's different about African SaaS specifically.
The framework is global. The parameters are Africa-specific.
The aha moment is harder to deliver. KYC, identity verification, payment setup, and regulatory onboarding are heavier in African fintech, lending, and payments products than their Western equivalents. A user signing up for a Nigerian lending product may face 15 steps before they can use the core product. Activation rate targets need to account for this structural friction — and the product work required to lift activation is harder, deeper, and more cross-functional than "improve the signup flow."
WhatsApp is a retention layer, not just a notification channel. For a significant number of African consumer SaaS products, WhatsApp is where the retained user relationship lives. DAU/MAU in the app significantly understates actual product engagement because the engaged user is engaging through WhatsApp threads, not through the app. Measuring retention without measuring WhatsApp touch points produces a false picture of churn.
Cohort quality varies dramatically by geography. In a multi-country African SaaS product — say, a payments or logistics platform operating in Nigeria, Kenya, and Ghana — the cohort curves by country are almost always dramatically different. Nigerian cohorts may activate faster but retain worse. Kenyan cohorts may retain at higher rates but with lower average transaction values. Aggregated retention metrics flatten this and make the data useless for product decisions. Always segment by country first.
The data is noisier. Network outages, USSD session timeouts, intermittent connectivity — these produce event streams that look like churn but aren't. A user who appeared to stop using the product after Day-4 may have had a connectivity issue. Cleaning for this noise before reading the retention curves is a technical investment that most African startups don't make, and it means their product analytics are systematically misleading them about the true retention picture.
The path from product analytics to revenue growth.
The chain of causality is this: better activation rate → more retained users → higher DAU/MAU → better NRR → lower effective CAC → ability to spend more on acquisition → revenue growth.
Every step in that chain is mediated by a product decision, measurable in Amplitude or Mixpanel, and actionable on a weekly cadence. The businesses that understand this chain start with activation and work forwards. The businesses that don't start with acquisition and work backwards — and they consistently spend more, grow less, and burn runway on users who don't stay.
Product analytics is the infrastructure for making that chain legible. It doesn't require a data team, a BI tool, or a six-month instrumentation project. It requires three events, two charts, and a Monday habit of looking at what they show.
When a seed-stage African founder presents product analytics metrics — activation rate, retention cohorts, DAU/MAU — alongside revenue projections, the conversation shifts. These metrics don't just describe current performance; they justify the growth projection. A business with 42% Day-30 retention and 31% activation rate has a compounding math that a business with flat retention and declining activation doesn't, regardless of what the top-line growth rate shows. Investors who understand this — and more do every year — will ask for these metrics. Have them ready.