If you’re a CFO in a $20M – $100M company, you don’t have the luxury of “buying the vision” and hoping it works out. You’re the person who has to fund it, defend it, and explain it when it goes sideways.
And let’s be honest. The word “transformation” often sounds like disruption. It sounds like frontline pain. It sounds like your best people getting frustrated, your customers feeling it, and your team spending months cleaning up the mess.
I’ve lived both sides of this. I’ve been a CTO inside massive retail operations like Loblaw Companies and Shoppers Drug Mart. I’ve also spent years advising mid-market leadership teams through change, when they don’t have a deep IT bench and they can’t afford mistakes.
So I’m going to write this the way I talk about it in the room.
Clear. Direct. Focused on what matters to you.
And what matters to you is simple: value, risk, and control.
CFOs aren’t anti-transformation. CFOs are anti-waste.
There’s a CFO reality that doesn’t get said out loud enough. You’ll fund technology when it makes sense. You’ll shut it down when it doesn’t.
That’s not you being “difficult.” That’s you doing your job.
A global survey of 1,500+ CFOs found 80% said top-five priorities include digital transformation. The same survey showed 71% see it as key to company success. It also said 77% will fund it when ROI is strong. And 67% refuse to waste dollars on IT initiatives that don’t move the needle.
That last one is the real headline.
You don’t want perfect technology. You want technology that creates leverage without creating chaos.
The first two questions I ask every CFO
When I sit down with a CFO, I start with two questions. I start there every time because it forces clarity.
First: What is it that you’re trying to transform within your business?
Second: How does that align to value creation?
If we can’t answer those two questions, we’re not transforming anything. We’re shopping.
And shopping is how companies end up with a stack full of tools that nobody trusts, nobody uses properly, and nobody can explain to the board.
You want to be in a different place. You want to make a decision you can defend.
The simplest question that cuts through the noise
Here’s the “old-fashioned” business word I wish IT used more when talking to Operations and Finance.
How do you make money?
I’m not being cute with that. I’m being practical.
Every company on the planet is here to make money. Period. So I follow the money. When you follow the money, you see patterns. When you see patterns, you start to see where the technology is in conflict with those patterns.
Once you see the conflict, you can remove it. That’s where the leverage is.
My “Financials First” view of transformation
At The Narrative Group, we call our approach “Financials First.” It’s not a buzzword. It’s a discipline.
It means we start with how the business creates value and how money flows through the P&L. Then we connect technology decisions to those flows.
I break the business into two big parts, because CFOs need clean framing.
Part one: the value chain
The value chain is how you deliver what customers pay for.
If you’re in manufacturing, this is how you design, build, ship, and service. If you’re in professional services, it’s how you sell, staff, deliver, invoice, and renew. If you’re in retail or distribution, it’s how you source, stock, sell, fulfill, and handle returns.
On the value chain side, the question is simple.
How productive are you at delivering the value chain today?
Where is delivery slow, inconsistent, full of rework, or dependent on heroics?
And then a second question.
Where can technology improve execution in a way you can measure?
Part two: the supporting functions
The supporting functions are the cost centers that keep the company running. Finance, HR, IT, customer service, internal operations, compliance. They matter because they either enable growth or they quietly tax it.
On the supporting side, I’m looking for a different outcome.
I want those functions to do more work without increasing labor. I want to manage, decrease, or maintain labor levels while volume grows.
That’s where CFOs often get surprised. A good investment doesn’t always show up as a flashy revenue bump. Sometimes it shows up as not needing to hire the next five people.
That’s a real P&L shift.
If you want to scale, productivity is the blocker
In Canada, in the US, in most places I’ve worked, businesses tend to have a productivity problem. They just don’t always name it that way.
They feel it as “we can’t keep up.”
They feel it as “everything takes too long.”
They feel it as “we’re hiring, but we’re still behind.”
The biggest hurdle companies face when they try to scale fast is productivity. If you can’t increase output per person, growth becomes expensive. It becomes risky. It becomes a constant scramble.
That’s why the first two levers I pull are standardization and automation.
Not because automation is trendy. Because it’s measurable.
The CFO trap: thinking IT spend lives in one place
Most mid-market businesses don’t have “an IT budget.”
They have spending spread everywhere. Software in department budgets. Contractors in project codes. Telecom in Facilities. Hardware refreshes done when something breaks. Cybersecurity tools bought after a scare.
Then somebody tries to talk about ROI, and nobody can even agree what the baseline spend is.
So the first move is always clarity. If you can’t see the full picture, you can’t manage it.
This is a big reason CFOs get frustrated with digital transformation. You’re being asked to fund something without a clean view of current costs, future costs, and where value is supposed to show up.
You deserve better than that.
The hidden cost of “cheap” IT decisions
Here’s an opinion I hold pretty strongly: the hidden cost of choosing low-cost IT providers is often the loss of scalability.
It looks cheap today. It gets very expensive later.
You pay for it when you need to integrate systems. You pay for it when you need to upgrade. You pay for it when you want to launch a new product line and the stack can’t support it without a rebuild.
And here’s the painful part. That rebuild usually happens when the business can least afford distraction.
Cutting license costs can turn into labor costs
Another trap I see constantly is the idea that you can cut software license fees and “save money.”
Sometimes you can. Often you don’t.
What I see more often is this: you cut licenses, and the business shifts the work into manual effort. Now people are doing process work by hand. Innovation slows down. Complexity grows. Culture gets stuck in old patterns because everyone is too busy “doing the work” to improve the model.
I’ve shared a specific example before because it’s so common in the mid-market. A company used an old tool called Mail Manager to save emails to SharePoint. The goal was avoiding Microsoft license fees. It sounded smart in the moment. Later, it complicated necessary upgrades like Windows 11.
That’s the cost of cheap.
Over-customization is a tax on your future
I’m also a big believer in vanilla software. I mean native, standard functionality.
Customization feels good at the start. It feels like control. It also creates a mess later when you need upgrades, security patches, or new integrations.
If your systems are heavily customized, you don’t really own a platform anymore. You own a one-off. And one-offs are hard to secure, hard to support, and hard to evolve.
“Current” beats “leading edge” for most CFOs
If you’re a mid-market CFO, you’re not trying to be a tech unicorn. You’re trying to run a business with predictable outcomes.
That’s why I recommend companies aim to be current. Not bleeding edge. Not leading edge. Current.
A culture of constant evolution beats a once-every-five-years reinvention. It costs less. It disrupts less. And it keeps your risk profile under control.
How good transformation consulting actually works
A lot of consulting firms talk in ambiguity. They talk in concepts and generalities, and everyone nods in the meeting. Then the project starts, and they don’t have the detail needed to deliver.
When the rubber hits the road, the difference between success and failure is usually definition. It’s business rules. It’s process clarity. It’s real-world testing.
Here’s how I approach it.
Step one: map the value chain and the real workflows
Every business is running long-running processes. That’s what it is. Those processes execute the objectives needed to deliver the value proposition.
The “official process” is often a PowerPoint. The real process is what people do to get work done when systems don’t cooperate.
If you want transformation without breaking the business, you start by understanding how the business operates. You map the value chain. Then you map how people, processes, and technology work together to deliver it.
You do this with the business. Not to the business.
Step two: draw the data flows
When systems don’t talk, it’s rarely a mystery. It’s usually an unmapped flow.
I tell teams to draw it out. A picture tells a thousand words.
What systems exist? Who talks to who? How frequently do they sync? Where does data get re-entered? Where do people “fix” things manually? Where do exceptions get handled?
Once you map it, you can usually see the breakpoints quickly.
I gave an example before around e-commerce and store inventory. You can’t solve that problem until you understand how the business fulfills. Are you shipping from a distribution center? Are you doing click-and-collect? Are you picking from store and delivering from store?
Amazon doesn’t pick from retail locations. Many grocery and retail chains do. That changes everything. It changes how inventory needs to be managed by location, how websites need to display availability, and how often systems need to exchange data.
If you don’t map those flows, you get stock-outs on the website, wrong promises to customers, and a mess on the floor.
Step three: define business rules before you automate anything
I’ve seen plenty of rollouts become frontline disasters. The root cause is usually simple.
The business rules were never defined.
People under-define what the process is supposed to do. Then they build a system without the rules embedded in it. The rollout happens, and not-so-good things happen.
CFOs feel this as a cost problem. COOs feel it as operational pain. Frontline teams feel it as frustration.
So before we automate, we define. We make the process explicit. We get the rules out of people’s heads and into something you can design around.
Step four: measure productivity in time, not opinions
I’m not a fan of vague ROI. I like measurable shifts.
Productivity improvements are measurable when you track the time required to execute a process. Use the company’s own metrics. Use independent measures that people already trust.
At a project level, this can be very clear. If a task took 20 hours and it now takes five, you don’t need a debate. You have a number.
And if you run fixed-price bids, the margin story becomes even cleaner. Use less labor to deliver the same output, and profit rises.
Step five: phase the work and pilot in real life
If someone tells you transformation will be flawless, they’re lying.
Large-scale change has pain. The job is to manage it.
You assess. You find where conflicts are. You do quick wins. You build a strategy to incrementally transform. You pilot in controlled settings, then scale.
I’ve said this before because it matters: real world experience is the most valuable thing you can have. Labs are useful. Pilots are decisive.
I’ve lived this on a large program scale. Rolling out a loyalty program can work fine with 10 users. The hard part is scaling to 10 million users hitting the same endpoint in a narrow window. I was involved in a loyalty rollout that got delayed by months because performance testing uncovered issues at scale. It wasn’t a nice-to-have delay. It was risk management.
CFOs should like this approach. It protects capital. It protects operations. It protects your reputation.
Retail taught me a blunt lesson: self-checkout is a finance case study
People love to debate self-checkout emotionally. I look at it structurally.
In retail, one of your biggest costs outside of goods for resale is labor. If you want to take labor out of the store, you have to get the customer to do the work.
That’s why self-checkout exists. It also helps optimize real estate. You can fit more lanes into a smaller footprint.
But here’s the part CFOs should focus on.
Self-checkout only produces labor leverage if the user experience is simple and the underlying data is clean. If the pricing data is wrong, if the UPC codes don’t work, if scans are inconsistent, you trigger interventions. Interventions require staff. Staff drives labor cost right back up.
At Loblaw, the self-checkout was so bad early on that we had to rewrite the entire front-end interface. Adoption was low. Error rates were high.
At Shoppers Drug Mart, we spent a lot of time on UX to make it super simple. We piloted in two stores. Early on, our biggest issue was service level, meaning keeping machines online and stable. Once we stabilized that, the success rate was strong. That supported scaling the investment across hundreds of stores.
And the measurement wasn’t complicated. You do time tracking on transactions, time studies on lanes, and error rate studies on self-checkout versus traditional checkout. You compare throughput and interventions.
That’s what CFO-grade transformation measurement looks like. You don’t need hype. You need a baseline and a delta.
Governance is the CFO lever that stops technology spend from drifting
A lot of companies think their issue is technology. It’s often governance.
Too many vendors. Too many fragmented systems. Too many one-off decisions. Nobody owns the end-to-end outcome.
So the question becomes: who decides, based on what, with what information?
In our work, we start with discovery. Financials first. Then we map how data moves and how the value chain is executed. Once we do that, it becomes clear who is contributing value and who is operating in a vacuum.
Then you organize the chaos into a small number of themes. Three, four, maybe five. Those themes become programs you can manage. You can assign ownership. You can measure progress. You can report to the board without telling a 45-minute technology story.
This is also where CFOs tend to regain confidence. You’re no longer funding a pile of disconnected projects. You’re funding a plan.
Roger Favero, CIO at HomeEquity Bank, described it this way: “They identified inconsistencies in governance, how our technology was being deployed, and excesses in our technology spending. We now have robust governance in place…”
That’s the point. Governance makes spend predictable. It makes delivery predictable. It makes risk visible.
Architecture can quietly crush gross margin
CFOs usually think of architecture as a technical concept. I think of it as a margin concept.
Bad architecture creates manual workarounds. It slows delivery. It increases support burden. It makes every change harder. It makes every integration more expensive.
Over time, it pushes cost into labor, downtime, and rework. That hits gross margin.
Thomas J. Moysak, President and CEO at Xtiva Financial Systems, said: “We never realized that our architecture was killing our GM.”
He’s not alone.
In my own work, I’ve provided CTO advisory services to a financial services technology provider where stabilizing and improving the technology improved the P&L and added in excess of 25 basis points to gross margin. That wasn’t magic. It was clarity, control, and a better technical foundation.
When CFOs ask me why “low-cost IT” turns into expensive IT, this is usually the answer. Scalability gets lost. You pay for it later.
Security and uptime: protect the business without blocking the business
CFOs don’t experience security as a technical issue. You experience it as business continuity, liability, and valuation risk.
You also experience it as operational interruption when systems are unstable.
At The Narrative Group, we provide managed cybersecurity with automated threat detection, patch management, and incident response. Our model is built to support 99.9% uptime and reduce security incidents by 85% compared to in-house management.
But I want to be clear about something else.
Security can’t become an excuse for IT to block the business.
I’ve seen environments where every request gets shut down “because security.” That’s a productivity killer. It damages trust fast.
One customer came to us with a blunt problem. They had six offices. When people moved between offices, they couldn’t connect to the network. Meeting rooms barely worked. Every time they asked IT for help, they got blocked under the banner of security.
Our approach was simple. We stabilized the basics first. We assessed infrastructure. We fixed problems office by office. We replaced core network gear. We replaced outdated servers. We put devices on lifecycle management. We invested in meeting rooms and made sure people knew how to use them.
Years later, the managing director told me, “You’ve created a problem for me… everybody wants the office to look exactly like the new office that you created because it’s that good.”
That story matters because it shows the order of operations. When you deliver reliability, you earn credibility. Once you have credibility, you can move up the stack into business process change.
Cloud migration: treat it like an investment, not a religion
Cloud can be great. Cloud can also be a cost surprise if it’s done without discipline.
CFOs should insist on a real cost model. You need current state costs, future state costs, and the operating model in between. You also need training, because adoption drives ROI.
Our cloud migration work includes a detailed cost analysis and optimization plan. Typical clients reduce infrastructure costs by 25 – 40% while gaining scalability benefits. We also include staff training and six months of performance monitoring, because the truth of cloud shows up after go-live.
If your partner can’t explain how cloud spend will be governed month-to-month, you’re taking on risk. Cloud isn’t “set it and forget it.” It’s “measure it and manage it.”
AI: useful, immature, and a very good liar
If there’s a buzzword today that makes me pause, it’s AI.
AI has real opportunity. It also has real risk. It doesn’t know what it doesn’t know. It can sound confident while being wrong.
So where does it help a CFO in a practical way?
I see strong opportunity in long-running workflows. AI can help manage exceptions, triage decisions, and improve data quality. It can also help generate standardized data that follows strong business rules. That type of output can be reused over and over again.
This matters because so many workflow roles are tedious and detail-heavy. Nobody wants those jobs. AI can take on parts of that workload, under supervision, and free people up for higher-value work.
We help clients run proofs of concept for AI and workflow automation so the business can see what’s real. One automation case reduced a client’s e-commerce product setup cycle dramatically. It went from a five-week cycle where one person spent three weeks doing the work, down to about four hours.
That’s not hype. That’s capacity.
And CFOs should still demand controls. AI left on its own in production, without oversight, is a disaster waiting to happen.
Change management: the math fails if people don’t move
I’ve been asked plenty of times: “What if people resist the change?”
They will. Sometimes quietly. Sometimes loudly.
So you need leadership buy-in. It starts at the top of the house. Especially in privately held mid-market businesses, where the owners and senior leaders are embedded in the business.
When leaders buy in, they help prepare staff for what’s coming. They set the stage for constructive conversations. They help you deal with the hard cases, too. There are always a few people who struggle with change. The worst move is ignoring it. You talk about it at the executive level and decide how you want to manage it.
And when frontline teams are scared, you lead with empathy. You ask them to show you their day. You listen to their frustrations. Most of the time, the frustration is role definition or technology not doing what the business expects.
If you want trust, you deliver. Talk is cheap. Actions speak volumes.
What “digital transformation consulting services” should include for the mid-market
Most $20M – $100M companies need enterprise-grade thinking. They just can’t justify enterprise-grade headcount.
That gap is why I founded The Narrative Group. I’m a business leader who wants good things for other business leaders. I wanted to give back. I wanted to make top-tier enterprise advice accessible to mid-market leadership teams.
We’re not just a reseller or an MSP. We’re a strategic partner. We connect IT strategy to financial outcomes.
Here’s what that looks like in practice.
Finance-First IT Strategy (IT Value Alignment Assessment)
This is a fixed-fee assessment designed to give you clarity fast. It maps IT spend to the P&L. It shows where money is going, why, and what value it is producing. It also produces board-ready ROI reporting.
Our typical outcome is 15 – 30% IT cost optimization within six months while improving measurable business performance metrics. The point isn’t starving IT. The point is spending with purpose.
Emma Reed, a CEO we worked with, put it in plain language: “They showed us how much IT costs in a way that made sense.”
That’s the job. Make it make sense.
Digital transformation planning that doesn’t break operations
We build 12-month roadmaps with quarterly milestones, budget forecasting, and ROI projections. We also support change management, because a roadmap without adoption is a document.
You’re not buying a plan. You’re buying a path from current state to target state, with risk managed along the way.
Fractional CTO leadership for CFOs who need an adult in the room
Many mid-market companies need a CTO or CIO. They just can’t justify a full-time executive hire, the cost, or the hiring risk.
We deliver fractional CTO leadership designed for companies in your revenue range. It’s typically delivered at 60 – 70% less cost than a full-time hire. It includes roadmap ownership, vendor management, and strategic planning. Our client retention rate is 98%, and our average engagement duration is 18+ months.
That’s not because clients love meetings. It’s because they want continuity and outcomes.
Managed services, security, and best-practice documentation
We provide managed services with a focus on security, uptime, and a stable end-user experience. We also build best-practice documentation based on Fortune 100 standards, including policies, procedures, training materials, compliance checklists, and quarterly reviews.
CFOs like this because it reduces key-person risk. It reduces “tribal knowledge.” It makes the operating model durable.
IT leadership coaching so your internal team gets stronger
In many companies, there’s an internal IT manager who’s doing their best. They just haven’t been coached to operate at an executive level.
We provide monthly coaching to strengthen presentation skills, stakeholder management, and strategic thinking. That matters because the IT-business relationship often breaks down at the communication layer.
What clients say when the work is done right
I don’t want to overtalk this. I’d rather let customers describe the outcomes.
Maria Elston, Managing Partner at a law firm, said: “We didn’t realize how much time we were losing to inefficient tech until TNG stepped in… cut 40% of our software spend…”
Iman Bilal, Managing Director at an online retailer, described the budget shift clearly: “70% of our IT budget was labour! With TNG, we have it back to 50/50 labour to non-labour. We are on our way to 30/70!”
And Sophie Grant, CFO at a retail store chain, said: “The Narrative Group leveraged their proprietary methodology to identify a roadmap… and charted a path toward IT spending being 1.5% of revenue…”
Those are CFO outcomes. Clarity. Predictability. Control.
The CFO scorecard: what I’d measure quarter by quarter
If you want transformation to stay real, you measure it.
I like a scorecard that connects directly to the CFO worldview. You track IT spend as a percentage of revenue. You track uptime and incident trends. You track the labor versus non-labor mix, because labor-heavy IT budgets usually hide productivity problems.
You also track process cycle time. Pick a few critical workflows and measure how long they take today. Then measure again after change. This is where you see if the roadmap is creating real leverage.
And don’t ignore data quality. If the business can’t trust its data, you get rework, bad decisions, and friction everywhere.
Choosing a consulting partner: the questions I’d want you to ask
If you’re evaluating digital transformation consulting services, don’t start with their slide deck. Start with their discipline.
Ask them how they will connect the work to value creation. Ask them how they will map spend into the P&L. Ask them how they will measure productivity using your metrics. Ask them how they will define business rules before they automate anything.
Ask them how they run pilots. Ask them how they test at scale. Ask them how they handle governance and vendor management so you don’t drift back into fragmentation.
Then ask the human question. Ask how they work with your frontline teams. Ask how they earn trust. Ask how they deliver, not just recommend.
If they can’t answer those questions clearly, you’re taking on risk.
Where to start next week (if you want control quickly)
If you want a practical starting point, keep it tight.
Start by answering what you’re trying to transform and how it aligns to value creation. Then get a clean view of total IT spend, even the spend hiding outside the IT budget. Map one high-friction workflow end to end, including data flows and business rules.
Once you see that picture, you’ll know where the conflicts are. Then you can build an incremental plan to remove them, pilot safely, and scale with confidence.
That’s transformation that respects the business.
And at the end of the day, that’s the narrative you’re trying to change. You’re moving from technology as a cost and a risk, to technology as an enabler of growth, margin, and enterprise value.
Frequently Asked Questions
What is the difference between digitization and digital transformation?
Digitization merely converts analog records (like paper invoices) into digital formats. Digital transformation fundamentally alters business workflows to create new value. For CFOs, the former is an efficiency play, while the latter drives revenue growth and competitive advantage.
How does cloud migration impact financial reporting (CapEx vs OpEx)?
Cloud adoption typically shifts IT spend from infrequent, heavy Capital Expenditures (CapEx) to predictable, monthly Operating Expenditures (OpEx). This model improves cash flow visibility but requires rigorous governance to prevent subscription cost drift.
Can digital transformation initiatives improve company valuation?
Yes. Modernizing infrastructure increases EBITDA multiples by reducing key-person risk and documenting scalable processes. Investors and acquirers value the predictability and transparency that integrated systems provide over businesses reliant on manual ‘heroics.’
Why do many digital initiatives fail to secure funding?
Projects often fail to articulate measurable value. With 67% of CFOs refusing to waste capital on initiatives without clear ROI, proposals must demonstrate specific efficiency gains or revenue impact to receive budget approval.
What is the role of APIs in mid-market IT infrastructure?
Application Programming Interfaces (APIs) allow disparate software to exchange data securely without manual entry. For mid-market firms, an API-first strategy prevents data silos and enables real-time reporting without the cost of heavy custom integrations.
How does digital maturity affect cybersecurity insurance premiums?
Insurers increasingly demand proof of robust security controls, such as Multi-Factor Authentication (MFA) and automated patching, before issuing policies. Demonstrating a proactive security posture can significantly reduce premiums and ensure coverage eligibility for the business.
Why prioritize Customer Experience (CX) in B2B transformation?
Digital portals and automated updates reduce the cost-to-serve while increasing retention. Since 71% of CFOs view transformation as key to success, aligning technology with customer needs ensures revenue durability.
What is the difference between a Consultant and a Value-Added Reseller (VAR)?
VARs primarily sell software licenses and hardware, often incentivized by vendor volume. Strategic consultants focus on process design, vendor agnosticism, and ROI, ensuring technology serves the business case rather than a sales quota.
How does Low-Code development fit into enterprise strategy?
Low-code platforms allow rapid deployment of departmental tools without burdening core engineering. However, CFOs must ensure IT governance oversees these tools to prevent security gaps and data fragmentation known as ‘Shadow IT.’
What defines a Data Warehouse versus an ERP?
An ERP manages daily transactions (invoicing, inventory), while a Data Warehouse aggregates historical data for analysis. Separating these functions prevents complex reporting queries from slowing down the critical operational systems used by frontline staff.