Enterprise technology buyers are not short of transformation ambition.
They have cloud strategies. AI pilots. ERP roadmaps. Data programmes. Security initiatives. Application rationalisation plans. Automation experiments. Innovation portals. Digital academies. Architecture committees. Board-level pressure. User frustration. Cost pressure. Risk pressure. Vendor pressure.
What they do not always have is a clean route from the estate they own today to the operating model they want tomorrow.
That is the real issue for IT vendors selling into large organisations.
Digital transformation is often positioned as a story of modern platforms, intelligent automation and faster innovation. But inside enterprise buying committees, the conversation is usually more difficult. Buyers are dealing with old applications that still run critical processes, fragmented data, unclear ownership, limited business capacity, integration debt, security risk, cloud cost concerns and stakeholders who have seen previous transformation programmes overpromise and underdeliver.
The result is a buyer who may agree with the direction of change, but still hesitate on the decision.
For vendors, this changes the sales task.
The winning message is not simply “we can modernise your stack”. It is “we understand why modernisation is hard in your environment, and we can help you reduce risk while creating visible business value”.
That distinction matters.
Recent enterprise IT roundtables across DACH and the Nordics show that legacy systems are no longer being discussed as a purely technical constraint. They are being discussed as a commercial, operational and organisational constraint. Leaders are asking how to decommission without disruption, how to connect legacy and modern systems, how to preserve institutional knowledge, how to prove value quickly, how to manage cloud and vendor dependency, and how to keep security and compliance embedded from the start.
For solution providers, this creates a clear opportunity.
Enterprise buyers are not looking for transformation theatre. They are looking for partners who can help them move carefully, commercially and credibly.
Legacy systems are not just old technology
One of the biggest mistakes vendors make is treating legacy systems as outdated assets that buyers simply need to replace.
Enterprise buyers rarely see them that way.
Many legacy systems are deeply embedded in business processes, customer journeys, pricing models, operational workflows and compliance routines. They may be old, inefficient or expensive to maintain, but they also carry business logic that is not fully documented anywhere else. They often contain years of institutional knowledge, workarounds, dependencies and assumptions that the business relies on every day.
That is why replacement is politically and operationally difficult.
In the roundtables, leaders discussed legacy environments across insurance, energy, real estate, fashion, banking, manufacturing and maritime sectors. The details varied by industry, but the pattern was consistent. Legacy systems were not just blocking technology renewal. They were shaping how quickly the business could launch new pricing models, integrate data, adopt SaaS, scale AI, improve customer journeys and reduce operational risk.
For vendors, this means the sales conversation needs to move beyond platform capability.
The buyer wants to know:
| Buyer concern | What it really means | Vendor response that builds confidence |
|---|---|---|
| “We have too many legacy applications” | The buyer needs clarity on what to keep, replace, connect or retire | Offer application landscape assessment and phased modernisation planning |
| “The business case is difficult” | The buyer needs measurable value before committing budget | Link transformation to cost, speed, customer experience, risk or revenue impact |
| “Integration is the issue” | New tools cannot succeed if they sit outside operational workflows | Show how your solution connects with existing systems and data flows |
| “We do not have enough internal capacity” | Business and IT teams are already stretched | Make implementation requirements explicit and realistic |
| “Security and compliance are slowing us down” | Risk teams must be involved earlier | Bring governance, access control and security into the first conversation |
| “We have tried transformation before” | Trust has been damaged by previous programmes | Lead with proof, staged outcomes and transparent delivery assumptions |
The commercial lesson is clear.
A buyer stuck with legacy systems is not automatically resistant to change. They are often trying to avoid another expensive programme that creates disruption before it creates value.
The best buyers are decomposing, not replacing everything at once
A strong theme from the roundtables was the shift away from all-or-nothing transformation.
Several leaders described a more modular approach to legacy modernisation. Rather than replacing entire platforms in one high-risk programme, they are decomposing systems piece by piece, prioritising the components where change can unlock faster business value.
This is a critical insight for vendors.
Many enterprise buyers want modernisation, but they do not want a cliff-edge migration. They want a controlled path. They want to reduce risk while improving functionality. They want to prove that a new architecture can support the business before they expose critical operations to unnecessary disruption.
One example discussed was the gradual replacement of components such as pricing, billing and data warehouse capabilities. The business case was not only about reducing technical debt. It was about enabling faster pricing changes and easier integration with older systems while lowering the risk of a full replacement.
That is the kind of value story vendors should be listening for.
If your solution helps buyers break transformation into manageable stages, say so clearly. If it can connect to existing systems while the buyer modernises around it, make that a core part of the pitch. If it helps the buyer avoid large-scale disruption, that is not a footnote. It is a buying trigger.
Enterprise buyers do not always need a bigger transformation vision. Often, they need a safer first move.
This also affects how vendors should structure proposals.
A stronger proposal might include:
| Transformation stage | Buyer objective | Vendor value |
|---|---|---|
| Discovery | Understand dependencies, data flows and business logic | Map the current estate and identify high-value pressure points |
| Stabilisation | Reduce operational risk before major change | Improve visibility, documentation, security and integration readiness |
| Decomposition | Replace or modernise priority components | Support modular migration without forcing full estate replacement |
| Integration | Connect legacy, SaaS, cloud and data platforms | Provide API, data and workflow interoperability |
| Optimisation | Prove business impact and scale what works | Track measurable outcomes and expand from validated use cases |
This is where many vendors can sharpen their enterprise positioning.
Do not sell transformation as a destination only. Sell the path.
Business value is now the internal language of transformation
Enterprise IT leaders may care deeply about architecture, data models, application rationalisation and infrastructure maturity. But when transformation reaches the board, the language changes.
Boards want financial benefit. Business leaders want practical improvements. Operational teams want tools that make work easier. Security teams want control. Data teams want quality. Architecture teams want coherence. Finance wants proof.
This creates a messaging challenge for vendors.
One roundtable discussion on digital transformation highlighted the importance of tailoring roadmaps to different audiences. Boards need to see financial outcomes. Operational teams need to see tangible day-to-day benefits. IT and architecture teams need to see the long-term technical logic. Business teams need to understand the time commitment required for successful implementation.
That is exactly where vendor messaging often breaks down.
Too many providers use one version of the value proposition for every stakeholder. They sell the same benefit to the CIO, the CFO, the business owner, the enterprise architect and the end user.
Enterprise transformation does not work that way.
A better approach is to translate the same solution into stakeholder-specific value.
| Stakeholder | What they need to hear | Messaging angle |
|---|---|---|
| CIO | The roadmap is controlled, scalable and aligned to business priorities | Modernise without adding unnecessary complexity |
| CFO | The investment has measurable commercial logic | Reduce cost, protect margin or unlock revenue faster |
| Enterprise architect | The solution fits the wider application and data landscape | Support integration, interoperability and long-term coherence |
| CISO | The change does not expand risk unmanaged | Build security, access and compliance controls in early |
| Business unit leader | The programme improves practical outcomes | Improve speed, customer experience, productivity or decision quality |
| Operations team | The change will not create hidden workload | Make adoption realistic and implementation manageable |
This matters because enterprise buyers are increasingly judging vendors on whether they understand the internal politics of transformation.
A vendor that only explains product capability forces the buyer to do the translation work internally. A vendor that explains business value, stakeholder impact and implementation reality becomes easier to sponsor.
The build versus buy debate is still live
Another recurring theme was the tension between building internally and buying external solutions.
This is not a simple preference question.
Some organisations have relied heavily on consultants and external providers, then found themselves exposed when knowledge sat outside the business. Others have tried to build custom solutions, only to discover that maintaining them becomes difficult when key people leave or when the business needs to scale faster. Some are now building stronger internal hubs to retain knowledge while still buying specialist components where it makes sense.
For vendors, this is a major positioning issue.
If buyers are worried about vendor dependency, an aggressive “replace everything with us” pitch can make that concern worse. If they are worried about internal delivery capacity, a “you can build this yourself” argument may also fail.
The opportunity is to position the vendor as an enabler of strategic control.
That means showing how your solution helps the buyer:
- Avoid unnecessary custom build
- Reduce dependency on individual internal experts
- Integrate with existing platforms
- Retain ownership of data and process knowledge
- Replace components if the roadmap changes
- Build internal capability over time
- Avoid being locked into a transformation path they cannot reverse
This is especially relevant for SaaS, cloud, data, AI, automation and integration vendors.
Buyers may want external capability, but they do not want to lose architectural control. They may want speed, but not at the cost of future flexibility. They may want modern tooling, but not a new dependency problem.
The best vendor message is not “buy instead of build”. It is “buy the right components in a way that strengthens your internal transformation capability”.
Data quality is the hidden blocker behind legacy transformation
Legacy modernisation is rarely just an application problem.
It is a data problem.
Roundtable participants repeatedly raised data quality, data ownership, data literacy, unstructured data, context and scalable architecture as barriers to AI, IoT and broader transformation. One discussion referenced that 63% of companies lack adequate data for AI, while another highlighted that 95% of AI pilots fail to generate meaningful business impact. Whether those figures are used in a sales deck or simply treated as market context, the message is clear: transformation is limited by the quality and usability of enterprise data.
For vendors, this creates an important opening.
Many buyers cannot move quickly because their data is trapped across older systems, inconsistent formats, unclear ownership models and fragmented processes. They may have modern AI ambition, but the underlying estate is not ready. They may have IoT opportunities, but data latency, proprietary sensor formats and network variation make scaling difficult. They may want automation, but process exceptions and undocumented workarounds undermine repeatability.
This is where vendors can create value before the buyer is ready for full-scale replacement.
Useful vendor-led conversations include:
| Data challenge | Why it blocks transformation | Vendor opportunity |
|---|---|---|
| Fragmented data across legacy systems | Buyers cannot create a single operational view | Offer integration, data fabric, MDM or harmonisation capability |
| Poor business context | AI and automation tools cannot interpret data accurately | Help connect data to business meaning and process logic |
| Unstructured data | Valuable information is hard to govern or use | Support classification, extraction, knowledge graphs or data literacy |
| Unclear ownership | Teams cannot agree who controls or validates data | Provide governance workflows and stewardship models |
| Low data quality | Pilots fail when scaled into real operations | Build quality checks into implementation and reporting |
| Data latency | AI and IoT use cases cannot operate reliably | Help assess real-time requirements and infrastructure readiness |
The strongest vendors will not treat data readiness as a technical prerequisite the buyer must solve alone. They will make it part of the value proposition.
Security must be built into the transformation story from the first conversation
Digital transformation expands the attack surface.
That came through clearly in the cybersecurity discussions. Cloud adoption, APIs, IoT, automation, remote work, AI-generated code and connected infrastructure all create new risk. Participants discussed zero trust, digital sovereignty, vendor management, supply chain exposure, AI-generated vulnerabilities, data security, cloud dependency and the need to build security into infrastructure from the beginning.
For vendors, this is not a separate issue from transformation selling.
If your solution touches data, cloud, AI, integration, workflow automation, APIs or infrastructure, the buyer will eventually ask how it affects security and compliance. If that conversation happens late, it can slow or derail the deal.
It is better to bring security into the commercial conversation early.
That does not mean turning every sales meeting into a technical compliance review. It means showing that you understand the buyer’s internal approval path.
A stronger vendor narrative includes:
- How access and identity are managed
- How data is protected across environments
- How the solution supports auditability
- How APIs and integrations are secured
- How cloud regions, sovereignty and exit planning are handled
- How AI or automation outputs are monitored
- How implementation avoids adding unmanaged shadow IT
- How security teams can be involved without blocking progress
This is especially important in regulated and infrastructure-heavy industries.
Buyers do not want security added at the end as a control layer. They want confidence that transformation will not create a new set of risks that someone else must clean up later.
In enterprise transformation deals, security is not only a technical requirement. It is a buying confidence issue.
Transformation also depends on hidden knowledge
One of the more subtle but important insights from the roundtables was the role of undocumented knowledge.
Legacy transformation often depends on what people know but have never formally written down. Business rules, exceptions, user behaviours, operational compromises, integration quirks and historical decisions may sit with long-serving employees, architects, analysts, engineers or business subject matter experts.
If vendors ignore this, implementation risk increases.
A transformation programme can fail because the system migration was wrong, but it can also fail because the vendor and buyer misunderstood how the business actually works.
That is why some leaders described the importance of open questioning, coaching techniques and collective intelligence during ERP and architecture transformation. The aim is not only to document systems. It is to uncover hidden assumptions across IT and business before they become delivery problems.
Vendors can use this insight in a practical way.
Instead of beginning with platform demos, begin with discovery questions that prove understanding:
- Which processes depend on this legacy system today?
- Where does business logic sit outside formal documentation?
- Which teams know the exceptions?
- Which integrations are business critical but poorly understood?
- Which manual workarounds keep the current process running?
- Which data fields are trusted by the business, and which are not?
- Which stakeholders would be affected if this component changed?
- What would make the first phase feel successful to operations, finance and IT?
These questions build credibility because they reflect how transformation actually happens inside enterprise environments.
They also help vendors avoid superficial discovery. Enterprise buyers know when a provider is only looking for enough information to position its own product. They respond better when discovery helps them understand their own transformation risk more clearly.
What vendors should change in their sales approach
The sales strategy for legacy transformation deals should be more disciplined than a standard product-led pitch.
The buyer is dealing with long timelines, internal politics, risk ownership, budget scrutiny and competing priorities. A vendor that sounds impatient, simplistic or overly optimistic will struggle to build trust.
Instead, vendors should make five changes.
1. Sell the first credible step, not the whole transformation
Buyers may have a multi-year roadmap, but they often need a near-term decision that can survive internal scrutiny.
Make the first step specific, valuable and low risk. Show what can be achieved in 90 to 180 days. Connect it to a bigger roadmap, but do not make the buyer commit to the full vision before they have proof.
2. Make integration a primary benefit
If your solution works with legacy systems, say it clearly. If it reduces integration pressure, prove it. If it can support phased migration, show the pathway.
Enterprise buyers are not only buying capability. They are buying compatibility with a difficult current estate.
3. Quantify value in business terms
Modernisation language is not enough. Buyers need a commercial case.
That might include faster pricing changes, reduced manual work, improved customer journey efficiency, lower maintenance cost, fewer system dependencies, better data quality, reduced risk exposure or faster product launches.
The important point is to connect technical change to a measurable business outcome.
4. Address capacity honestly
Transformation requires time from IT and business teams. Buyers know this. Vendors lose trust when they underplay it.
Be clear about what the buyer must provide, where internal capacity will be needed, and how your approach reduces the burden.
5. Bring governance, security and architecture into the early story
Do not wait for procurement, architecture review or security assessment to introduce these topics.
Show that your solution fits the wider transformation environment from the start. This makes the buyer’s internal sponsorship job easier.
A practical messaging framework for vendors
For vendors selling transformation into legacy-heavy enterprise environments, the strongest message usually follows this structure:
| Message layer | What to communicate | Example positioning |
|---|---|---|
| Recognition | Show that you understand the current estate | “Transformation cannot ignore the systems still carrying critical operations.” |
| Risk reduction | Show how you lower disruption | “We support phased modernisation without forcing a high-risk replacement event.” |
| Business value | Tie change to commercial outcomes | “The first phase focuses on faster decision-making, reduced manual effort and clearer data.” |
| Integration | Prove compatibility | “The solution is designed to work across legacy, SaaS, cloud and data environments.” |
| Governance | Address approval barriers | “Security, compliance and architecture stakeholders are built into the implementation model.” |
| Scale | Show how value expands | “Once the first use case is proven, the model can extend across additional processes or business units.” |
This turns the vendor from a tool provider into a transformation partner.
That is where the enterprise opportunity sits.
The vendor opportunity
Enterprise buyers stuck with legacy systems are not standing still. They are actively looking for ways to modernise without creating operational chaos.
They need partners who understand application landscapes, data foundations, cloud trade-offs, AI readiness, stakeholder politics, hidden business knowledge, security requirements and measurable outcomes.
That is a demanding buyer environment, but it is also a valuable one.
The vendors that win will be those who can help buyers move from complex current-state reality to credible next-step progress.
Not by overselling transformation.
By making it safer, clearer and easier to fund.
For IT solution providers, the commercial question is simple: are you selling the future state, or are you helping buyers navigate the reality that stands between today’s estate and tomorrow’s operating model?
If your team wants to understand where senior enterprise IT leaders are actively prioritising transformation, legacy modernisation, AI readiness, cloud, data and security investment, get in touch with us here: