TL;DR: This is not a story about a bad process. It is a story about a workflow that was never designed to do what the business now needs it to do. Here is a minute-by-minute account of what answering a business question actually costs.
It is Wednesday morning. The operations director sends a message to the FP&A manager. Customer acquisition costs seem to have moved significantly in the last few weeks. Can finance confirm whether that is real and what is driving it?
It is a reasonable question. It is the kind of question finance exists to answer. The data is almost certainly in the systems. And for the FP&A manager reading that message, the next three days look entirely predictable.
Not because the team is inefficient. Not because the systems are particularly poor. But because the workflow that sits between a business question and a credible finance answer was designed for a different era and has never been fundamentally rebuilt for the speed at which the modern business operates.
What follows is an account of those three days. Not a hypothetical. A description of what is happening in mid-market finance functions every week across thousands of businesses.
Wednesday: Finding the Data
The FP&A manager's first task is not analysis. It is archaeology.
Customer acquisition cost is a metric that exists at the intersection of marketing spend and new customer volume. The marketing spend data is in the ERP, spread across several cost categories: digital advertising, agency fees, event costs, and sales team compensation attributable to new business. The new customer volume is in the CRM. The ERP and the CRM do not automatically talk to each other in a way that produces a clean customer acquisition cost calculation.
The FP&A manager opens the ERP and exports the relevant cost categories for the period in question. This takes thirty to forty-five minutes because the chart of accounts is not perfectly aligned to the business's current cost classification, and some spend that should be included in customer acquisition cost is sitting under a general marketing line that needs to be manually split.
The CRM export takes another twenty minutes. The data needs to be filtered to new customers only, excluding renewals and upsells, and the CRM's definition of a new customer does not perfectly match the finance function's definition, which creates a reconciliation requirement before any analysis can begin.
By mid-morning, the FP&A manager has the raw data. It has taken roughly two hours to reach this point. No analysis has been done.
Wednesday Afternoon: Reconciliation
The ERP export and the CRM export do not agree on the first pass. The total cost in the ERP includes a category that the prior calculation excluded. The new customer count in the CRM includes a cohort that was acquired late in the prior period and should arguably be attributed there rather than to the current period.
These are not errors. They are the normal ambiguities of financial data that sits across multiple systems with different update schedules and different definitional conventions. Resolving them requires judgment, and judgment requires time.
The FP&A manager creates a reconciliation tab in Excel. The discrepancies are documented. Decisions are made about the correct treatment of each ambiguous item. The decisions are conservative, consistent with prior period methodology, and defensible if challenged. This takes three to four hours.
By end of day Wednesday, the data is clean. A number is emerging. Customer acquisition costs have moved. The movement looks real rather than definitional. But the analysis of why it happened has not yet begun.
The Harvard Business Review has documented that companies with fragmented financial data systems spend sixty-five percent more time on report preparation than those with integrated systems. This Wednesday is a specific example of that cost being paid in real time.
Thursday: Building the Model and Looking for Causes
Thursday is the analytical day. The FP&A manager builds a model in Excel that breaks customer acquisition cost into its components. What happened to spend? What happened to volume? Which channels moved and which were stable? Is the change driven by higher spend on a productive channel or lower volume from a channel that has become less effective?
This is the work that finance professionals are trained for. It is where genuine analytical skill is applied. It produces real insight. For an experienced FP&A manager, it takes four to six hours to do well.
The model is built. The picture is becoming clear. Digital advertising spend increased while new customer volume from that channel declined, suggesting a deterioration in conversion efficiency rather than a strategic decision to increase acquisition investment. The cost per acquisition in the direct sales channel is flat. The headline movement is concentrated in digital.
The FP&A manager has an answer. But it cannot be shared yet. The model needs to be checked.
Thursday Afternoon: Checking for Errors
Any finance professional who has experienced the consequence of sharing an incorrect analysis with a business leader understands why this step is not optional. Excel models break. Formulas reference the wrong cells. A filter applied incorrectly in the reconciliation step can misstate the headline number by a material amount.
A second analyst reviews the model. Two items are queried. One is a definitional question about how a specific marketing cost was categorised. One is a formula that references the wrong period in one column. Both are resolved. The model is confirmed correct. This takes two hours.
Friday: Writing It Up and Getting It Out
The operations director needs context, not a spreadsheet. The findings need to be communicated in a format that works for a leadership audience. A short document is drafted: the headline finding, the driver breakdown, a view on whether the trend is likely to continue, and a recommendation for what the commercial team should review in response.
This writing step genuinely adds value. A well-framed narrative that connects a cost signal to a commercial recommendation is exactly what finance should be producing. It takes one to two hours.
By Friday afternoon, the analysis is shared. Three days after the question was asked. The operations director reviews it and asks a follow-up: is this pattern showing in any other acquisition channels we have not looked at yet?
The cycle begins again.
What the Business Experienced
From the operations director's perspective, a question asked on Wednesday morning received an answer on Friday afternoon. A two and a half day gap between a question and a response about something that may already be impacting current-period performance.
That gap is not unusual. KPMG research found that eighty-seven percent of finance teams spend significant time reconciling data discrepancies rather than generating insight. The three days described above are a specific instance of where that time goes in practice.
McKinsey's research is direct about the strategic implication: you cannot be a genuine business partner if you are spending eighty percent of your time on data assembly and reconciliation. The Wednesday and Thursday described above are that eighty percent. The Friday afternoon document is the twenty percent that reaches the business. The ratio is inverted from what it should be.
What Three Minutes Looks Like
The three-minute version of the same answer exists. It requires a different architecture, not better tools inside the existing one.
When actuals are monitored continuously, the FP&A manager does not start the analysis on Wednesday morning. The system has been watching customer acquisition cost as the underlying data has moved. When digital conversion efficiency started declining in week two of the period, the signal was visible then. The channel-level breakdown was already isolating the movement. The context was already being built.
When the operations director asks the question on Wednesday morning, the FP&A manager reviews what the system has already assembled. They confirm the analysis is correctly framed, add the commercial judgment about what the conversion efficiency decline likely reflects, and share the response within the hour.
The data gathering, reconciliation, model building, and error checking that consumed the three days are not eliminated. They are continuous background processes rather than a reactive workflow triggered by a business question. The finance team's cognitive effort goes to interpretation and recommendation rather than assembly and verification.
That is not a marginal improvement on the existing workflow. It is a different relationship between the finance function and the business it is supposed to serve.
Uptio continuously gathers, reconciles, and contextualises actuals so that when a business question arrives, the analysis is already forming rather than just beginning. Three days becomes three minutes. The work that remains is judgment, not assembly. Learn how Uptio works.