Column-level lineage
Trace any number on a dashboard back through every join, model and source column. Lineage is parsed from query logs, so it stays correct without annotation.
How lineage is builtWhy mccloudCo
Data infrastructure should be boring. We make it boring on purpose.
mccloudCo started with a simple observation: a school district and a growing business have almost nothing in common — except both needed senior leadership they couldn't justify hiring full-time. Building one advisory model that actually works for both was never the easy part. It was just the part worth doing.
mccloudCo is two practices led by two principal consultants — one for schools and districts, one for growing businesses — and neither of us learned this business from the outside. We built the firm after watching what happens when "senior advisor" quietly becomes "whoever's available" once an engagement runs past the first few months, and after watching how often advice gets bent toward whatever platform or curriculum the advisor happens to sell. Neither happens here. It shows in how we work: the same consultant from the first call to the last, a named backup so nothing stalls if that consultant is ever out, and recommendations that are never steered by a commission — no curriculum, platform, or product endorsement sits behind anything we tell you. When an engagement ends, the rubrics, playbooks, and frameworks we used stay with your team; capability is the actual deliverable, not a report that gets filed away and forgotten.
We diagnose before we recommend anything — a short review, either standalone or built into the first month of working together, that tells us what the situation actually calls for rather than what we'd like to sell. From there, everything gets scoped and put in writing before any work begins, so there's never a gap between what was discussed on a call and what actually shows up in the engagement. The relationship is built to let you start small and grow only when the work demands it: plenty of our clients stay exactly where they started for years, and we treat that as a good outcome, not a missed upsell. Response times are published, not promised — thirty minutes for anything critical, a single business day for a routine request — and if the diagnostic turns up nothing that justifies bringing us in further, we say so directly instead of finding a reason to proceed anyway.
The principal consultants
The people behind the platform
Forty-one people across nine countries, building the data operations layer we wanted back when we were the ones carrying the pager.
