Small business digitalisation: start with one process

Digitalising a small business can start with one task, not replacing every tool. Choose a recurring process, assign an owner and measure where time is lost. Then choose the solution.

This guide shows how email, spreadsheets and phone conversations can become a clear workflow. The example is illustrative: it does not show a client's internal application or measured customer savings.

Digitalisation and automation are not the same

Digitalisation organises data, responsibilities and work status in a digital system. Automation carries out an agreed step without manual copying or sending.

A shared request register is digitalisation. Automatically assigning a request and sending a reminder before its due date is automation. A person can still review a request with missing data. Not every step needs artificial intelligence.

Which process should you digitalise first?

List 3 recurring tasks: handling enquiries, confirming orders, service requests or internal approvals. Ask the same questions about each:

• Frequency: how often does it happen each week and how many minutes of active work does it need?
• Errors: how often do you look for missing information or correct an entry?
• Ownership: who can explain the rules and decide on exceptions?
• Data: where does it originate, who may see it and can it be exported?

For the first pilot, choose a limited process with a noticeable problem, accessible data and a clear owner. If the rules change every week, agree them first. An infrequent task with few errors may not need a new application at all.

Example: from email to a clear service request

Imagine a small service business. A customer emails a request, an employee copies it into a spreadsheet and calls a technician. When the customer asks for an update, the team has to search for the latest agreement again.

The first version can cover just this workflow. Every step has a defined result, so nobody has to guess what happens next.

1. 1. Capture

   One request with contact details, a problem description and an attachment. It receives a unique reference.

2. 2. Check

   Missing information or a possible duplicate goes to the responsible person for review.

3. 3. Carry out

   An approved request gets an assignee, due date and visible status. Reminders follow the agreed rule.

4. 4. Complete

   The assignee records the completed work. The register keeps the outcome and change history.

This scope does not yet include route planning, inventory, billing or replacing accounting software. Add those connections only if needed and after checking feasibility. See business process automation for more detail.

Existing software, integration or a custom application?

Configure an existing tool first

If your software already supports forms, statuses and task assignment, check its configuration and how people use it. Another application may be unnecessary. Even a shared spreadsheet can be enough for a simple process with few users.

Connect systems when you copy data between them

If both tools do their job but data transfer is missing, consider business system integration. Before implementation, check data access, licences, duplicate identification and what happens when a transfer fails.

Build an application when you need your own workflow

A custom business application is an option when you need specific approvals, different access permissions and linked records that your current solution cannot support. You do not have to replace everything that already works.

How to measure whether the change helps

Track comparable requests before implementation and during the pilot. Separate active work from time spent waiting for a customer or approval. Also record corrections and requests with no assigned owner.

Illustrative calculation: 80 monthly requests at 15 minutes of active processing take 20 hours. If a comparable request takes 9 minutes during the pilot, processing takes 12 hours. The difference is 8 hours per month, before subtracting additional system administration and exception handling.

This is a calculation method, not a promise of savings. Freed capacity does not automatically become cash savings. Include development, onboarding, hosting, licences and maintenance when comparing costs. For ranges and scope boundaries, see how much custom application development costs.

What to check before regular use

• Exceptions: what happens with missing information, duplicate entry, a rejection or an unavailable external system?
• Access: can each person view and change only the data needed for their work?
• Recovery: who manages backups and has restoring the data actually been tested?
• Handover: who on the team accepts the result, helps users and receives fault reports?

Start with a limited pilot. Agree which record is authoritative and how work continues if something goes wrong. Two conflicting registers could bring back the duplication you wanted to remove.

Prepare a short description of your process

You do not need a technical document for the first conversation. Prepare answers to these 5 questions. Remove personal and other confidential data from any examples you share.

1. What event starts the work and what counts as completion?
2. Who is involved and who approves exceptions?
3. Which tools, spreadsheets and documents do you use?
4. How many cases do you handle and where do they usually get stuck?
5. What would the first pilot need to demonstrate to count as successful?

If a shared spreadsheet is the main bottleneck, read about moving from Excel to an application. For the steps from the first conversation to handover, see how we work together.