
Digital transformation for small business: where to start when nothing is connected
Digital transformation for small business sounds like a programme, but it usually starts with something smaller: the spreadsheet three people keep, the customer details that differ across four systems, the mailbox that serves as the archive. This article is about the order: what to put right first, so that every next step has something to stand on.
Do not start with new software. Start with a drawing of which data sits where, and where people retype it.
Name one leading system for each kind of data: customers, products, employees, finance. Everything else reads from it.
Get sign-in right first: one account per employee, with multi-factor authentication. Only then integrate, and leave automation until last.
Digital transformation for small business and SMEs starts with a drawing
Most small businesses are not undigitised. They have accounting software, a CRM or a customer list, Microsoft 365, a scheduling tool, a web shop or sector software. The problem is that these sit side by side. Data moves from one to the next through a person retyping it, an export someone runs every Monday, or an email with an attachment.
So start with one drawing on an A3 sheet or a whiteboard:
- Which systems exist, including the spreadsheets and shared mailboxes that in practice work as systems.
- Which data they hold: customers, products, orders, employees, hours, invoices.
- How data moves from one to another, and who moves it.
- Where it goes wrong today: duplicate customers, a price that differs in two places, an order stuck between two systems.
That drawing is the most useful document in any digital transformation for small business. It shows where the time goes and where the errors come from, and it stops you buying software for a problem that sits somewhere else.
One source for each kind of data
The biggest gain rarely comes from a new system, but from an agreement: for each kind of data there is one leading system, and that is where it is changed. Every other system reads it from there.
- Customers and contacts: the CRM or the accounting software, but not both.
- Products and prices: the ERP or stock system, not the web shop and not a price list in a spreadsheet.
- Employees: the HR records, and from there the account in Microsoft 365.
- Files: one place with a fixed folder structure, not the laptop, the mailbox and a USB stick.
Write that agreement down and explain it. An integration between two systems that both think they lead does not make the problem smaller, only faster.
Start with sign-in: one account per employee
Before you connect anything, it must be clear who someone is. In many small organisations each employee has a handful of separate accounts with separate passwords, plus a few shared accounts where nobody knows who still has the password.
Make one account per employee the foundation, with multi-factor authentication, and let new applications sign in with it (single sign-on) wherever possible. That gives you three things at once: fewer passwords, permissions you can see in one place, and a leaver process that closes everything in one action.
The same foundation covers devices: laptops and phones that are centrally managed, so you know what exists and what is on it. How that workplace fits together is covered in our article on the digital workplace.
An order that works
No single order fits every business, but this one rarely goes wrong, because each step delivers something on its own:
- Take stock. The drawing above, plus a list of licences, contracts and who administers each application.
- The foundation. One account per employee, managed devices, a backup you have actually restored.
- Files in one place. Loose folders, email attachments and local drives moved to a shared environment with a structure and permissions per group.
- Choose the leading systems. For each kind of data, as above, and clean up the data in them.
- Integrate. Using the standard connectors the applications offer, so data is no longer retyped.
- Only then automate. Letting processes run on their own only works once the data is right and the systems talk to each other. That is a subject of its own, with its own decision per process.
Skip a step and you will meet it later: an integration built on dirty data, or new software nobody can administer.
Choosing new software when connection is the goal
Sometimes the drawing shows that an application is missing, or that an old one really has to go. Then, alongside the questions about features, ask these five:
- Which integrations already exist with the applications you are keeping, and who maintains them?
- Can it sign in with your existing accounts, so it does not become a user directory of its own?
- Can you get your data out, complete and in a usable format, if you ever leave?
- Where is the data stored, and on what terms does the vendor process it? If it involves personal data, you need a data processing agreement under UK GDPR.
- Who becomes the administrator in your organisation, and who at the vendor?
An application that wins on features and loses on these five makes the drawing busier rather than simpler.
Who does it, and how to keep it going
Digitalisation rarely fails on technology and often on time and ownership. Name one person who keeps the overview, even if they are not in IT, and for each application a key user who knows how it works and fields questions.
- Do one thing at a time. A new file environment and a new CRM in the same month asks too much of the same people.
- Bring people along before go-live. A short explanation and a place to ask questions stop everyone falling back on the old spreadsheet.
- Switch the old thing off. As long as the old list exists it will be updated, and then you have two sources.
- Look back after a few months. Is anything still being retyped? Are customers still duplicated? Those questions tell you whether it worked.
Where our work stops
What we do. We provide the IT foundation digitalisation rests on: accounts and multi-factor authentication, managed laptops and phones, Microsoft 365 and the file environment, backup, network and security, and an overview of licences and administrators. We also help with the inventory and the drawing. Integrations between applications and bespoke software for work no package covers are a separate service with us: software development.
Where it stops. How your work runs, which systems lead and who owns which process is your decision. We do not decide which step goes or which application wins: we put forward what the drawing shows, and the choice is yours. And packaged software stays with its vendor: we do not build a replacement ERP or till system, and we do not sell a package of our own.
Questions we get about this
The five that come up most.
What does digital transformation mean for a small business?
For most small businesses it does not mean replacing everything, but making the systems they already have fit together. Data sits in one place, is no longer retyped and is available to whoever needs it. New applications and automation come after that.
Where should a small business start with digital transformation?
With a drawing of which systems exist, what data they hold and how it moves between them today. Then put the foundation right: one account per employee, managed devices and files in one place. Only then choose a leading system for each kind of data and start integrating.
What is the difference between digitalisation and automation?
Digitalisation means making sure data and work are available digitally and in the right place. Automation means letting software carry out a step a person does today. Automation only works well once digitalisation is in order; otherwise you automate the errors.
Do we need to buy a new ERP or CRM first?
Usually not. The gain often lies in agreeing which existing system leads and in the standard connectors the applications already have. New software only makes sense when the drawing shows something is genuinely missing or an old application can no longer be connected.
Do you also build the integrations between our systems?
Yes, integrations and bespoke software for work no package covers are a separate service with us, alongside the IT foundation of accounts, devices, Microsoft 365 and security. What we do not do is decide how your work runs or which system leads; that is your decision. And we do not build a replacement ERP or sell a package of our own.
Further reading
What digitalisation connects to.
Shall we make the drawing together?
Tell us which systems you have and where it rubs today. We will map out which IT foundation is needed and in what order, so every next step has something to stand on.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.