Many executives I interact with believe deferring an automation or AI investment is a neutral act. It is not. It is a choice to keep funding the current process design, and that process design has a price tag that grows every single day.
I want to be precise about what I mean, because this is a point that gets misunderstood. I am not positing that every organization should be automating everything, or that all of the AI urgency messaging you see everywhere right now is correct. Some of it is, some if it is not. What I am suggesting is the question many organizations never ask is the most important one: what is our current process costing us right now, and are we comfortable with that answer?
In my experience, once organizations run that number, the conversation changes fast. And, you have a baseline to compare against, which put you light years ahead of most people when taking a proposal to your CFO.
The Budget Is Already Committed
Here is the misconception that does the most damage. When a leadership team decides to defer a process improvement initiative, they tend to frame it as cost avoidance. No project spend means no cost. That logic sounds reasonable until you realize the budget is already committed; it is just going toward labor, rework, delays, and fragmented handoffs instead of improvement.
Deloitte found that over half of organizations had not calculated cost reduction from automation, and 70% had not quantified expected revenue increase from it. The real obstacle here is process analysis, not technical implementation. There is no baseline and no goal for change. The cost of the current process is invisible, so it never shows up in the conversation about whether to invest in changing it. The status quo gets a free pass because nobody is running its P&L.
This is why, when we work with clients, one of the first things we do is anchor on what the desired outcome is. Where does the organization want to go, what does the current process cost, and what will it cost to get to the desired outcome? A CFO is not interested in a shiny demo. They are interested in whether the numbers make sense. You cannot answer that question without knowing where you are today.
Five Things You Are Paying for Right Now
When I look at a process that still runs on manual work and informal handoffs, I see five costs running simultaneously. None of them appear on a project budget. All of them are real.
1. Labor drag. Slack’s Workforce Lab found that desk workers spend 41% of their time on low-value or repetitive tasks, which works out to roughly two full days each week. Apply that ratio across a process team and you are not looking at a small inefficiency. You are looking at nearly half your labor budget funding administrative overhead. The calculation is not complicated:
(people in the process) X (loaded hourly cost) X (the share of time going to work that does not require human judgment) = status quo cost
That number, annualized, is what the status quo costs you before you count anything else.
2. Delay cost. Slow cycle times and handoff gaps are treated in many organizations as a fact of life. They should be treated as a financial decision. Forrester’s 2024 US Customer Experience Index found that CX quality had reached an all-time low, and that customer-obsessed organizations grew revenue 41% faster and retained customers at 51% higher rates than those that were not. The bridge from internal process to external outcome is direct. Slow approvals, slow onboarding, and inconsistent exception handling are not internal problems. They become churn rate, pricing pressure, and increasingly unfavorable competitive position.
3. Rework. This is the one that consistently surprises people when they run the numbers. Leaders know their error rate in the abstract. They rarely convert it to a dollar figure that accounts for the full rework cycle: the case that comes back, the person who has to identify the problem, re-route it, correct it, log it, and verify the fix. Rework adds 20 to 50% to total process cost in many of the workflows we assess. That range is wide because it depends on how error-prone the process is and how expensive each error is to resolve. In my experience, the number almost always surprises the process owner.
4. Risk. This one requires some care in how it is framed, so I want to be precise. I am not saying manual processes cause breaches. I am saying that wherever sensitive data, financial controls, or compliance checkpoints run through manual judgment and informal handoffs, you have a control gap. IBM’s 2024 Cost of a Data Breach report put the global average breach cost at $4.88 million. IBM also found that organizations using AI and automation reduced breach costs by $1.88 million compared to those that did not. The relevant question for an operations leader is not whether the process could fail. The question is what a single exception, missed review step, or miscommunication would cost, and how many opportunities for that to happen exist in a given year. One caveat is if using AI, you must make sure you have governance in place so you don’t offset gains in efficiency with sensitive data leakage.
5. Competitive position. BCG’s 2025 research found that only 5% of companies are what they call future-built, 35% are scaling AI and generating value, and 60% are still seeing almost no material result. The leaders are getting five times the revenue increases and three times the cost reductions of everyone else. That gap is not closing. It is widening, because the organizations that figured out the process and governance prerequisites are now compounding. Every quarter they scale, the laggards fall further behind. Doing nothing is not holding position. It is losing relative ground to organizations that solved the same problem you are sitting on.
A Word on Failed Transformation
Before I go further, I want to address something, because I have sat across from enough skeptical executives to know what they are thinking at this point. They have watched transformation projects fail. They have seen technology deployed that did not change how the business operated. And they are not wrong to be cautious. The definition of insanity is doing the same thing over and over and expecting different results.
Gartner found that only 48% of digital initiatives meet or exceed their business outcome targets. PwC found that 88% of executives struggle to capture value from technology investments, and 85% struggle to update their operating models to support a new vision. Those numbers do not argue for inertia. Rather, they shine a clear light on why organizations should seek to understand why transformation fails, which is almost never the technology.
What I see repeatedly is that the process underneath was never redesigned, the baseline was never measured, and the success criteria were never locked before implementation began. The solution works. The implementation goes live. And six months later, when the CFO asks what the results were, nobody has a clean answer, because nobody documented what the cycle time, cost, or error rate looked like before the project started. This is a discipline problem dressed up as a tech problem. The discipline is to baseline, simulate, and predict BEFORE approving a project.
Inertia is choosing not to act. Failed transformation is acting without the baseline and process analysis to stress-test projections before moving to implementation. Both are expensive. They are different problems, and the solutions look nothing alike.
What Measured Change Looks Like
The alternative to both inertia and reckless transformation is not complicated to describe, but it does require discipline to execute. Measured change starts with three things most organizations do not have before they start: a documented baseline, defined success criteria, and a measurement plan.
Without the baseline, there is no proof of value. Without success criteria, there is no shared understanding of what done looks like. Without a measurement plan, the investment has no accountability structure and the CFO will not approve it, or if they do, they will ask the uncomfortable question twelve months later and nobody will have the answer. I had this happen to me 15 years ago. Not fun!
Deloitte’s latest research put it clearly: the most successful organizations redesign jobs and workflows rather than layer AI onto legacy processes. That is the sequencing that works. Document the process, baseline the cost, identify the highest-value interventions, simulate the results, prove value in a constrained pilot, then scale what works. It is not exciting. It is also the approach that produces defensible results and will make you look like a Transformation rock star.
Caution is healthy here. I want to be clear about that. An organization that has seen projects fail and now demands a baseline, a governance model, and a clear proof-of-value scope before committing budget is making the right call. That scrutiny makes projects better. The problem is when caution becomes paralysis; when automation has been on the roadmap for three or four years with no structured first step, no criteria for moving forward, and no mechanism for making the evidence case. Deloitte found that 22% of organizations still have no clear, accepted vision for intelligent automation, and 41% lack an enterprise-wide strategy. That is not caution. That is an organization quietly funding its own inefficiency while it waits for certainty that will not arrive on its own.
Running the Number
If you want to make the cost of your current process visible, the calculation has five inputs. Labor drag: people in the process times loaded hourly cost times the share of time going to repetitive or manual work. Delay cost: transaction volume times average delay times the value of faster completion or avoided backlog. Rework cost: error rate times volume times cost per reworked case. Risk cost: probability-weighted cost of a control failure, audit finding, or breach in a given year. Opportunity cost: revenue or capacity currently left on the table because the process cannot scale.
Sum those five and annualize the result. That number is what the organization is already paying, every year, to keep the current process design running. It is the denominator for every investment conversation you will have about changing it.
The tool that makes this tractable is Business Compass. Using AI, you can map the AS-IS and TO-BE processes, instrument activities with the right metrics, simulate scenarios, and generate the financial outputs your CFO needs: ROI, net present value, internal rate of return, and payback time. The math is not the hard part. The hard part is having a structured method for capturing the inputs, which is exactly what process modeling and simulation give you. We use Business Compass with every project we implement at no cost to our clients.
Where We Come In
Salient’s role is to compress the time between recognizing the problem and having a number your CFO can evaluate. Most organizations are stuck in a loop: they know their processes are slow and expensive, but they do not have the baseline data to make the investment case. The CLARITY Opportunity Lab is designed to break that loop in two to three weeks. We baseline three to six candidate processes, identify the bottlenecks and exception hotspots, produce ROI ranges, and build an executive funding pack. This is the tangible and provable evidence your CFO needs to make the decision to say Yes easy.
The front door is the Process Clarity Workshop, which is a two-hour session. What it surfaces is something most organizations find genuinely useful: there is often a meaningful gap between where the team feels the most pain and where the cost is concentrated. The loudest complaint is not always the highest-cost process. The workshop structures the conversation around five questions: what is the actual end-to-end cycle time across all variants, not just the average; what does each transaction cost including rework; what is the real error rate from system data rather than self-reporting; what share of capacity is going to fixing things rather than processing them; and what would a 20% throughput improvement mean for unit costs and the P&L. Leaders leave with a prioritized list and a shared framework. That replaces the informal debate about where to start, which is where most programs stall.
The most important point I would want any CFO, COO, or operations leader to take from this: the cost of doing nothing is not the cost of avoiding investment. It is the recurring cost of funding inefficiency, delay, risk, and missed opportunity every single day the current process stays in place.
That is the number nobody is running. It is usually the most important one in the room.
