Where the "we've always done it this way" syndrome comes from
Resistance to change does not come from bad intentions or laziness. It is a deep psychological mechanism that takes very specific forms at work. Research by Oak Engage in 2023 named the main sources of resistance: lack of trust in the organisation (41%), not knowing why the change is happening (39%), fear of the unknown (38%) and feeling left out of decisions (23%).
The comfort of the status quo and the real threat
People naturally prefer what they know. Even if current processes are inefficient, they give a sense of control and predictability. An employee who has managed orders in Excel for five years knows exactly how to do it, and fears that a new CRM will make their skills worthless. That is not irrational. It is a reasonable worry about their own position.
The trouble is that the comfort of the status quo is an illusion. A company that does not modernise its tools does not stand still, it falls behind. Competitors that have introduced sales automation or a dedicated ERP serve more customers, faster and at lower cost.
Take a simple example. A trading company with 30 salespeople keeps contacts in a spreadsheet. Each salesperson spends 45 minutes a day on manual data entry, searching contact history and preparing reports. That is over 300 working hours a month, close to two full-time jobs, spent on tasks a CRM would do automatically. And this does not count the leads lost in uncoordinated communication.
The role of leaders in keeping resistance alive
Resistance often starts at the top. Only 25% of organisations have employees who see change management as a strength of their senior leaders. When the management does not believe in the purpose of a transformation, or cannot explain it, the whole organisation gets a clear signal: better not to touch anything.
In B2B companies and small and mid-sized firms the problem is especially visible. An owner who built the company's processes personally over the years may treat changing them almost as a personal insult. "My Excel works just fine" is a sentence we hear regularly, and it is usually the start of expensive stagnation.
What outdated solutions really cost
Companies often see the cost of keeping old systems as zero, because "we've already paid for them". It is one of the costliest misunderstandings in business. The real costs of legacy systems are large, but they sit under the surface of daily operations.
Hidden costs of legacy systems
According to market analyses, organisations spend up to 60 to 80% of their IT budgets on maintaining existing systems, which leaves only 20 to 40% for innovation and growth. A company that spends $150,000 a year on IT could therefore lose up to $120,000 on patching old solutions instead of investing in tools that give it an edge.
There are also costs that are less visible but just as real: time lost on manual processes, errors caused by missing integration, delays in customer service and missed sales. UK research found that 48% of employees lose more than three hours a day because of inefficient systems. Over a year, that adds up to hundreds of thousands in lost productivity.
Another factor that rarely gets mentioned is staff turnover. Talented people do not want to work with tools from the previous decade. Young salespeople, marketers and analysts expect modern systems that help their work. Outdated tools add to frustration and departures, and recruiting and onboarding a replacement typically costs several months of salary.
Technical debt as a ticking bomb
Gartner estimates that companies spend up to 40% of their IT budgets on servicing technical debt. It works like interest on an unpaid loan: the longer you put off modernisation, the more you pay to keep what you have. Every patch, workaround and manual fix adds to the complexity of the system and the risk of failure.
90% of IT decision-makers admit that legacy systems stop their organisations from adopting new digital technologies, including AI and automation. This is not an abstract problem. It means a real loss of competitiveness in a market where customers expect faster and more personal service every year.
Five common excuses and how to answer them
Change needs arguments that speak to both logic and emotion. Here are the five excuses we hear most often from companies that put off transformation, and the answers that tend to work.
"Our current system works"
It works, but at what cost? "Working" and "working efficiently" are two different things. If people copy data between spreadsheets by hand, spend hours on reports a CRM could produce in seconds, or lose leads because nobody follows up automatically, that is not working. That is surviving.
"We don't have time for implementation"
The paradox is that companies have no time for implementation because manual processes eat it. Modern ways of building IT systems, such as phased rollouts, MVPs and iterative development, let you launch a core version in weeks instead of months. Every week of delay is more hours lost on processes that should be automated.
"It's too expensive"
A Forrester study on migration to a modern ERP showed a 265% return on investment over three years. Finance team productivity rose by more than 15%, operations teams by 12.5%, and companies saved more than $80,000 a year in legacy software costs. "Too expensive" is not an argument, it is a missing calculation.
"Employees won't adapt"
74% of employees are willing to adapt if they understand the purpose of the change and have proper support. The problem is not the people but how the change is communicated and carried out. Research shows that involving employees in implementation planning raises the success rate by 24%.
"We tried once and it failed"
One failed implementation does not mean that every one will fail. The most common causes are the lack of a clear strategy, too little communication and trying to change everything at once. This is exactly why a small-agency approach, with a dedicated team, phased delivery and constant feedback, succeeds far more often than buying an off-the-shelf product.
How to lead change successfully: a plan for decision-makers
IT transformation is not only about technology. It is mainly a project about people and processes. Here is an approach that keeps resistance low and raises the chances of success.
Step 1: diagnose and measure the current state
Before you propose a change, show with numbers that it is needed. How many hours a week does the team spend on manual tasks? How many leads are lost for lack of a system? What is the average response time to customer enquiries? Hard data replaces the subjective claim that "things work fine". A process audit is the first step that turns vague hunches into a concrete business case.
Step 2: start with quick wins
Do not try to turn the company upside down overnight. Pick the one process that causes the most frustration and automate it first. It might be automatic lead assignment in the CRM, one-click sales reports or connecting website forms to the customer service system. A fast, visible success builds confidence in the whole project.
Step 3: involve people, do not impose
Research is clear: in projects where employees help create the implementation plan, the success rate is 24% higher. You are not asking permission for the change, you are asking how to carry it out. People who feel like co-authors of a solution become its ambassadors instead of saboteurs.
Step 4: communicate openly and continuously
KPMG research indicates that companies that invest in clear communication see employee engagement rise by 30%. One email announcing "we are introducing a new system" is not enough. You need regular two-way communication: why the change is happening, what it means for each team, what support is available and what comes next.
Step 5: measure, adjust, repeat
Transformation is a process, not an event. Launching an MVP is only the beginning. What matters most is collecting feedback, changing course when needed and expanding functionality in iterations. Companies that pilot changes with a small group before a full rollout triple their chances of success.
Why a small-agency approach to IT works
Many companies that have been through a failed implementation fell into what could be called the boxed-solution trap: forcing unique business processes into the rigid frame of off-the-shelf software. It is like buying a suit off the rack and expecting it to fit as if it had been tailored.
Custom solutions vs off-the-shelf systems
Every company has its own processes, structure and organisational culture. A CRM for a logistics company will differ fundamentally from one for a marketing agency, in the whole logic of data flow and automation and not only in the set of fields. A dedicated IT solution is designed around a company's real processes, not the other way round.
Direct contact with specialists
In large software houses the client talks to a project manager, who talks to a team lead, who assigns tasks to a developer. In a small IT agency the decision-maker talks directly to senior specialists who understand both the technology and the business context. That removes misunderstandings, speeds up decisions and makes sure the final product really meets the company's needs.
Phased delivery against resistance
Instead of a months-long big bang project, the small-agency approach is iterative: a quick start with core functions, regular demos and feedback, then gradual expansion of the system. The team sees results in weeks, not months, which lowers resistance and builds momentum for change.
In practice it looks like this. In the first month we launch the base module, say contact management and a sales pipeline in the CRM. The team starts using the new tool at once, sees the benefits and begins to suggest ideas for further features. In the second month we add follow-up automation and reporting. In the third, integrations with email, calendar and the website. Each stage builds on the one before, and each success lowers resistance to the next step.
Technological flexibility instead of vendor lock-in
Modern custom solutions are built on open-source technologies and open standards, such as Laravel, Vue.js and PostgreSQL. The company does not become dependent on one vendor or a closed ecosystem. The system can be extended, connected to any outside tools and changed as business processes evolve. This is a basic difference from off-the-shelf platforms, where any non-standard change either costs extra or is not possible at all.
Change is coming: the question is whether you control it
The "we've always done it this way" syndrome is not harmless attachment to tradition. It is a real threat to profitability, efficiency and market position. According to McKinsey, 70% of transformation initiatives fail, and the main reasons are people's resistance and the lack of a change management strategy, not bad technology.
The good news is that resistance can be overcome, not by force but with a sensible strategy. Diagnosing the current state, involving the team, delivering in phases, communicating openly and showing quick wins are what turn a sceptical team into supporters of the change.
Companies that delay transformation pay for it every day in lost productivity, lost customers and growing technical debt. Those that act get tools that not only streamline operations but open new ways to grow.
In 2026 the gap between companies that embraced digital transformation and those that avoided it is clearer than ever. AI, advanced automation and intelligent CRM and ERP systems are no longer the future. They are the present for companies that win in their markets. The question is not whether to change but how quickly and how sensibly.
If you want a system built around your company's processes, get in touch. We help turn business goals into concrete IT solutions: dedicated CRMs and ERPs, process automation and integrations with the tools you already use. We start with an audit and a conversation about what is really holding your growth back.
