Executive Summary
Your data team is spending a few frantic days trying to produce a 'Cohort Retention by Vintage' chart for an investor, and the numbers don't quite match last month's board report.
This isn't just an inconvenience. Investors tend to see inconsistent metrics as a sign of operational trouble, which can damage trust at a critical moment.
The problem isn't usually the analyst's SQL query. It often comes down to metric definitions that haven't been pinned down across the business. The fix is to stop the last-minute work and build a single, governed source for your core metrics.
The familiar scramble for a cohort chart
It's a familiar moment. You're in the middle of a Series B due diligence process. The investors are happy with the top-line growth and make a reasonable request: "Can you send over cohort retention, by monthly vintage, for the last 24 months?" You pass the email to your Head of Data, thinking it's a straightforward job.
Then, a bit of a pause. The Slack messages begin.
Your analyst, who is very good, pulls the data. But it doesn't line up with the churn figures from the last board pack. It turns out the logic for that pack was a one-off script, and the underlying data has since been updated. The product team's definition of an 'active user' is different from how the finance team defines a 'paying customer'. The result is a few days of everyone dropping tools to reconcile figures that were never really designed to be reconciled in the first place.
By the time you get the chart, it comes with a page of caveats and footnotes. You've lost three days, your team is tired, and you've presented a critical business metric that looks, shall we say, a little cobbled together. This isn't really a reporting problem: it's a symptom of a deeper one.
Why different teams define churn differently
In my experience, the problem isn't the dashboard tool, and it's not your analyst. It's often a sign that the business has scaled on metrics that were never formally agreed upon. You might have a modern data stack, with Snowflake, dbt, and Looker, but you've just moved the same issues to a faster system. Automating a fuzzy process just gets you the wrong answers more quickly.
I've seen this happen at quite a few scale-ups. The root cause of a wobbly cohort chart is almost always a fractured Churn Definition. This isn't a technical issue, it's an organisational one.
When an investor asks for the retention number, which one is correct? The scramble is your team trying to stitch these different views together with SQL. This can be a red flag during the Due Diligence process, as it can suggest a lack of clarity on the business's core mechanics.
A more structured way to define and report metrics
The fix for this isn't usually another dashboard or hiring a new analyst. It's about changing how you structure your data work.
The trade-offs of a consistent approach
To be clear, putting this in place can be disruptive. It means taking away the 'flexibility' for departments to define metrics in a way that suits their immediate goals. It means using a standard that might make one team's numbers look less good in the short term. You are asking them to give up their local spreadsheets and work from a shared definition. You should probably expect some resistance.
This kind of change usually needs a top-down mandate. It might mean slowing down for a couple of weeks, but it lets you move faster and with more confidence for the next few years.
What this looks like in the next funding round
Imagine the next funding round. The investor asks for the cohort chart. Instead of a three-day scramble, your Head of Data applies a filter to a dashboard and sends back a trusted, accurate chart in five minutes. The numbers match the board pack precisely because they are drawn from the same governed source.
That is the difference between a business running on slightly chaotic data and one with a defensible, scalable way of handling it. You're no longer just reporting numbers: you're showing you have a robust, well-understood business. Your valuation is now supported by your data, not undermined by it.