Getting Budget for a Process Fix When the C-Suite Does Not Yet See a Process Problem
A VP who needs headcount, tooling, or consulting spend to fix a broken workflow faces one problem before the ask: she has to make the dysfunction visible to people who have never lived inside it. This is a framework for translating operational drag into financial terms a CFO will act on, specific to retail process improvement.

Quick answer
It is Sunday at 8:40pm. You open the laptop, pull up last week's performance report, and start reformatting it the way the SVP expects: three columns, variances flagged in red, plain-sentence narrative under each section. You have done this forty-six times. You know exactly what it needs to look like because you built the format yourself, over the first few weeks in this role, and then kept doing it because writing it down felt like it would take longer than just doing it again. You close the laptop at 10:15pm. You tell yourself you will think about how to fix this next week. I have watched this loop run for months inside organizations I work with, and I have run a version of it myself. The person who built the process and understands it best is the same person absorbing its cost most directly, and she is the last one to put a dollar sign on what it is taking from her. That is what this piece is about. Getting budget for a process fix is a translation problem before it is a financial problem. You have to convert what you are living inside every Sunday night into language that lands on a different part of the CFO's desk. This is the framework for doing that.
TL;DR
What the data says before you read further.
Retail operational inefficiency costs rose from 4.5% of gross sales in 2024 to 5.5% in 2025 to 6.4% in 2026 (Coresight Research, 2026)
That figure rose from 4.5% in 2024 to 5.5% in 2025 to 6.4% in 2026, totaling $196.4 billion across key U.S. retail sectors, even as technology investment increased (Coresight Research, 2026).
Operations VPs spend the majority of their week on reactive and administrative tasks, leaving little scheduled time for process design or strategic planning
Cross-functional coordination alone consumes 26% of an operations VP's week, crowding out the analytical work needed to build a budget case (McKinsey Operations Practice, 2025).
Manual reporting is the most recoverable time leak
Operations leaders who automate routine reporting redirect 4 to 5 of those recovered hours per week toward process improvement within the first quarter after implementation (McKinsey Operations Practice, 2025).
CFOs now require a business case with clear cost or efficiency impacts before approving any material AI spend
A technology pitch without a financial baseline fails before it reaches the committee (Optimum Corporate Solutions, citing CFO Dive, 2026).
Among senior executives assessed for burnout, nearly half reported the strain had already affected their decision quality (CEREVITY clinical review, 2025-2026)
The leader preparing the budget case is frequently operating at reduced judgment capacity precisely when that case needs to be its sharpest (CEREVITY clinical review, n=298, 2025-2026).
A phased pilot is easier to approve than a full-scale request
It also produces real data that strengthens the case for scaling rather than asking a CFO to absorb all project risk before any value has been demonstrated (Optimum Corporate Solutions, 2026).
Why the ask stays stuck
The Sunday night report is a measurement. It tells you exactly what an undocumented process costs: time you will not get back, judgment you will not apply to anything else that week, and a low-grade resentment that builds across forty-six iterations. This particular process has never been documented partly because you have not had time, and partly because writing it down means acknowledging it needs to be fixed, and fixing it means making an ask, and making the ask means quantifying how many months you have been absorbing a cost that the business should have been carrying. That is the admission that feels like a performance risk. So the report goes out every Monday, and the conversation about fixing it moves to next quarter. I have seen this dynamic in rooms across retail organizations, and I have watched it play out the same way every time. Someone says, in a meeting, that the process needs attention. Someone else says they can take that offline. And then, as often as not, the offline conversation never happens, or it happens once and no one follows up, and three months later the same person is still running the same workaround because, as the room has agreed without saying so explicitly, we have always done things this way. <cite index="42-2,42-3">An automation business case fails for one simple reason: it sounds like a technology upgrade when it should read like a capital allocation decision.</cite> The CFO who controls the budget is not living inside the Sunday night. She reads P&Ls. She approves capital allocation decisions. She has seen inflated ROI projections, and a single unverifiable number will end the conversation before it starts. The work of getting budget is the work of translating what you are living into language she already tracks. That is a different skill from describing the problem, and it starts earlier than the business case document.
The four-line current-state cost baseline
Before the CFO will act on a number you give her, she needs to believe you measured it rather than estimated it. <cite index="40-8,40-9">The current-state cost baseline is the most important element of a business case for a CFO. Without that baseline, the ROI calculation has no anchor and the case reads as speculative (Procright, 2026).</cite> The Sunday night report is a good place to start because you already know every step. Time one full cycle, including the pull, the reformatting, the narrative pass, and the read-through before you send. Multiply that by the weeks you have been doing it. That number, multiplied by your fully loaded hourly cost, is the first line of your baseline. For a retail operation, four lines build the complete picture.
Labor cost of the broken process
Name the process. Count the people who touch it. Time each step, including the reformatting, the manual checks, the email chains that fill the gaps between systems. Multiply hours by fully loaded labor cost. A number you measured is a number the CFO can verify.
Error and rework cost
Manual processes generate errors. Errors generate rework. Rework generates delay. Quantify one downstream consequence: a delayed promotion recap that caused a markdown decision to miss its window, an inventory count that required a recount, a report reissued after a formula error. Attach the operational cost of that one event and multiply by frequency.
Opportunity cost of your time
<cite index="46-4,46-5">Operations leaders spend roughly 6.2 hours per week on activities with low decision value, representing about 12% of a 51-hour workweek. Organizations that automate routine operational reporting see their operations leaders redirect 4 to 5 of those recovered hours toward process improvement and team development within the first quarter after implementation (McKinsey Operations Practice, 2025).</cite> Name what process improvement work is not happening because those hours are consumed by report formatting. That is the cost of doing nothing.
Risk exposure from single points of failure
If the institutional knowledge for this workflow lives in one person's head, the company carries undocumented operational risk. That risk has a financial value: cost to recruit and ramp a replacement, cost of a process breakdown during a transition, cost of a compliance gap if the process touches auditable data. Document that exposure in those terms.
What retail operational dysfunction actually costs, in numbers the CFO tracks
The macro number gives context. <cite index="2-4">Retailers are accelerating investments in store intelligence technology at record levels, yet operational inefficiencies continue to rise, costing 6.4% of gross sales annually, up from 5.5% in 2025 and 4.5% in 2024, totaling $196.4 billion across key retail sectors (Coresight Research, "The State of In-Store Retailing 2026").</cite> Investment is going up. Inefficiency costs are going up faster. That is the opening line of a CFO conversation, not a footnote. The micro number is what closes it. A mid-sized consumer goods brand with three people touching weekly business reporting, each spending three to four hours across the week, spends between £540 and £720 per week on report compilation alone. <cite index="36-4">Over the course of a year, that is £28,000 to £37,000 spent purely on pulling data together and checking reports (Sontai, 2025).</cite> Scale that to a retail operation with multiple reporting streams, promotional cadences, and channel complexity, and the number grows without the work becoming any more valuable. <cite index="9-4,9-5">Operational inefficiency costs the average mid-market company 23% of annual revenue, according to research spanning 800 organisations across six sectors (Global Operations Research Consortium, April 2026). Only 19% of those organisations have conducted a formal inefficiency audit in the past 24 months, leaving the majority operating without a complete cost picture.</cite> That last figure is the structural reason the C-suite does not see a process problem: nobody has measured it and handed them the number. For retail specifically, <cite index="5-9,5-14">operational inefficiencies account for $12 billion, or 13% of total retail shrink. In some categories, operational losses account for up to 70% of store shrink, waste that goes unnoticed until it shows up on the P&L (Appriss Retail, 2026).</cite> The VP knows this because she sees where the variance lands every week. The CFO sees it only when it has already hit the income statement.
Translating the baseline into CFO language
<cite index="41-5,41-6">Most operational leaders present departmental metrics and compete with other divisions for limited resources, rather than making a case around total business impact. Securing CFO-level approval requires translating operational metrics into financial impact statements (Appriss Retail, 2026).</cite> Three translations do most of the work. First, convert hours to dollars. A VP earning $180,000 in total compensation costs roughly $90 per hour. Two hours of weekly report formatting is $180 per week, $9,360 per year, in senior labor spent on a task with no analytical value. That is a number a CFO can audit. It is also the number that makes the Sunday night visible to someone who has never spent one. Second, connect the broken process to a metric the CFO already tracks. Inventory variance, markdown rate, promotional lift accuracy, days of supply: pick the one the CFO reviewed most recently and show how the broken process contributes to variance in that number. <cite index="2-7">Research shows that technology sequencing, not investment alone, is what separates value creation from value erosion (Coresight Research, 2026).</cite> The process breakdown is a sequencing problem with a financial consequence already in the data. Third, frame the ask as revenue protection. <cite index="41-6,41-7">Siloed departments cannot see interconnected patterns, such as up to 80% of retail losses stemming from non-fraud sources like damaged goods, process breakdowns, and inventory errors. Securing CFO-level approval comes from treating budget conversations as business intelligence briefings rather than departmental requests (Appriss Retail, 2026).</cite> A departmental ask competes for discretionary budget. A revenue protection case lands on a different part of the CFO's desk.
What a CFO-ready business case looks like in retail
<cite index="38-2">CFOs now require a business case with clear impacts either in the form of cost savings or efficiency gains before approving any material AI spending (CFO Dive, cited in Optimum Corporate Solutions, 2026).</cite> The structure that gets approved has five components. First, the current-state cost, built from the four-line baseline above. Second, the proposed intervention, scoped narrowly: one process, one team, one workflow. The Sunday night report is a usable scope. <cite index="38-6,38-8,38-9">Propose a pilot scoped to one process or one department, with a defined measurement window and a specific dollar or hour figure attached to success. A phased approach is generally easier to approve than a single large request for full-scale investment. It also produces real data that strengthens the case for scaling, rather than asking a CFO to accept all the risk before any value has been demonstrated (Optimum Corporate Solutions, 2026).</cite> Third, the ROI projection, in ranges rather than point estimates. Finance committees have seen inflated projections before. A conservative, base, and aggressive scenario signals rigor. For context on what retail automation delivers: <cite index="11-20">89% of retailers report increased revenue and 95% report decreased operating costs after implementing AI (Ringly.io, citing industry survey data, 2026).</cite> Use sector benchmarks to anchor the range, not to promise the ceiling. Fourth, the measurement plan: which metric, measured how, over what window, with what constitutes success and what constitutes a stop signal. Fifth, the total cost of ownership. <cite index="15-4,15-5">Hidden costs include data integration, often 20 to 30% of project budget, staff training, and ongoing model maintenance. Budget an additional 25% beyond vendor quotes for a successful implementation (ManyForce, 2026).</cite> A CFO who discovers hidden costs after approval does not approve the next ask.
The burnout lens: why the most qualified person is often the least prepared to make this case
There is a structural contradiction sitting inside this problem, and it is worth naming directly. You have been reformatting that report for eleven months. You know the downstream consequences of a delayed recap. You know the variance it creates. You know the institutional knowledge that lives in your head and nowhere else. You are the most credible person in the organization to make this case. You are also the person least equipped to build it right now. <cite index="20-2">In a clinical review of 298 senior executives and CEOs, 71% met criteria for significant burnout on structured assessment, 63% reported deliberately concealing the severity from their boards, and 49% said the strain had already affected their decision quality (CEREVITY clinical review, 2025-2026).</cite> The person preparing the budget case is frequently operating at reduced analytical capacity precisely when the case needs to be its most precise. <cite index="27-8">Deloitte's 2025 Workforce Intelligence Report found that mental fatigue, cognitive strain, and decision friction have now surpassed workload volume as the leading indicators of burnout.</cite> The report formatting is a symptom of a workflow that was never designed to protect your time, and the hours it takes every Sunday are hours you are not applying anywhere else. <cite index="25-2,25-3">Research found that burnout can coexist with visible innovative activity, while significantly weakening the deeper capacity required for complex thinking, sustained focus, and sound judgment. Busyness can remain high even as innovation capacity begins to decline (unBurnt, April 2026).</cite> The report goes out every Monday. What is not visible is the judgment you are not applying to anything else because the formatting consumed the last hour of your Sunday. This belongs in the business case, written as a risk statement: the operational leader responsible for executing this improvement is currently spending X hours per week on the process this investment would eliminate. That is X hours per week of strategic capacity being consumed by administrative work. Write that sentence. Most operations VPs leave it out because naming it feels like admitting something they would rather not admit. Naming it is the beginning of the case.
The sequencing question the C-suite will ask, and how to answer it
Even a well-constructed business case will face one question before it moves: why now, when other priorities are competing for the same budget? <cite index="1-4">In-store inefficiency costs rose from 4.5% of gross sales in 2024 to 5.5% in 2025 to 6.4% in 2026 (Coresight Research, 2026).</cite> The cost of the broken process compounds as the business grows, as channel complexity increases, as promotional cadences intensify. <cite index="36-5,36-6,36-7,36-8">Manual reporting scales badly as the business grows. As new retail partners, new product development, and additional data sources are added, the reporting workload grows with them. What starts as a few reports becomes a daily sales update, a permanent admin task, a background task for senior staff. The cost does not stabilize. It increases with assortment complexity, promotional activity, and channel mix (Sontai, 2025).</cite> The question the CFO is weighing is whether fixing the process now costs less than the accumulated drag of leaving it broken for another twelve months. With the trend line attached, the answer is almost always yes. <cite index="34-9,34-10">Businesses looking to cut wasted effort do not need to tackle every workflow at once. With most recoverable time concentrated in a small share of processes, a targeted approach yields the biggest returns, even as a long tail of short, manual processes remains harder to address (IT Brief, citing process audit research, 2026).</cite> The ask is one process, scoped tightly, with a measurement window and a stop signal.
What could go wrong
The baseline numbers are soft and the CFO notices
Estimates rather than measured figures undermine the entire case. If you do not have time-diary data for the broken process, run one cycle with a stopwatch before submitting the case. One measured data point is stronger than ten estimates.
The ask is scoped too broadly
A request that covers three workflows, two teams, and a new data platform reads as speculative. Scope to one process, one team, one measurement window. The pilot result is what gets you the broader investment.
The ROI projection uses vendor-provided numbers
Finance committees have seen inflated vendor projections before. Use sector benchmarks from independent research as the range anchor, then apply a conservative discount. A projection you can defend is more valuable than a large number you cannot.
The case is presented as a departmental request rather than a business impact
If the case competes for discretionary budget against other departmental asks, it will be evaluated against other departmental asks. Connect the broken process to a metric the CFO already tracks and the conversation changes category.
The total cost of ownership is understated
Data integration, change management, training, and ongoing maintenance costs are regularly excluded from initial requests. Including them signals rigor. Excluding them produces a CFO who feels misled after approval, which is a worse outcome than a slower approval.
The case is built while depleted
A business case drafted on a Sunday night after eleven months of the same report carries the analytical quality of a Sunday night after eleven months of the same report. Block time earlier in the week, before the week fills. Write the case inside that window. The document will say something different.
The J.Caresse point of view
Here is what I keep seeing underneath the cases that do not get made. The VP who has been living in this workflow knows exactly what it costs. She could build the case in a weekend. She has the numbers, the downstream consequences, the institutional context the CFO does not have. She has built dozens of business cases over her career and she is good at it. She has not built this one because building it requires her to admit, in writing, that something has been broken for eleven months on her watch. That she has been absorbing the cost personally rather than surfacing it as a business problem. That the reason it is not documented is that she is the one who knows how to do it, and writing it down would mean acknowledging it should have been fixed by now. That admission feels like a performance risk. So the report goes out every Monday. The conversation moves to next quarter. The cost compounds. The line I want you to be able to say to yourself the next time you close the laptop at 10:15pm: the capacity I need to fix this is being consumed by the thing I need to fix. That is the sentence that belongs in the business case. It is also the sentence that makes the ask real rather than theoretical. The process is undocumented because documenting it requires naming what it has cost. The ask has not been made because making it requires quantifying how long you have been tolerating something you knew was wrong. One honest number on a page changes both of those things. What this process actually costs, in dollars, per week, for the last twelve months. That number is where the business case starts. Write it down before you let yourself think about anything else.
Key takeaways
One action this week. The rest can follow.
Write one number down before the week ends
Time one full cycle of the process you are carrying: the pull, the formatting, the narrative pass, the read-through. Multiply that by the weeks you have been doing it. Multiply by your fully loaded hourly cost. Write that number down. That is the first line of your baseline, and it is the number that makes the Sunday night visible to someone who has never spent one.
Build the current-state cost baseline from four lines
Four lines build the complete baseline: labor cost of the broken process, error and rework cost, opportunity cost of your time, and risk exposure from single points of failure. Without that baseline, the ROI calculation has no anchor and the case reads as speculative (Procright, 2026).
Translate operational terms into financial terms
Hours become dollars. Workflow gaps become variance in a metric the CFO already tracks. The ask becomes revenue protection rather than a departmental budget request. That translation is the work, and it is different from describing the problem.
Scope the ask to one process with a defined measurement window
A pilot with a specific dollar or hour figure attached to success, and a defined stop signal, is easier to approve than a full-scale investment. The Sunday night report is a usable scope. The pilot data is what builds the case for scaling.
Use the trend line to answer the why-now question
Retail operational inefficiency costs rose from 4.5% to 5.5% to 6.4% of gross sales in three consecutive years (Coresight Research, 2026). The cost of doing nothing is not flat. Frame the delay as a compounding financial decision.
Name your own capacity cost in the case
Write this sentence in the business case: the operations leader responsible for executing this improvement is currently spending X hours per week on the process this investment would eliminate. Most operations VPs leave it out. Put it in.
Bring these ideas into the room.
If this essay sounds like the conversation you're sitting with, Jessica responds personally to every inquiry.
More insights.

She Knew the Pilot Was in Trouble in Week Three. She Did Not Say So Until Week Eleven.

Before You Select the Tool, Answer These Three Questions about your data
