Two days for a cohort question, now forty seconds

The problem

Lanternfly’s revenue team ran weekly cohort reviews. Every review produced three follow-up questions, and every follow-up went into the data team’s queue. The median turnaround was two days, which meant the answer landed after the decision.

What changed

Sable read the warehouse, the CRM and the support tool, and mapped accounts across all three. Revenue now asks in plain language and gets the number with the tables it came from, so the data team reviews definitions instead of writing one-off queries.

Where they are now

Forty seconds is the weekly median across the whole company, measured on Sable’s own timing. The data team’s ad hoc queue went from about thirty tickets a week to four.