Programs

Three ways the work begins.

Most engagements open with Diagnose. Some skip straight to Build when the diagnosis is already written. A few graduate to Advance — ongoing analytics work that pays for itself. The right one depends on where your data function is today.

Which program fits you?

Tell us where you are.

One question, thirty seconds. We'll point you at the program that matches the shape of your problem — not the shape of our pricing page.

cl/recommender · 30 seconds1 / 2

Question · 01

Where are you today?

Awaiting inputNo email required

Program · 01

Diagnose.

See what's broken.
Know what to fix first.

Most engagements open here. Two weeks, a written diagnosis of what's broken across GA4, attribution, the warehouse, and the dashboards your team has stopped trusting. You walk away with a prioritized fix list, an honest build-buy-kill call on every tool, and — if it's warranted — a scoped path into Build.

Capabilities
Audits · Data Strategy
Shape
2 weeks, fixed scope

Program · 02

Build.

Wire it right.
Document it well.

Event taxonomy, GTM, the warehouse, dbt models, executive dashboards — wired right the first time and documented for whoever you hire next. Scoped against the audit findings. You graduate from spreadsheet reporting to a defensible data layer your next analyst can read on day one.

Capabilities
Data Engineering · BI & Reporting
Shape
6–12 weeks, scoped per engagement

Program · 03

Advance.

Decisions, not dashboards.
Spend that compounds.

Attribution that survives a CFO challenge. LTV measured on a real cohort. A churn model that earns its keep at quarterly review. Advance is for teams whose warehouse is sound and whose next problem isn't more reporting — it's a defensible answer to a specific business question.

Capabilities
Advanced Analytics · Marketing Analytics
Shape
ongoing retainer or 4–8 week project

Typical engagement flow

How the three programs connect.

The default route runs all three, in order. About a third of engagements skip a stage. Each stage produces a defensible artifact you'd be comfortable showing the board before the next stage starts.

01Diagnose02Build03AdvanceBUILD FOLLOWSONCE STABLEONGOING SUPPORTSTART
01 · DiagnoseMost teams start here — two weeks, written diagnosis.
02 · BuildBuild follows the audit — ship the warehouse and dashboards.
03 · AdvanceOngoing once the warehouse is stable — models and decisions.

Side-by-side

The three programs, at a glance.

A compressed read for finance, ops, or anyone trying to brief a CTO in three minutes. Differentiating outputs are highlighted.

 № 01Diagnose№ 02Build№ 03Advance
Typical duration2 weeks · fixed scope6–12 weeks · scopedRetainer or 4–8 wk project
Deliverable shapeAudit doc + prioritized fix listWarehouse, dbt models, executive dashboardsPredictive models + decision loops
Best for teams that…Suspect their data is lying but can't prove itHave the diagnosis; need it shipped rightTrust the warehouse and want compounding work
CapabilitiesAudits · Data StrategyData Engineering · BI & ReportingAdvanced Analytics · Marketing Analytics
Tools usedGA4 · Segment · dbt · Snowflake · Hexdbt · Fivetran · Snowflake · Looker · GTMPython · Bayesian · cohort models · attribution
First defensible artifactWritten audit · end of scopePer the SOW · scoped milestonesSigned measurement plan

Frequently asked

Questions we get every week.

That's the most common starting point. Use the recommender above, or just send a note. Most engagements open with Diagnose because two written weeks are cheaper than guessing for three months.

Yes, when you've already done a credible audit or have an internal data lead who's written the diagnosis. We'll review what you have, agree it's defensible, and scope Build directly from it.

Scope conversations start with a 30-minute intro. We don't publish bands because Diagnose, Build, and Advance carry very different shapes — and so do the teams that need them. After one call we send a written scope and a number you can take to finance.

A two-week Diagnose. Smaller than that, you're asking us to ship without reading the stack first, and we don't do that work.

Occasionally, when the analytics question is unusually well-defined. The studio is sized for mid-market, growth-stage teams — that's where our diagnoses, dashboards, and models tend to pay for themselves.

You do. Every schema, dbt model, dashboard, and runbook we ship is yours. The point is to leave you ready to hire a full-timer who can read what we built on day one.

How to start

Still not sure?

Send a note. We'll read it, route you to the right starting point, and follow up with a 30-minute intro. No deck, no pitch — just a question or two so we can write a scope you can take to finance.

© 2026 Coded Level — Toronto analytics studio.Toronto, ON · Canada