Consulting firms have a profitability problem, and it isn’t driven by lack of demand.
Across the Big 4, management consulting, and tech consulting firms, EBITDA margins fell to 9.8% in 2024, the lowest in over a decade. Billable utilization slipped to 68.9%, under the 75% line at which firms start losing money on their people. Revenue growth slowed to 4.6% year-over-year, barely half the five-year (’19–’24) average of 8.7%. Yet deal pipelines grew 8% in dollar value. The demand is there, but the engagement economics are under pressure.
This headroom is sizable. For a billion-dollar firm, moving EBITDA from 9.8% toward a top-quartile 15% is $50M of operating income recovered annually. One of our largest customers puts the number at $37M for every day of DSO released back to the partnership.
Ironically, the answer sits in the Office of the CFO. The finance stack hasn’t materially changed in a decade while the demands on top of it have doubled. Seventy-two percent of professional services finance leaders name data integration as their top pain point; 63% cite reporting and 49% cite forecasting, among the highest figures across the services industry. The firms selling digital transformation to clients are running their own finance operations on very different stacks.
The dynamics of the partnership model make this problem hard to solve. Practice leaders run semi-autonomous P&Ls, managing partners own client relationships, and the shared services stack spans across the partnership. Investment in shared infrastructure requires aligning diverse partner and client priorities. It’s a coordination problem as much as a technology one, and margin pressure is often what finally gives leaders the mandate to solve it together.
What keeps consulting CFOs up at night
Ask a CFO in this industry what their teams spend their week on, and five workflows come up every time.
Forecasting firmwide billables and expenses, cut by service line, office, and practice area. This is what the partnership lives and breathes. Missing this number by basis points erodes the partner payout pool by millions.
Reporting and analytics for practice area reviews. Partners want their numbers sliced granularly, and they want them yesterday. Most of the data-wrangling gets outsourced offshore, which means the PA leader sees the report a week to ten days after the month closes.
Chasing client invoices. Millions sit trapped in unbilled WIP because partners are slow to clear timecards or sign off on bills. Every week of slippage is a week of cash the firm has effectively lent to its clients at zero interest.
Procure-to-pay. Vendor onboarding, T&E approvals, expense outliers surfaced after a project has already closed, long after the damage is done to the margin.
Modeling partner equity. Retirements, new admits, rundowns, capital contributions. Every cycle is a multi-month Excel exercise that defines take-home pay for the senior-most people in the firm and cannot afford to be wrong.
Each of these workflows reaches into Salesforce, SAP, Workday, Concur, and several spreadsheets. The finance team is expected to manually stitch answers together from systems never designed to talk to each other.
Why this is so hard today
Four structural problems sit beneath those workflows.
Data silos are the most obvious. Pipeline lives in Salesforce. Actuals live in SAP. Headcount and billing rates live in Workday. Partner equity often lives in a spreadsheet that reports to nobody. No one sees a unified view across transactional and analytical systems, and finance teams spend the first two weeks of each month reconciling these.
Dashboard creep is real. Every partner wants their own view of reports. Tech builds it. Six months later the firm has hundreds of dashboards. No one agrees on what the numbers mean. Revenue, utilization, margin, and client profitability are often calculated differently by practice, region, partner, or reporting team. Once those definitions drift, every report becomes debatable, Finance spends its time reconciling numbers instead of explaining performance, and partners rebuild their own view of the business in Excel.
Demand management is fragmented and tricky. Partners need fast answers on clients, practices, forecasts, and margins, but Finance often cannot answer those questions directly from trusted, governed data. So each new ask gets routed to Tech, a backlog forms, and by the time the answer comes back, the decision has already been made.
Manual work keeps Finance in cleanup mode. Analysts spend their mornings reconciling pipeline, invoices, contracts, and expenses instead of explaining margin, forecast risk, and cash flow. This is work a well-built pipeline should do in the background. Instead, it’s what your senior FP&A analysts open their laptops to every morning.
McKinsey finds that data users spend 30 to 40 percent of their time searching for data and another 20 to 30 percent cleaning it. In a business where the product is people, that is a drag on margins every single month.
How Databricks enables a modern finance function
Image: CFO Control Center landing page with persona toggle and Genie-powered agentic chat
It starts with a single source of truth. Lakeflow creates a live, governed view of SAP, Salesforce, Workday, and Concur, while Lakehouse (or Lakehouse-based applications) provides the transactional backbone for finance apps that read and write in real time. Unity Catalog handles lineage and access across both. Pipeline-to-GL reconciliation stops being a monthly fire drill, and accrued revenue versus forecast becomes visible the day after accrual, not three weeks later.
Atop that layer sits Genie, which lets Finance leaders ask “why” questions. “Why did the Chicago office trail New York on EBIT this quarter?” “What assumptions do I change in my forecast to better predict expenses?” “Why do I have more 60+ day invoices in Feb vs. Jan?” Each query pulls from actuals, pipeline, and headcount. What took an offshore analyst three days now takes 30 seconds, and the partner gets the answer themselves.
Image: Genie answering a “why” question with root cause across SAP, Salesforce, and Workday
The same platform serves persona-driven views partners actually trust. A Head of Finance sees DSO, receivables aging, and T&E variance. An Office Managing Partner sees EBIT coverage and pipeline health for their region. A Practice Leader sees realized margin by cohort. Critically, they can see the SQL and source tables behind every number. The shadow P&L problem goes away because the central view has the granularity that sent partners into Excel in the first place.
Since analytics and workflows live on the same platform, you can build apps right where your data sits. Lakehouse-powered finance apps can turn a flagged invoice, a T&E breach, or an off-target practice area into a nudge to the responsible partner, with the reply or approval written back in real time. Insight becomes action without leaving the screen.
Image: “Top Unpaid Invoices” table with Collection Nudge workflow and AI-generated email modal
Why do modern CFOs prefer Databricks over the rest?
We appreciate that there is no shortage of analytics platforms or planning tools today.
Four reasons why Databricks wins with finance leaders within professional services:
You don’t rip and replace. Big 4 and consulting firms have spent a decade investing in core systems for financials, engagements, people, and T&E. Databricks sits on top of that stack and unifies it, rather than asking Finance and Tech leaders to revisit every ERP decision they’ve already made.
You build apps where your data already lives. A partner equity model, a practice margin app, a DSO tracker — each built directly against the governed data layer, without exporting, without ETL, without a shadow copy that goes stale by the next reporting cycle. For firms running partner equity modeling every cycle, that removes weeks of manual work and the audit headache that comes with it.
You’re not locked into a single AI model. Forecasting wants one kind of model. Invoice automation wants another. Partner equity wants a third. A one-model strategy today is a one-model liability next year. The CFO’s office will run dozens of AI workloads, and none should require rebuilding the foundation.
Governance, audit, and lineage are built in. Your clients are banks, insurers, healthcare providers, and governments, and they audit your controls. Unity Catalog gives you end-to-end lineage from source transaction to KPI, row-level security by persona, and the access logs, lineage, and change history your auditors already ask for, captured automatically. The same standard of control you sell into regulated industries can now run your own back office.
Showing outcomes in practice
A global consulting firm used Databricks’ Genie to cut cash forecasting cycles by 3 to 5 days and reduce FTE hours on the reporting cycle by 80%. Their CFO described it simply:
“I didn’t just want to talk to my data. I needed my data to start talking back to me. What used to take a week takes minutes.”
At their scale, every day of DSO improvement accelerates roughly $37M in cash flow back to the partnership.
We’ve also done this ourselves. Databricks’ own Office of the CFO unified ERP, CRM, HRIS, and planning onto one governed layer. Our revenue close dropped from 15 days to 8, a 52% reduction. We saved approximately 50 hours per person per month, or 1,280 hours overall. All of our revenue is now calculated in Databricks, with full SOX audit readiness through Unity Catalog.
What finance leaders need to do to move from vision to value
This isn’t a multi-year transformation. A typical CFO implementation runs 10 to 12 weeks end-to-end. Foundation and data sharing in weeks one to three. Medallion transformations and KPI layers in weeks three to six. Genie and app deployment in weeks six to nine. Hardening and cutover through weeks nine to twelve.
For finance leaders reading this, three imperatives are worth exploring this quarter:
- Pick the one workflow that is most painful and least defensible, whether that’s revenue close, unbilled WIP, T&E leakage, or practice margin drill-down. Quantify the FTE burden and the cash or margin at stake. The ROI depends on how sharply you scope your pain.
- Run a half-day workshop with your Databricks account team to map that workflow against the reference architecture and size the build.
- Ask to be introduced to a peer who has already done it. We’ll make the connection.
The firms that make this shift don’t just recover margin. They start running their finance function the way they tell their clients to run theirs.
