Skip to main content

Workflow Software Development

Workflow software that moves work through defined states with an owner at each step. Built for UK firms in small releases, with the code in your account.

What Actually Breaks In A Business

Not tasks done badly. Work that stops moving.

An SOP describes how to do one thing well. A workflow describes how work travels between people and stages. They fail differently, and the second failure is far more common and considerably more expensive.

The classic case: something sits waiting for an approval nobody knows is theirs. Nothing was done incorrectly. It simply stopped, invisibly, and was noticed when a customer asked.

Workflow software exists to make that impossible, by giving every piece of work a state, an owner and an expected duration.

What It Gives You

Location. Anyone can answer where something is without asking around.

Ownership at every step, including the awkward ones. Most stalls happen where responsibility was implicit.

Visible ageing. Work sitting too long in one state is the single most useful operational signal a business can have, and it only exists if states exist.

Exceptions handled deliberately. Every real process has them. Undefined, they get handled by whoever notices, differently each time.

Evidence as a by-product. Who approved what, when. Which matters enormously if you are ever asked to prove it.

Define Before You Build

Start from what actually happens, not what should. Trace one real item end to end and write down every state it passed through, including the informal ones: the email waiting for a reply, the check somebody does mentally, the approval that happens verbally.

Those informal steps are where the process really lives. Leaving them out produces a system nobody recognises, and people route around systems they do not recognise.

Then for each state: who owns it, what has to be true to leave it, and how long it should take. The third question is the one usually skipped, and it is what turns a description into something manageable.

What Moves The Price

Number of distinct states and transitions. A linear five-stage process is simple. Branching, parallel approvals and conditional routing are each a step up.

How many exceptions need first-class handling versus routing to a person.

Whether approvals need to be provable. An audit trail that holds up is a design requirement, not a feature added later.

Integration. A workflow that does not connect to where the work actually happens becomes a second system people update afterwards, which decays immediately.

How many roles and how differently they see the same item.

Where These Projects Go Wrong

Building a parallel system. The work happens in one place and gets recorded in another. It stays accurate for about six weeks. Evidence has to be a by-product of doing the work, not an extra task.

Modelling the ideal process. Written by a manager describing how it should run, while the people doing it use a different route with three workarounds. Wrong from the day it is finished.

No escape hatch. Real work occasionally needs to skip a step. If the system forbids it absolutely, people will work outside it entirely. Allow it, and record it.

Too many required fields. Every mandatory field is a reason to avoid starting the process properly.

Questions To Ask Whoever Builds It

  • Have you spoken to the people who do the work, or only the manager? The workarounds live with the former.
  • What happens to the exceptions?
  • Can somebody skip a step, and is it recorded?
  • How do we see what is stuck? There should be an obvious view.
  • Does this replace where the work happens, or sit alongside it? Alongside decays.
  • What does the audit trail capture, and can an administrator edit it?

A Brief You Can Send Anyone

The process: [each stage, in order, as it really runs]
Who owns each stage: [by role, and by name where it matters]
Where it stalls today: [people know this; ask them]
How long each stage should take: [and what happens when it does not]
The exceptions: [and how they are handled now]
What must be provable later: [approvals, decisions, timings]
What systems the work already lives in: [and whether they have APIs]

How We Build Them

The first deliverable is the written workflow, not code, because it is cheap to change on paper and expensive to change afterwards.

Then states, owners, durations and exceptions in software, integrated with wherever the work already happens so nobody is updating two things.

Where the process is defined and the need is automating parts of it rather than managing it, business automation is the narrower job. The delivered product is a business workflow system.

Get in touch and tell us where work gets stuck.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.