The $100 Million Transformation

The Distance From The Pizza — Part Four

How a transformation can deliver its promised savings and still leave the business worth less to its customers.

Imagine Angelo's pizza business has grown from a single neighbourhood shop into a successful chain of 50 locations. He's built it over decades, one pizza and one customer at a time. The business has a reputation for good food, friendly service and knowing its customers. Some families order every Thursday. Angelo's people know their preferences, recognize their voices on the phone, and understand what keeps them coming back.

But growth has brought complexity. Fifty locations mean more employees, more suppliers, more inventory, more scheduling and more decisions. The systems that worked when Angelo could see everything happening in one kitchen are no longer enough. The company needs better information, more consistent processes and a way to manage the business at scale.

A consulting firm is engaged to help. After months of analysis, workshops and financial modelling, it presents a $100 million transformation. A new ERP system will integrate the business. Purchasing will be consolidated, recipes and production processes standardized, ordering automated and delivery outsourced. Management will have better information, greater control over costs and a clearer picture of performance across all 50 locations.

The business case is compelling. The expected savings are substantial, the projected return on investment is attractive, and the implementation plan identifies the risks. The board approves the investment.

There's nothing inherently wrong with any of this. Angelo needs to run a larger business, and technology can help him do it. Better inventory management can reduce waste. Standardized processes can improve consistency. Online ordering can make life easier for customers. Outsourcing delivery can provide flexibility. The right systems can give Angelo's people more time and better information to do their jobs.

The question isn't whether the transformation makes sense. The question is whether the business case has considered everything that might change when the transformation reaches the customer.

The front counter

For years, the same friendly person has answered the phone at Angelo's. She recognizes a regular customer's number and answers, "Good evening, John. The usual tonight?"

She knows the customers, their preferences and the little things that make the experience personal. If someone has an unusual request, she can usually help. If a customer mentions a problem with last week's order, she remembers the conversation and can do something about it. She's not just taking orders. She's part of the relationship between Angelo's and the people who buy from him.

The transformation introduces online ordering and automated order processing. The business case shows that fewer people will be needed to take orders, transactions will be processed more efficiently, and errors will be reduced. Customers can order whenever they want without waiting for someone to answer the phone.

For many customers, this will be an improvement. They may prefer the convenience, and the technology can make routine transactions faster and more reliable.

But what happens to the relationship that existed before?

John can still order a pizza, of course. The system has captured his order, processed his payment and sent instructions to the kitchen. From an operational perspective, everything is working as intended. But the familiar voice is gone. The person who knew John and could recognize an unusual request has been replaced by a screen. Perhaps John doesn't mind. Perhaps he misses the personal touch but doesn't think much about it. Or perhaps, over time, the experience becomes just a little more anonymous.

When another pizza shop offers a similar product, the personal connection that once distinguished Angelo's is no longer part of the equation. The company has automated the transaction. Has it also automated away part of the reason the customer came back?

The business case counted the cost of answering the phone. Did it count the value of the person answering it?

The kitchen

Angelo has always taken pride in the quality of his pizzas. He learned his craft growing up in Italy, and years of experience have taught him things that are difficult to put into a recipe.

He knows how the dough should feel, how the ingredients should be distributed and what a properly cooked pizza should look like when it comes out of the oven. He can spot a pizza that isn't quite right before it goes into the box. Sometimes it's the crust. Sometimes it's the way the cheese has browned. Sometimes it's something he can't easily explain. He simply knows.

The new ERP system introduces standardized recipes, specified quantities, production instructions and cooking times. Every location is expected to follow the same process. New employees can be trained more quickly, ingredient usage becomes more predictable, and management can monitor compliance across the chain.

A newly hired 18-year-old student follows the instructions exactly. The system specifies the ingredients and quantities, and the production process has been completed according to the approved standard. But Angelo looks at the pizza and knows he wouldn't have put it in the box. The crust is slightly uneven. The toppings aren't distributed quite right. The cheese has browned in a way that tells him the oven was too hot. The student hasn't done anything wrong. He's followed the process he was given. Nobody has taught him what Angelo knows, because nobody fully recognized how much of Angelo's expertise existed outside the documented procedure.

The organization standardized the work, but it didn't necessarily transfer the expertise.

The system knew how to make a pizza. Angelo knew when the pizza was right.

Standardization can be enormously valuable. Angelo cannot personally inspect every pizza produced across 50 locations, and the business shouldn't have to depend on one person's presence to maintain quality. But there's a difference between documenting the steps of a process and transferring the judgment that makes those steps work.

If the transformation captures Angelo's knowledge and teaches others how to apply it, the business can scale his expertise. If it captures only the recipe, it may scale the process while losing part of what made the product special. The technology isn't the problem. The question is whether the organization has understood what the technology needs to preserve.

The delivery

Carlo is Angelo's son. He's grown up around the business and knows the neighbourhood almost as well as his father knows the kitchen. He knows which streets are difficult to navigate, which houses are tucked behind others, and which customers order every Thursday. When he delivers a pizza, he hands it over with a smile, a thank you and a familiar, "See you next week."

The transformation outsources delivery to a third-party company. The financial case is straightforward: fewer employees on the payroll, less scheduling and administration, and a delivery cost that varies with demand.

The new driver may be perfectly competent, but he's unfamiliar with the neighbourhood. He spends twice as long finding an address that Carlo could locate without thinking. The pizza gets colder while he searches. When he finally reaches the customer's door, he hands over the box and says, "Here ya go," before heading off to the next delivery.

