Large companies talk about digital transformation as a programme with a budget and a steering committee. For a company of forty people, it usually starts with a spreadsheet that has grown too important to lose.
The goal is the same at any size: fewer manual steps, data you can trust, and tools your customers expect. The path is different, because smaller businesses run into problems that big ones solve with headcount.
The obstacles we see most
- Knowledge lives in people, not systems. One person knows how invoicing really works, and nobody has written it down.
- Tools were bought one at a time. Accounting, sales and stock each have their own app, and none of them talk to each other.
- There is no one to own it. Without an in-house tech team, every change waits for an outside vendor.
- The budget is real money. A failed project is not a line in a report; it is this year’s margin.
Start with one process, not a platform
The most common mistake is trying to replace everything at once. A new all-in-one system promises to fix every problem, takes a year to configure, and lands on a team that never asked for it.
We start smaller. Pick the one process that costs the most time or causes the most errors, often order handling or invoicing, and fix it end to end. Map how it works today, automate the repetitive steps, and connect the two or three tools it touches. A few weeks later the team feels the difference, and the next step is easier to agree on.
The first project should pay for itself before the second one starts.
Keep what works
Legacy does not mean useless. An old system that holds ten years of clean customer data is an asset. Often the right move is to put a modern layer on top of it, an API or a simple internal app, rather than migrate everything on day one.
Own the result
Whoever builds it, make sure you own the code, the data and the accounts, and that the work is documented well enough for someone else to pick up. Dependence on one vendor is how small companies end up stuck again in three years.
Where to begin
Write down the three tasks your team repeats most each week and how long they take. That list is usually enough to find the first project. If you would like a second opinion, a short technical review will tell you what to fix first and what can wait.
