Don't wait for perfect
The instinct to wait for a perfect, fully-integrated data platform before doing anything is usually the wrong call inside a holding period that's already three years in, with two or three left. The better default:
Immediate value discovery in parallel with progressive data foundations.
The foundation work itself
That means running early, useful analysis against whatever data exists right now, siloed CRM exports, a spreadsheet of support tickets, whatever's actually accessible, while building toward better foundations at the same time, not sequencing one strictly before the other. Specific foundation work worth naming: resolving siloed data (sales, support, and product usage sitting in three systems that don't talk to each other) into a single customer identity (one canonical record per account, not three partial ones); agreeing KPI definitions once, centrally, so "NRR" is computed the same way in every report (directly enabling Lesson 30's standardization); and data quality work, the unglamorous but necessary cleanup that everything downstream depends on.
For Meridian specifically, this is exactly what stands between "we have an idea for account-health scoring" (Lesson 26) and it actually shipping: does account-level usage data already exist in a queryable form, or does building that come first?
| Question | Before | After |
|---|---|---|
| "How many active accounts?" | 3 different numbers, one per system | One number |
| Time to build a churn-risk report | ~2 weeks of manual joining | Hours |
| KPI definition consistency | "NRR" computed 3 different ways across teams | One definition, one source of truth |
Checkpoint
- Parallel, not sequential: pursue value discovery and data foundation work together, don't wait for a perfect platform first.
- Customer identity: one canonical record per account, resolved from siloed sources.
If anything here still feels unclear, ask before moving to Lesson 33.