A current-state read
What you actually have, from the inside: systems, data quality, who maintains what, and what breaks when they're away.
01Service
Analytics Strategy
What to build, in what order, and what each piece is worth — decided before you spend a platform budget.
Not a maturity score. A sequenced roadmap tied to the decisions it unblocks, with the dependencies named, so you know why the third thing can't come first and what it costs to skip it.
Client databases in one view
49 to 1
A thirty-year-old travel-data platform, aggregated across clients for the first time, as a working proof rather than a report.
When this is the right service
Everyone agrees something must be done, and nobody agrees what.
A platform quote arrived and you can't tell whether it's the right first move. Technical leadership says rebuild; finance says the reports are fine. Two years of known-needed work and no agreed order.
If you already know what to measure and the problem is getting the number, skip this and go to Data Platform & BI.
What you get
The sequenced roadmap
Phases in dependency order, each with a price band, a duration and the decision it unblocks. Built to be handed to any competent firm.
A working proof
Where it's feasible, the riskiest assumption built small and real — so the roadmap rests on something demonstrated rather than asserted.
A metric glossary
Every number your board sees, defined once, in your words. Usually the first time competing definitions get surfaced in writing.
What not to do
The work that looks urgent and isn't, and the spend we'd advise against. Named explicitly, with the reasoning.
A board-ready summary
One document your sponsor can present without translating it first. Written for the people approving the money.
How it runs
Fixed price, fixed end date, and a deliverable that outlives the engagement.
You are not committed to us for the build. The roadmap is written so anyone can execute it.
01Weeks 1–3
Discovery
Sessions with the people who actually produce the numbers, not just the executives who consume them.
02Weeks 4–7
Proof
The riskiest assumption built for real against your live data, so the recommendation is tested rather than theoretical.
03Weeks 8–12
Recommendation
The roadmap, priced and sequenced, reviewed with your sponsor before it's final rather than presented as a surprise.
Then your call
Execute
Hand it to your team, to another firm, or to us as a platform build. No obligation either way.
Travel-data SaaS · holdco portco
A thirty-year-old platform had never aggregated across its clients. The engagement returned a working proof of concept, not a report about one.
On record
Day 10
Six discovery sessions complete, a week ahead of plan
49 → 1
Databases brought into a single aggregated view for the first time
2 years
A rebuild the client knew was needed, finally sequenced and priced
Scope cut
We narrowed our own proposal before signing, and said which parts could wait
Every figure traces to a delivery artifact — acceptance documents, refresh logs, or a reconciliation the client ran themselves. Clients are blinded until they've signed off on being named.
What this isn't
Not a maturity assessment
Scoring you against a generic model tells you nothing you can act on Monday. You get a sequence, not a grade.
Not a sales document
The roadmap is written to be executable by anyone. If the right answer is a smaller job or a different firm, it says so.
Not a slide deck
Where it's feasible you end the engagement with something running, because a recommendation nobody has tested is a guess.
Bring the decision you can't get agreement on.
Thirty minutes, no deck. If a strategy engagement isn't the right first move, we'll say which service is.