The close needs a committed expense allocation before the evidence is complete.
Accounting protects an auditable ledger while FP&A protects a usable forecast for model-serving spend.
Who you’d be doing this for
“My VP wants the serving bill split by project today, and half these calls have nowhere defensible to land.”
Nicolas Gutierrez · ML Engineering Manager
Owns production model-serving workloads whose spend is charged back to an internal cost center.
What is at stake
Unclassified serving charges could leave more than 0.5% of monthly AI spend outside a traceable cost center. You must weigh a timely close against an allocation method Internal Audit can defend.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- close speed vs. auditability
- forecast usability vs. route-level evidence
- pipeline change control vs. unresolved usage
- cost-center precision vs. bounded exceptions
Why Databricks
Mosaic AI serving usage reaches Finance through governed datasets, so missing route attribution directly weakens cost reporting for AI workloads.
Written with these in mind
Not your kind of problem? 107 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.