When Does Technology Transformation Become a Growth Strategy Rather Than a Cost Program?

Technology transformation has become one of those phrases that can mean almost anything.

For some organizations, it means replacing legacy systems. For others, it means moving to the cloud, introducing AI, modernizing data architecture, consolidating applications or automating processes. Increasingly, transformation is presented as a path to both efficiency and growth but there is an important distinction that boards and executive teams should make before approving another major transformation program:

Is this fundamentally a cost program with a technology component, or is technology being used to change the company’s growth trajectory?

The difference is not semantic. It changes what gets funded, who owns the work, how success is measured and ultimately whether the organization creates sustainable enterprise value.

I have led transformations where technology modernization was essential to improving the economics of the business. I have also seen organizations invest heavily in technology without changing the underlying customer experience, commercial model or operating behavior. The technology got better. The business did not grow and the customers didn’t feel the change.

The dividing line is surprisingly straightforward.

A transformation becomes a growth strategy when technology changes the company’s ability to acquire, serve, retain, expand or monetize customers — and when those outcomes are explicitly connected to investment decisions.

That is a test a board can actually apply.

Start with the customer, not the technology

The easiest way for a transformation to become a cost program is to start with the technology.

We need a new ERP. We need to consolidate platforms. We need to migrate to the cloud. We need a new CRM. We need an AI strategy.

All of these may be perfectly rational investments. However, none of them, by themselves, constitute a growth strategy.

The more important question is: What are we trying to make possible for the customer that we cannot do today?

That question changes the conversation.

Perhaps the organization wants to reduce the time required to onboard a new customer from months to weeks. Perhaps it wants to give customers a dramatically more personalized experience. Perhaps sales teams need real-time insight into customer behavior so they can identify expansion opportunities earlier. Maybe the company wants to enter a new segment but its current operating model makes the economics impossible.

Those are growth problems. Technology becomes the enabler rather than the destination.

This distinction matters because customers do not buy “technology transformation”. They buy outcomes: faster service, lower friction, better insight, greater productivity, lower risk or something that helps them achieve their own objectives.

If the transformation cannot ultimately be explained in those terms, I would question whether it is really a growth strategy.

The board question: where does the transformation change the growth equation?

Boards do not need to become technology experts to challenge a transformation strategy.

They need to ask a few deceptively simple questions.

Which part of the revenue equation will this investment change?

Will it increase customer acquisition? Improve conversion? Increase average contract value? Reduce churn? Create expansion opportunities? Improve pricing realization? Open a new market?

And then:

How much revenue do we expect it to influence, by when, and through what mechanism?

That last question is particularly important.

Transformation business cases can become filled with impressive activity metrics: applications retired, processes automated, employees trained, systems migrated, data consolidated, releases completed.

Those measures tell us whether the transformation is happening.

They do not tell us whether the business is becoming more valuable.

A board should be able to trace a line from investment → capability → customer behavior → commercial outcome → enterprise value.

If that line cannot be drawn, the transformation may still be necessary but it should be governed as an infrastructure or cost program rather than marketed internally as a growth strategy.

Who owns the customer journey?

One of the most revealing questions I have encountered in transformation work is also one of the simplest:

Who owns the customer journey?

Not the CRM. Not the digital experience. Not Marketing. Not Customer Success.

The journey.

From the customer’s first interaction with the company through acquisition, implementation, adoption, renewal, expansion and advocacy.

In many organizations, ownership is fragmented. Marketing owns demand. Sales owns the opportunity. Professional Services owns implementation. Product owns the end user experience. Customer Success owns adoption. Finance owns the contract. Support owns the problem when something breaks.

The customer, however, experiences one company.

This fragmentation becomes especially visible during transformation. Every function can optimize its own piece of the process while the overall customer experience becomes more complicated.

A growth-oriented transformation therefore needs someone accountable for the end-to-end commercial and customer outcome, not simply for delivering the technology.

That does not mean one executive literally owns every customer interaction. It means there is clear accountability for whether the transformation makes the customer’s journey better — and whether that improvement translates into economic value.

In transformations I have led, this has often required breaking down functional boundaries that existed for years. The hardest work was not always implementing the technology. It was getting Sales, Marketing, Product, Services, Customer Success, Finance and Operations to agree on what the customer actually needed and how the company would measure it.

Technology exposed the organizational seams.

Transformation required us to repair them.

Investment priorities should follow the growth constraint

Another useful test is to ask:

What is currently constraining growth?

This sounds obvious, but it is remarkably easy for organizations to lose sight of it once a transformation program gets underway.

Imagine a company has a sophisticated new platform but cannot generate enough qualified demand.

Or it has automated its sales process but its salespeople are selling to the wrong customers.

Or it has dramatically improved implementation efficiency but customers still do not adopt the product.

Or it has built an impressive data environment but executives cannot agree on which customers, segments or products deserve investment.

