Balancing Business as Usual & Digital Transformation: Tips for SMEs

I burned $40,000 on a warehouse management system that sat unused for six months because I tried to implement it while running a 140,000-square-foot facility at full capacity. Worst decision of my scaling phase.

Here’s what I learned the hard way: you can’t digitally transform everything at once while keeping the lights on. Pick ONE process that’s causing you daily pain and automate just that. When I finally got smart about it, I stopped trying to overhaul our entire operation and focused exclusively on our returns process. It was eating 12 hours of staff time per week and creating customer service nightmares. We implemented a simple returns portal over a weekend, trained the team on Monday, and by Friday we’d cut that time to 3 hours. More importantly, the warehouse team actually used it because it solved a problem they felt every single day.

The practical tip that saved me? Run your digital transformation like you’re running two businesses simultaneously. Your existing operation is Business A, which pays the bills today. Your transformation is Business B, which you’re building in 90-minute blocks. I literally blocked my calendar every Tuesday and Thursday from 6 a.m. to 7:30 a.m. just for implementation work. No emails, no operations fires, just focused transformation time. My team knew those blocks were sacred.

Most SMEs fail at this because they treat digital transformation like a side project that happens “when we have time.” You’ll never have time. The warehouse will always be short-staffed. The customer will always need something urgent. You have to ring-fence specific hours and protect them like you’d protect payroll day.

The other mistake is hiring consultants to transform your business while you keep running it. That’s like hiring someone to raise your kids. You need to own this. I spent those morning blocks learning our new systems alongside my team. When something broke at 2 p.m., I could actually help fix it instead of waiting for a consultant callback.

Start small, protect your implementation time like it’s revenue-generating work, and only move to the next transformation after the first one is running without you touching it for a full week.

The practical tip I give every time: stop calling it transformation. The word sets up the wrong expectation. It implies you’re replacing the existing operation with something new. Most organizations can’t pause operations to rebuild them. What they can do is improve one workflow at a time while everything else keeps running.

The framing that works: treat it like a maintenance schedule, not a renovation project. You don’t shut the restaurant to repaint it. You pick the quietest Tuesday and start with the back room.

At Microsoft, I saw this pattern repeatedly with mid-market customers. The ones that got stuck started with the biggest, most visible system: their ERP, their main product, their customer database. The ones that moved quickly started with a problem they could solve in 90 days without touching the core business. Automating a report that was taking someone eight hours a week. Connecting two systems that had never talked to each other.

The projects that held together also had an executive sponsor willing to limit scope publicly rather than keep adding priorities midstream.

Two things matter for continuity that usually get skipped: give the new workflow an explicit owner, and define what happens if it breaks. Not a crisis plan, just a clear answer to “if this fails Thursday, who owns it and what’s the fallback?” Teams that skip that step revert to the old process the first time something goes wrong, and momentum dies there. I’ve watched that happen more than once.

I run IT for a university of about 60,000 people, and the existing operation is not something I am allowed to pause while we modernise. Most SMEs get this backwards. They treat the current operation as inertia to push through, when it is closer to a contract they have already signed with the people who pay them.

The tip is unglamorous. Write down what the current operation owes people before you touch it. Response time on the thing customers phone about. Hours the system has to be up. Who gets called at two in the morning. What the fallback is when that fails anyway.

Most small firms have never put this on paper. Which means a transformation project has no way of telling when it has broken something. The damage surfaces as churn a few months later rather than as a failed deployment, and by then nobody connects the two.

We formalised ours under ISO 20000 and ISO 22301. That is heavier machinery than an SME needs, and the principle underneath it fits on one page. Once the baseline is written down, every proposed change gets checked against it before anyone commits to a date. Stability stops being the thing that argues against modernisation and becomes the constraint the modernisation is designed around.

The advice we give SME clients is to run digital changes in parallel with the old system for one full cycle before switching over completely, not as a phased rollout in theory but as an actual overlap where both exist at once. A retail client wanted to move their entire booking process online in one weekend. We talked them into keeping the phone line staffed for a full month after launch, even though it felt redundant.

That overlap caught a booking bug that would have quietly lost them a full week of appointments if the phone line hadn’t been there to catch the calls that fell through the online form. The bug wasn’t obvious from the analytics. It only showed up because a real person was still available to notice customers getting stuck and asking about it directly.

The practical tip: budget one extra month of the old process running alongside the new one, even when it feels wasteful. Cutting over completely on day one saves a small amount of short-term cost and risks a much bigger loss if anything breaks quietly in week one, when nobody trusts the new system enough yet to complain loudly about it.

