Diagnostic

When a diagnostic fits

Most diagnostics start with one of a few moments. The warehouse bill grew faster than the business and nobody can explain the difference. Two teams bring different numbers for the same metric to the same meeting. A renewal or a new vendor contract is due, and nobody wants to sign it on instinct. Or leadership has asked for an AI plan, and the honest first question is whether the data underneath can carry one.

In each case you need an outside read that is fast, specific, and written down. You do not need a transformation program.

What I look at

• Cost. Warehouse and cluster spend by workload, idle compute, oversized warehouses, pipelines that refresh more often than anyone reads the result, and whether spend can be traced to a team at all.
• Architecture. How data moves from source to the numbers leadership sees, where it gets copied, and where a single failure would stop reporting.
• Governance. Who owns each important dataset, whether lineage exists outside people's heads, and who can see regulated data.
• AI readiness. Whether your metric definitions, access controls, and metadata could ground an AI assistant, or whether it would repeat today's inconsistencies faster.

I read the platform as it actually runs, from query history, billing exports, and pipeline code, rather than from the architecture diagram.

What you get

A written findings memo. Every finding has an owner, an estimate of the effort to fix it, and a place in a fix-first order, so the week after the diagnostic is already planned. We close with a readout for your leadership team, and the memo is yours to keep.

How the two weeks run

1. Days one and two. A kickoff call, read-only access, and conversations with the people who run the platform day to day.
2. Days three to eight. I work through billing, query history, pipeline code, and access policies, and check what I find against what people told me.
3. Days nine and ten. The memo, then the readout.

What it is not

A diagnostic changes nothing in your accounts. It is a read, not a build. If you want the findings fixed, that is a Build, and the memo becomes its scope.