The order is complete. The delivery is recorded. The transaction has been fulfilled.

But has the business delivered the same experience? Carlo knew the customer. The new driver knows the address. Those aren't necessarily equivalent things.

The company may have reduced the cost of delivery while removing a small but meaningful part of the relationship between the business and its customer. It may also have increased delivery times and reduced the likelihood that the pizza arrives at the temperature Angelo intended. Again, the decision may be entirely reasonable. Outsourcing can provide flexibility and improve economics. The question is whether the business case considered what was being traded away alongside what was being saved.

Then someone opens the box

Now let's put these decisions together.

The customer places an order online instead of speaking to a familiar person. The pizza is made according to a standardized process that may not fully capture Angelo's judgment. It arrives later and cooler than it used to, delivered by someone the customer has never met. When the family opens the box, they notice that the pizza looks a little smaller and there aren't as many slices of pepperoni as they remember.

Someone at the table says, "Has this place changed owners? Their pizzas used to be better."

That is the moment the transformation reaches the customer. Nobody at the table knows about the ERP system, the revised ingredient specifications, the outsourced delivery contract or the cost-reduction targets. They don't see the improved inventory management or the new dashboard.

They experience the combined result of decisions made throughout the organization. And they draw their own conclusions about the business. Perhaps they continue ordering. Perhaps they order less frequently. Perhaps they quietly try another pizza shop and never return. They may not complain, complete a survey or tell anyone at Angelo's what went wrong. They simply stop coming back.

The business case measured the benefits of individual decisions. The customer experienced the cumulative consequences.

This is where the distance from the pizza becomes important. The people who approved the transformation weren't necessarily careless, incompetent or indifferent to customers. They made decisions using the information available to them. Each decision had a rationale, a projected benefit and an expected return.

But the information described the business from a distance. It showed what each change would save without necessarily revealing what the customer would experience when all those changes came together. The transformation may have succeeded at everything the business case asked it to do—and still left the business worth less to its customers.

The missing line in the business case

Technology feasibility studies are generally good at calculating internal impacts. They identify positions that can be eliminated, hours that can be saved, processes that can be accelerated and costs that can be reduced. Those benefits can often be quantified with reasonable precision.

But what about the external consequences?

How many customers might be lost if service becomes less personal? What happens to repeat purchases if the product changes in ways customers notice? How much expertise is lost when experienced employees leave or their judgment is replaced by a process that captures only part of what they know? What happens to customer loyalty when the relationship that once distinguished the company becomes a series of automated transactions?

Before calculating how many heads a technology investment will remove from the payroll, we should consider how many customers it might remove from the business.

That isn't a claim that every efficiency improvement will drive customers away. Technology can improve quality, reliability and convenience. A well-designed transformation can make a business better for employees and customers alike. The point is to identify the risks, understand what customers value today, establish a baseline and measure what actually happens after the change.

There is a financial consequence here, too. The organization may report the savings attributable to the transformation while attributing any lost revenue to the economy, the competition or the sales department. The costs and benefits end up in different reports, different budgets and different conversations. Nobody necessarily connects them to the original decisions.

The savings are visible. The lost value is harder to see.

And when a problem is finally recognized, the organization may have to spend money to correct it: changing the process, retraining employees, improving delivery arrangements or restoring a human option at the front counter. Meanwhile, customers may have gone elsewhere, experienced employees may have left, and trust may have been weakened.

The business might eventually return to its previous level of performance, but that doesn't mean it has recovered the full economic value lost along the way. The cost of remediation is only one part of the equation. Lost sales, missed opportunities, management distraction and relationships that cannot be restored also matter.

A transformation business case should consider not only the cost of implementing the change, but also the potential cost of getting the change wrong—and the cost of recovering when it does.

Look in the box

Perhaps the most important question for Angelo's leadership team isn't whether the ERP system is working as designed. It's whether the business is delivering what customers believe they're paying for.

That requires more than a dashboard. It requires people who remain connected to the work and the customer, who can recognize changes in quality or behaviour, and who have a way to bring those observations back to the people making decisions.

It also requires recognizing that employees like Angelo, Carlo and the person at the front counter contribute more than the tasks listed in their job descriptions. They carry experience, judgment, relationships and knowledge that can be difficult to replace once lost. A transformation should consider how to preserve and develop that value, even when the work itself changes.

The goal isn't to prevent change. It's to make better decisions about what should change, what should be preserved and what new capabilities the organization needs to develop.

A $100 million transformation deserves a business case that examines the whole business—not just the parts where the savings are easiest to calculate.

Before the next major technology investment is approved, perhaps leadership should ask a few additional questions. What will our customers actually experience when these changes come together? What knowledge, judgment and relationships are we putting at risk? How will we know if the product or service has become less valuable to the people who buy it?

And who will be close enough to the customer to notice before the consequences appear in the financial results?

The spreadsheet can tell us how much the new process should save. The dashboard can tell us whether the new process is operating as designed. But neither, on its own, can tell us whether the customer still thinks the pizza is worth buying.

How far away from the pizza are we—and what value might we be removing without realizing it? Because the ultimate test of a transformation isn't simply whether the organization has become more efficient. It's whether the business has become better at delivering the value its customers came for in the first place.

Cambiara Group - October 2026