In each case, technology may have improved. But the growth constraint remains somewhere else.

The best transformation leaders therefore allocate investment against the binding constraint in the business, not against the most visible technology problem.

That can require difficult tradeoffs.

I have been in situations where the organization wanted to pursue a broad enterprise transformation because the market opportunity appeared enormous. But pursuing that opportunity exposed gaps in product capabilities, operational maturity, services capacity and the underlying go-to-market model.

The answer was not simply to spend more.

Sometimes the most strategic decision is to narrow the focus.

A transformation creates value when it concentrates resources on the capabilities that matter most to the company’s chosen customers and economic model.

The uncomfortable relationship between transformation and commercial execution

There is another reason technology transformations fail to become growth strategies: organizations often separate the transformation office from the commercial organization.

The transformation becomes something “the company” is doing while Sales and Marketing continue operating according to the old model.

That is a mistake.

If the transformation is intended to drive growth, the commercial organization should be one of its primary customers.

Sales leaders should be able to say:

This capability will allow us to sell something we could not sell before. This data will allow us to identify expansion opportunities we currently miss. This process will reduce friction in the buying journey. This platform will let us serve a segment profitably that we cannot serve today.

Those statements are much more powerful than “the new system will improve efficiency.”

Efficiency matters. But efficiency becomes strategically interesting when it creates capacity for growth.

If automation saves 20% of someone’s time, the value is not necessarily the 20% reduction in labor.

The question is what the organization does with the capacity it creates.

Does the salesperson make more calls? Does Customer Success spend more time with strategic customers? Does Marketing personalize campaigns? Does Product accelerate releases? Does the company reinvest the savings into a growth market?

Cost savings are an outcome. Capacity creation can be a growth strategy.

Measure value, not activity

This may be the most important discipline of all.

Every transformation should have two scorecards.

The first measures execution. Are we on time? Are we on budget? How many systems have been migrated? How many processes have been automated? How many users have adopted the new platform?

These metrics matter. They tell us whether the program is being delivered.

But the second scorecard measures business value.

What happened to revenue? What happened to retention? What happened to win rates? What happened to sales productivity? What happened to customer acquisition cost? What happened to expansion? What happened to gross margin? What happened to customer satisfaction and lifetime value?

And, critically, did those outcomes persist after the transformation team moved on?

That last question separates sustainable value from transformation theater.

A temporary revenue spike caused by extraordinary executive attention is not the same as a repeatable commercial capability.

A one-time cost reduction is not the same as a structurally better operating model.

A successful implementation is not the same as customer adoption.

The real measure of transformation is whether the organization can operate differently — and create more value — after the program becomes business as usual.

What I would put in front of a board

If I were evaluating a major technology transformation today, I would want to see five things.

First, a clearly defined growth thesis. Not “modernize our technology.” Instead: “This investment will allow us to increase retention in this segment, accelerate acquisition in this market or create this new revenue opportunity.”

Second, an explicit customer journey. Where does the transformation materially improve the customer’s experience and who owns the end-to-end outcome?

Third, a capability map. What capabilities are genuinely differentiating and which are simply table stakes? Not every problem requires proprietary technology or a major transformation.

Fourth, a capital allocation logic. Why are we investing here rather than somewhere else? What constraint are we removing? What will we stop doing to fund the priorities that matter most?

And fifth, a value scorecard. Not just milestones and implementation metrics but measurable changes in revenue, retention, productivity, margin and customer economics.

The board should also ask one final question:

If we stopped calling this a transformation, would the business case still make sense?

That question is powerful because it strips away the language.

Technology transformation should never be valuable simply because it is transformation.

Transformation is ultimately about changing what the business can do

The best transformations I have been part of were not really technology projects.

They changed what the company was capable of doing.

They enabled the organization to see customers differently, make decisions faster, operate across boundaries, sell more effectively, serve customers more intelligently or scale an economic model that previously did not work.

Technology was critical but technology was not the strategy.

The strategy was the new capability the technology made possible.

That is the distinction I believe boards and executive teams should increasingly demand.

A cost program asks: How can technology help us do what we already do for less?

A growth transformation asks: What could we do for customers — and therefore for our business — that we cannot do today?

Both can create value.

But they require very different leadership.

In an environment where technology investment is competing for capital with every other growth opportunity, that distinction is no longer academic. It is the difference between spending money to modernize the business and investing money to change its trajectory.

---

Nina Simosko writes The Growth Mandate, sapperment’s column on Technology-Led Growth. She is Chief Revenue Officer at CYPHER Learning; former President & CEO of NTT Innovation Institute (NTT i3), Nike global technology leader and SAP Senior Vice President. She writes here in a personal capacity; views are her own. Articles are vendor- and firm-neutral.

Next: meet Nina Simosko and The Growth Mandate · explore Executive Clarity, the board-level decision series · or browse the sapperment library.