My primary advice is to secure organizational alignment and create a phased, fundable roadmap so day-to-day operations are not disrupted while you transform. In my work, the harder problem is clarifying what the engineering team must deliver, what skills need development, and how the effort will be funded. One practical tip I learned is to start with a focused, in-depth assessment that produces a concrete plan showing what to migrate, in what order, training needs, and the expected cost trajectory. That assessment also surfaces funding pathways many SMEs overlook, such as hyperscaler credits, co-investment programs, and hardware buyback options, enabling a migration you can actually execute while maintaining operations.

The mistake many SMEs make is digitizing exceptions instead of fixing the standard path. Custom workarounds feel urgent, so leaders automate edge cases while the main operating rhythm stays messy. That creates expensive complexity. Real transformation begins by tightening the default process, reducing decision variation, and making routine actions easier to repeat across teams. Consistency is the real multiplier.

A practical lesson we use is to track handoff failure as closely as output volume. Most operational drag comes from unclear transitions between sales, delivery, finance, or support, not from the tasks themselves. If ownership changes hands without context, even strong systems underperform. SMEs gain more by cleaning up two critical handoffs than by launching a broad digital program that never addresses execution discipline.

Pick one bottleneck and automate that first. Not the whole operation. Most SMEs try to transform everything at once. Then it breaks, because the team’s learning new software while still doing the job in front of them. What’s worked for me is simpler: let the new piece run beside what already works. Don’t replace it on day one.

The setup can’t add a task to anyone’s plate either. A tool that needs someone writing prompts or babysitting a dashboard is just another job stacked on a full day. That’s usually where these projects stall. The work has to be done for the business, not handed to it.

Phone handling is where I see this most in home service companies. A missed call is a missed job. An agent that answers in under 60 seconds and books straight onto the calendar can run around the clock. Nobody on staff has to learn new software to make it work.

Start with the process that annoys everybody and earns nothing.

The usual advice is the opposite. Go where the value is, which in practice means an SME rebuilding its ordering system, its checkout or its client database first, because that is where the money runs through. If you break one of those while learning, you are not running a project any more, you are running an incident, and the business will refuse the next three good ideas because of it.

We watched a client attempt exactly that, replacing the system that took their orders during their busiest quarter because the return looked biggest there. They spent about 6 weeks running two systems in parallel, both half right, and the transformation was abandoned. Not because the software was wrong. Because nobody had capacity to learn a new tool while also keeping the revenue arriving.

The tip is to pick something low stakes and universally irritating first. Expense claims, holiday requests, the shared drive nobody can find anything in. No customer is lost if it goes wrong, everybody notices when it goes right, and the team learns how a rollout works on something forgiving. Then you have a group of people who have been through one successfully and will believe you next time.

Sequence matters more than tool choice. Order the changes so the first one is allowed to be imperfect, and put the money critical systems third or fourth, never first.

Publish what is broken, on purpose, where the staff can see it.

The hardest part of changing systems is not the software. It is the fortnight where half the business runs the new way and half runs the old, and everybody is reporting the same fault to an owner who is also doing their day job. Trust drains fast in that window, not because things break, which people expect, but because nobody can tell whether anyone knows.

So during our last change we kept one page at the front desk listing every known fault, who had reported it and the date it would be looked at. Twenty-two things went on that sheet in the first two weeks. Eleven of them turned out to be the same fault reported by different people, which we would never have discovered otherwise, and four were things we had believed were finished.

It cost nothing and it stopped the repeat reporting almost immediately. Staff checked the sheet, saw it was already there, and got on with their morning.

What I would say to another owner is to accept that you are running two versions of the business for a while and manage that openly. The ones who come out of it badly are the ones who pretend the transition is not happening, then wonder why people are quietly keeping the old spreadsheet going.

Pick one workflow that’s costing you the most manual hours each week and automate that single thing before you touch anything else. I built my digital products business while still running day-to-day operations, and every time I tried to overhaul multiple systems at once, both the new project and the existing business suffered. The wins came from isolating one bottleneck, fixing it, then moving on.

Run a two-week time audit first. I had my team track where every hour went, and we found that a large share of our weekly capacity was going to repetitive customer communication tasks. We automated that one category with a simple sequence tool, freed up those hours, and used them to build and test our first digital product line.

That freed-up capacity created space for the next improvement without pulling anyone off their existing responsibilities. Solve the biggest time drain first, prove it works, then layer the next change on top of a team that already has breathing room.

I run Kelley & Dawson Service in Wichita, where 24/7 HVAC and plumbing work means transformation can’t interrupt the day’s calls. My rule is: digitize the habit that already keeps customers comfortable, not the thing that looks flashiest.

For us, that habit is documentation. Every HVAC visit already includes checklist items, measured system data like temperature, pressure, airflow and CO testing, visible wear notes, and prioritized recommendations.

