No central system. Most things happen over email, WhatsApp, and spreadsheets. There is no single place where the state of the business lives. Different people have different versions of the truth. Things fall through the cracks. The answer to “where is this?” is usually a phone call.

The good news is that this stage is actually the most tractable. There is no legacy to work around, no entrenched system to unpick. The challenge is sequencing it correctly.

The mistake most businesses at this stage make

The temptation when you can see all the problems is to fix all of them at once, either by buying a comprehensive platform that promises to handle everything, or by starting a large development project. Both usually fail. The platform forces you to adapt your processes to fit the software. The large project takes too long, the requirements change mid-build, and what ships does not match what the business needs. The businesses that make the most progress start with something specific, build it properly, prove it works, and use that as the foundation for the next thing.

How to pick what to fix first

• Where do things fall through the cracks most often? The process that generates the most “I thought you were handling that” conversations.
• Where does the same information get entered more than once? Every manual transfer is an error waiting to happen.
• Where does someone always have to ask someone else? If a recurring question can only be answered by a specific person, that information is in the wrong place.

What to build first

The specification is simple: a clear input, a clear output, no manual steps in between, and a record that gets created automatically. Do not overbuild. The first version should do one thing reliably for the standard case, and it needs to be something real people will actually use.

• Job or order management, a single place where every job exists, with a current status, an owner, and a history.
• Approval workflows, replace email chains with a tracked, structured flow.
• Client or contact records, one place where everything about a client lives.
• Invoice and document processing, automate the receive–review–approve–pay flow.

What good looks like

• People actually use it, if the team reverts to the old method within a month, the system failed. Usually it needs to be simpler, not more sophisticated.
• It creates a record automatically, who did what, when, and the outcome.
• It handles the exception, not just the rule, routes edge cases to a person rather than failing silently.
• It connects to what you already use, email, accounting software, so the transition is gradual.

What this is worth

A simple job management system for a 20-person business typically saves 15 to 25 hours a week across the team. At an average fully loaded cost of £35 an hour, that is £27,000 to £45,000 a year, and the cost to build it is usually a fraction of the first year’s saving. The more important number is the growth it enables: a business on email and spreadsheets has a growth ceiling set by its people’s capacity to handle everything manually.

About Alfaveo

Alfaveo builds custom software that connects to your existing systems and handles the processes they were never designed for. We start with a working prototype in 10 business days, real UI, real data, real workflow, so you can see exactly what you are getting before committing to a full build.

If what you have read here describes your situation, the most useful next step is a 30-minute conversation. No proposal, no pitch, just an honest assessment of what is worth fixing first and roughly what it would take.