Did you have to accept a 30 per cent price increase for your internal communications platform? We didn’t. It began with a polite call from our vendor’s renewal team, framed as an AI opportunity. The AI features were nice in principle but largely unnecessary for us, as was the 30 per cent price increase.
What followed was a migration to a platform already included in our existing licence. This saved approximately €25,000 to €28,000 annually. That represents an 80 to 90 per cent reduction in enterprise communication spend. But the real story is not the savings. It is what the price increase revealed about how vendor lock-in works. Mid-sized organisations find themselves in this position far more often than they realise.
This article is for leaders of small to mid-sized companies who have been handed a renewal notice with numbers that don’t add up. If you’ve ever felt that your organisation’s bargaining power had quietly evaporated, not through any single decision but through the accumulated weight of defaults, habits, and infrastructure investments, this is for you.
A Framework for Understanding Vendor Lock-In
Michael Porter’s Five Forces framework identifies five structural forces that determine the competitive dynamics of an industry. One of those forces is buyer bargaining power. This explains what happens when an organisation becomes dependent on a single vendor. The more lock-in accumulates, the weaker the buyer position becomes.
Lock-in rarely arrives as a single decision. It builds through three types of moat:
Financial moats accumulate licence spend normalised by convention. When every team has the premium tier “because that’s what we use,” it stops feeling like a procurement choice and starts feeling like the default option. The cost becomes invisible until someone asks you to pay more for it. At that point, you no longer have the leverage to say no. Walking away has become expensive in its own right.
Cultural moats are the hardest to see and the cheapest to dissolve. They consist of tool habits and the user’s comfort zone. They are the collective belief that “Slack is just what we use.” Users develop emotional attachments to tools not because they’re technically superior but because they’re familiar. Cultural moats resist rational arguments about functionality. You cannot negotiate with habit or personal taste overnight.
Operational moats are the kind of lock-in that becomes visible only when you try to leave. Integrations, data export friction, and vendor-enforced exit barriers are structural dependencies that compound over time. The subtlest form is vendor behaviour change: a company raises prices and simultaneously tightens API quotas. This makes the migration timeline harder and the cost higher. This isn’t necessarily hostile intent. It’s a rational market exercise of supplier power.
Understanding these three moats transforms what looks like a pricing dispute into a structural problem with a structural solution.
Testing Alternatives: Five Moat-Breaking Questions
When evaluating any platform alternative, I use five questions that test whether the new option actually breaks one or more of the moats described above. They aren’t feature checklists. They are moat-testing heuristics.
1. Was the alternative already paid for and available? This tests the financial moat directly. If the capability already exists within your existing licence suite, you’re not looking at an incremental cost. You’re looking at freed-up spend from removing a redundant layer. The alternative was part of our existing subscription. It was paid for and waiting to be used with zero marginal cost.
2. What percentage of current usage is internal-only? This tests the cultural moat. If 90 per cent or more of your communication is happening between colleagues already on the same platform, you’re paying enterprise pricing for a tool that functions as an instant messaging product. The difference between the incumbent platform and the alternative for internal use is incremental, not foundational. After looking at our usage data, I estimated that 80 to 90 per cent of our usage fell into this category. This was confirmed by the post-migration retention numbers.
3. Were add-ons and integrations replaceable within your existing ecosystem? This tests the operational moat. Vendor lock-in features are only dangerous if you’re actively using them. If your integration stack sits primarily within your existing technology ecosystems, switching a communication layer doesn’t require rebuilding your infrastructure. It requires connecting tools that already share common foundations.
4. Was vendor-specific lock-in functionality actually being used? Enterprise platforms package dozens of features but only a fraction are actively deployed. If you’re not using version history, e-discovery, or advanced governance controls at scale, then you are paying premium pricing for the baseline feature set. Exceptions will exist and should be handled on a case by case basis.
5. Is historical data migration scope manageable by limiting retention? This tests exit friction directly. Not all historical data is equally valuable. Setting a pragmatic retention boundary, such as several years rather than decades, dramatically reduces migration complexity. This still preserves organisational memory at a usable level.
These five questions do not produce a vendor recommendation. They produce a structured way of thinking about whether a potential migration is structurally viable. They also highlight what specific barriers you would need to address to make it work.
Why ROI and Governance Need to Align
The idea of cleaning up our enterprise communication platform had been on the table for a few years. We had the same conversation at the last few renewal cycles. As data accumulates, so does governance and compliance risk. However, this growth in risk wasn’t quite enough to drive the decision.
The business case was straightforward. Annual licence spend was approximately €36,000. This worked out at €180 per seat for 200 users. By migrating to the alternative at zero incremental cost, we retained only 25 to 45 seats for genuine external collaboration needs. We projected annual savings in the range of €25,000 to €28,000. The payback period was approximately six months from project start against the one-off migration costs of €8,500. These savings secured board approval through the alignment of both governance and financial arguments.
Being able to communicate in the language your board understands demonstrates executive maturity. It shows an understanding of organisational decision-making psychology. Governance improvements were beneficial, but they weren’t the key that unlocked the door.
Once the door opened, governance posture became the reason for staying. That distinction matters for leaders who want their next platform decision to have a different outcome. If you know governance arguments stall in board discussions, lead with ROI and show governance as the structural advantage that emerges after the financial case clears.
Differentiation as Education, Not Policy
The cleanest insight from this migration was about user differentiation. It came through an unexpected mechanism.
We drew a boundary: the incumbent for business-to-business communications and the alternative for internal communications. No policy mandate, no justification workflow for premium tiers, no enterprise licensing review board. Just clarity about which tool served which use case. The runbook was a FAQ mapping “how do I do X in the alternative” to the equivalent incumbent workflow. It functioned as an education mechanism, not a compliance document.
This established a simple framework. Different tools serve different jobs. Whilst getting access to a licence on the incumbent requires approval, the decision is fairly black and white. This reduces friction. Developing shared understanding throughout the organisation dissolved the cultural moat. Education beat policy and mandates. It organically built intuition within the culture rather than forcing it through compliance. The people who needed the incumbent learned quickly that retaining access was justified by their actual workflow. The rest adapted to the alternative.
The Realities of Change Management
Memes and informal expression are a legitimate and predictable component of organisational change processing. Allowing them to run their course is an effective de-escalation strategy, if you can resist the impulse to manage them.
After the migration, teams needed time to process the change. This is the cultural moat resisting dissolution. Memes and informal expression were a legitimate and predictable component of organisational change processing. Users posted them in self-selected spaces where they felt comfortable expressing themselves. Rather than suppressing this behaviour, or forcing artificial positivity, I let it run its course. It took approximately three months. Users returned from the December break and simply moved on.
This is not a failure of communication strategy. It is the predictable arc of cultural adaptation. Even when the framing is clear and the business case is sound, tool transitions carry an emotional dimension that requires time to resolve. Meeting users where they are during transition, including letting them vent, is more effective than demanding compliance through messaging alone.
Lessons Learned, Mapped to Moats
Three mistakes shaped how this migration unfolded. Each one maps to the moat type it relates to, and each one offers a structural lesson for future projects.
Financial moat lesson: Start vendor selection from day one when cost pressures appear. The odds are stacked against you as a small to mid-size organisation in negotiation with a much bigger vendor. The only way to restore bargaining power is to have a credible alternative in hand. This means finding alternatives and evaluating them as soon as cost pressures appear. Ideally, you should have options planned before prices increase. Waiting for feedback during negotiations is only losing time and eroding leverage. The more you wait, the more you are locked in.
Operational moat lesson: Architect cross-organisation collaboration capability from day one. The alternative’s external channels were available at migration time but not implemented initially. In some cases, this configuration was changed and data was re-migrated to support some cross-org collaboration capabilities. This additional operational overhead and reduced interoperability during the interim period was entirely avoidable. If your organisation spans multiple entities or studios, cross-org collaboration capability should be part of the initial architecture, not a retrofit decision made after the platform cutover.
Cultural moat lesson: Build user differentiation into the operating model proactively. Don’t wait for a vendor price shock to trigger a remediation exercise in how your organisation uses tools. Enterprise licensing on every user should be unusual, not default. Differentiation between internal and external communication needs, or between operational roles that genuinely require real-time collaboration and those who don’t, is an operating model question, not a procurement response. The fact that we only needed 44 seats for genuine B2B requirements after retaining 200 was visible in hindsight. Making it visible in advance requires building differentiation into how you evaluate tool adoption from the start.
The Outcome (As It Actually Is)
- Pre-migration annual licence spend: €36,000 (200 seats at €15 per seat per month, Business+ tier)
- Post-migration annual licence spend: approximately €8,000 to €10,000 (44 seats retained for B2B.)
- Annual savings: approximately €25,000 to €28,000, or roughly an 80 per cent reduction in enterprise communication spend
- One-off migration cost: €8,500 (Transition vendor engagement fee)
- Payback period: approximately six months from project kick-off, or immediately upon timely completion.
Governance posture improved as a sustained benefit. This supports our differentiated and distributed IT organisation. It has structurally kept the right teams and data on the right tools.
Where This Leaves Us
The lasting advantage of this migration was not the savings, though those were meaningful and measurable. It was the restoration of bargaining power on every subsequent platform decision.
Defaulting enterprise-tier licensing to every user was the actual problem, not the incumbent platform itself. Vendors profit from conflating enterprise pricing with default access. They make premium tiers feel like the option you’d choose naturally, which is how financial moats form. Cultural moats then cement it through habit and comfort. Operational moats seal the deal through accumulated infrastructure dependencies.
Escaping that cycle starts with education rather than mandate. It requires treating differentiation as a behavioural question (who actually needs what?) rather than a procurement exercise (who should we approve for premium tiers?). It also demands starting vendor evaluation from day one when cost pressures appear, not after lock-in has already baked in through accumulated moats.
The structural transformation was never about replacing one platform with another. It was about realising that matching platform capability to actual user behaviour makes every subsequent decision cleaner and cheaper. You have restored the fundamental leverage that any buyer should have: the ability to say no.