Fixed fee · Two weeks · Scorecard either way
Find the Databricks spend that is not working for you
Workspaces drift. Clusters get sized for a load that never arrived, jobs that should be serverless still run on all-purpose compute, schedules outlive the person who wrote them, and Unity Catalog coverage stops halfway. Two weeks, a fixed fee, and a scorecard whether or not you do anything about it.
- Length
- Two weeks
- Who it is for
- Teams already on Databricks whose bill is growing faster than the work
- Bench
- 80 Databricks-certified engineers
What we inspect
- Compute and workload cost patterns, from system tables where you have them
- Cluster and warehouse sizing, and which jobs are serverless candidates
- Job failure and retry patterns, and what they cost in reruns
- Unity Catalog coverage and privilege hygiene
- Orphaned compute and schedules nobody owns
- Model serving and AI Gateway spend, where they are in use
What you get
- 01A written scorecard with findings ranked by severity
- 02Estimated savings against each finding, with the reasoning shown
- 03A thirty, sixty and ninety day remediation order
- 04A fixed-scope proposal for the remediation, if you want us to do it
FAQ
Questions about the Health Check
What access do you need?
Read access to the workspace and, where you have them, system tables. We do not need production data, and we do not need write access to run the audit. If your security process needs a named scope, we will write one before anything is granted.
What if you find nothing worth fixing?
Then you have a scorecard saying so, which is worth having in front of a CFO asking about the bill. The fee is fixed either way. We would rather tell you the platform is healthy than manufacture findings to justify a remediation.
Do we have to use you for the remediation?
No. The scorecard is yours and it is written so your own team can act on it without us. We quote the remediation separately, and plenty of clients do the straightforward parts themselves and bring us in for the rest.
How is this different from the cost dashboard we already have?
A dashboard tells you what you spent. This tells you which of it bought nothing, why, and what to change. That judgement is the deliverable, and it comes from engineers who have run these platforms rather than from a billing export.