That became the best place to improve digitally because it helps operations immediately: cleaner handoffs, better follow-up, and less “what did we tell this homeowner last time?” It also works for indoor air quality visits, where humidity, airflow, duct condition, and filter performance all matter over time.

My practical tip: before buying or building anything, write down the exact field notes your best employee already captures. If your process doesn’t work on a clipboard, software will just make the confusion faster.

I started HomeBuild as a windows and doors company in 2004 and grew it into roofing services as an Owens Corning Certified contractor while keeping the same owner-supervised process on every job.

We rolled out the new roofing division by applying the exact same estimate and approval standards already used for siding and door replacements.

One practical step was bringing Synchrony financing into the workflow so customers could complete applications online during the initial visit.

This kept crews focused on field work and let the core business run without separate teams or delays.

Having spent 16 years running Social Design House and guiding growth-focused companies through digital strategy, my advice is to abandon massive, long-term operational overhauls in favor of rapid, low-risk prototyping.

When we looked to streamline our agency’s operations by merging our EOS leadership tracking with our project management tools, I didn’t derail daily client work with a huge IT overhaul. Instead, I used AI vibe coding to build a rough, functional MVP in a few hours to test whether the concept worked before making any real operational shifts.

My practical tip is to build lightweight AI working partners—like custom-prompted Claude projects—to immediately fill operational and skill gaps within your existing team. Rather than spending months shopping for enterprise software, prompting an AI assistant to act as an operational visionary or analyst allows your current team to execute digital initiatives right away without disrupting daily operations.

An Expiration Date for Every New Tool

For SMEs, it is easy to slowly build up a collection of subscriptions and tools. In a marketing firm, you often see fragmented tools for reporting, AI content assistance, project management, and contact monitoring, in addition to SEO research and automation—employees still maintain their own spreadsheets because the main system does not reflect how they actually work.

What I would recommend you do is treat any new tool like a 60-day or 90-day operating experiment. It’s best to schedule the cancellation decision on the day you buy it. Schedule a review date right away and, if possible, ask the assigned person to demonstrate what actually changed in the workflow. I am not impressed with usage numbers; employees can check into a platform daily, yet still duplicate some of the work elsewhere. It’s best to show that something tangible actually makes a difference. This way, the digital transformation does not add one more layer of work while the business is trying to run as usual.

I’ve been in the trades for over 30 years, and the biggest transformation I’ve navigated wasn’t a single tech upgrade—it was learning to layer new systems onto existing operations without breaking what already works. When we added smart home integration services at West Sound Comfort, we didn’t overhaul our entire workflow overnight. We folded it into jobs we were already running—HVAC installs, electrical work—so techs could learn the new technology in familiar territory.

The practical tip nobody talks about: use your existing customer relationships as your testing ground. Our 95% customer retention rate meant we had loyal clients willing to try new offerings with us. That trust gave us room to learn without the pressure of proving ourselves from scratch.

The mistake I see SMEs make is treating digital transformation like a separate project with its own lane. It isn’t. When we started offering smart thermostat integration alongside our mini-split installs, it wasn’t a new department—it was just the next logical step in a conversation we were already having with the homeowner.

Protect your core operations first. The charity auction I run for our local food bank taught me the same lesson—you can’t build something new if you’ve neglected what keeps the lights on.

The SMEs I talk to usually have the new system and the old spreadsheet running side by side for months, as a safety net. That’s where it dies. Nobody has the hours to double-enter, so people default back to the spreadsheet and the new tool turns into shelfware somebody’s still paying for.

The tip that worked for us: pick one workflow you already measure, and cut over on a date instead of running both. Ours was outreach, because we knew the reply rate before we touched anything, so when the new setup got us roughly 5x better response rates, nobody had to argue about whether it felt better. Everything else stayed exactly as it was for months. That put us behind our own rollout plan by a fair bit, which nobody loved at the time.

Maintain a Plan B for Automation

In our reputation management work, mistakes can quickly become public when automated. I tell the team what should be done when the system makes a mistake before automating reviews, monitoring, responses, or escalations. A two-star review can be handled as normal; one involving a safety issue, a legal threat, or a complaint against employees should be treated differently. The automated procedure should allow staff members to pause it and handle sensitive scenarios manually.

It’s best to define a turn-off switch for every meaningful automation. Pick an individual who can pause it, create a manual backup process, and set hard rules for when they need to intervene. Run these scenarios on the live site without your system in advance. On the one hand, you let automation do routine work, but on the other hand, you give control back to experienced employees who use human judgment when it needs to be exercised.

One tip that still works is to appoint a translator, not just a project owner. In smaller businesses, change can stall when leaders talk about goals while frontline teams focus on daily problems. We need someone who can turn plans into clear steps that people can follow. This person helps both sides understand what needs to happen.

We also rely on this role to spot problems before rollout. They can catch unclear terms, missing approvals, or steps that were never written down. We find that this helps teams feel prepared instead of pushed into change. Transformation works best when the plan fits real work and people know how to use it.

My advice is to start with an integrations audit before buying another tool. Map the systems your team uses every day, then look for places where people are re-entering the same information, maintaining duplicate records, or checking multiple platforms to get one answer. Those friction points usually show you where a small digital improvement can have the biggest effect without disrupting the work that already needs to get done.

One practical change that helped our team was combining our project tracker and content calendar into a single workflow. Blogs, emails, and campaigns now move through the same process with clear owners and statuses. That cut down on duplicate check-ins and made it much easier to adjust when priorities changed. For a smaller team without dedicated operations or IT support, digital transformation doesn’t have to mean replacing everything. It can start with getting the tools you already use to work better together.

For SMEs trying to keep operations running while moving forward on digital transformation, start by getting clear on the problem you are solving and make sure the frontline team agrees the pain is real. When I introduced a Digital Build Plan, the breakthrough was listening to technicians about how much time they were losing hunting for the right work orders and assembly instructions, then building the new approach around that daily friction.

If I have to give one practical tip, that would be, find a respected team member who can be a champion and act as an advocate for the change. The change is reinforced peer to peer, not just pushed top down. If the new process is genuinely valuable and easier, adoption follows faster because people feel the improvement in their daily work. Keep it simple, train regularly, and focus the small rollouts on removing a visible bottleneck rather than trying to digitize everything at once.

At WAJ Technology, I’ve learned that digital transformation isn’t only about introducing a new system. A big part of it is making sure the team has enough time and support to actually get comfortable with the change without affecting their daily work.

One practical thing that has worked well for us is having a proper training period. We stay closely involved with the team, help them step by step, and follow up on their work while they’re getting used to the new system. This way, we can solve issues early and make sure the transition doesn’t slow things down.

My advice to SMEs would be not to rush the process. Give your team the support they need, and focus on making the new system genuinely easier and more organized rather than simply replacing the old way of doing things.

My advice to SMEs is to digitize the part of the business that customers already find frustrating.

For Packur, that was quoting. Custom packaging usually involves too many emails before the customer even knows whether an order fits their budget. We could have started by digitizing internal reports or dashboards, but that would not have changed the customer’s experience as much.

So we focused on making product options and pricing clearer online. It did not remove the need for human support, but it made the conversation more useful when customers did contact us.

The practical tip is to avoid digital transformation that only makes the business look modern internally. Start with the step where customers lose time, lose trust, or ask the same question again and again.

Small companies get digital transformation backwards when they let change touch the same layer that customers or staff currently rely on to get paid and served. The operation that keeps revenue coming in is not the place to experiment; it is the last place you touch. My practical tip is to build the new process as a shadow track that runs alongside the existing one, doing the same work quietly, without anyone downstream depending on its output yet. Let it fail there, get corrected there, and only route real customers or real decisions through it once it has earned trust on its own, unwatched. Owners often reverse this because the new system feels urgent and the old one feels boring, so they retire support for the working process before the replacement has proven itself. That sequencing choice, not the technology itself, is usually what breaks small operators.

I’m Aleksa Baburska, Director of Solution Acceleration at Devox Software. I have 7 years of experience in custom software development with an inclination to platform modernization.

Incremental transformation should be your second name. SMEs usually can’t allocate substantial budgets to modernization initiatives; that’s why they risk abandoning attempts altogether. To avoid this unfortunate situation, you need to act gradually, starting with the most value-driven operations or bottlenecks. Doing it without downtime is completely possible once you treat the modernization process as a sequence of small steps. Expert developers know how to modernize without disruption; they have techniques for that. Moreover, you don’t need to hire a full dedicated team for this project. Consider staff augmentation or similar engagements to save costs.

For me, innovation is core, and that’s been every part of my business. Every 6 months, everything changes. We’re in a world that is rapidly, rapidly changing. I’ve made the lifeblood of my business change and innovation. Every single month, we do an all-hands, and I showcase the painting of William Turner’s The Fighting Temeraire. It’s a gorgeous painting of a famous ship that won us the Battle of Trafalgar against Napoleon. This painting, done only a few years later, shows the ship being towed to the scrap heap by a new kind of ship, a steam engine. The painting is a reminder that innovation always trumps past glories. I’m constantly instilling in my team this idea that we must always change what we’re doing, because everything is changing around us, and they’re encouraged to spot gaps and opportunities for change. If we don’t stay on top, we won’t survive.