A business workflow is a defined series of steps that turns a trigger into a finished piece of work. Every service business runs many of them, from answering a new inquiry to closing the books at month end, often without a single one written down.
This guide explains what a workflow is, how to find yours and how to map one before you change it. It ends with how to decide which steps to hand to workflow automation: software that moves routine work between your tools by itself, without anyone pushing it along.
What a workflow is, in plain words
Every workflow has the same parts. The trigger is whatever sets it off: a phone call, a web form, a signed contract, a new month starting. The steps follow in order, and each one belongs to someone, even if nobody ever said so. Some steps are decision points, where a rule picks the path: a brand-new client gets the welcome pack, and a returning one does not. And it ends in a known place, with the piece of work done.
Take a routine every service business has: billing a client once a job is finished.
- Trigger: the job is signed off as done.
- The invoice is drawn up from the agreed price or hours.
- Someone checks it, then emails it to the client.
- Decision point: once the due date passes without payment, a polite reminder goes out.
- When payment arrives, it is recorded in the books.
- Finished: the money is in and the books agree.
Written out like that, it looks simple. In practice, step four often relies on a person's memory, and step five means typing the same figures in a second time. Those are the places where a routine quietly loses time and money.
Finding the workflows in your own business
You can probably name a few routines straight away. The rest hide in plain sight. Two angles bring them out: your departments, and what is typical of your industry.
By department
Go department by department and ask what happens, step by step, when something arrives. In marketing and sales, it starts with an inquiry: who replies, where the contact is recorded, when the follow-up goes out. In customer experience, it is a new client starting, or a question coming in. In finance, it is invoices, expenses and checking your books against the bank. Operations holds the handoffs between people, the approvals and the deadlines. IT holds the software accounts and access for anyone joining or leaving. People and HR holds hiring and onboarding new staff, and workplace productivity holds meetings, scheduling and the reports you rebuild every week.
By industry
Each industry has its own version of these routines. A brokerage or mortgage office collects documents and watches deal deadlines. A clinic sends intake forms and appointment reminders. A law firm opens new files and sends engagement letters, the letter that sets out the terms of the work. A recruitment agency books interviews and turns approved timesheets into invoices. An online store confirms orders and handles returns. A property manager logs repair requests and sends rent reminders. Each page describes that field's routines in the language it actually uses.
The tell-tale signs
Some routines only show themselves when they fail. Listen for these:
- names and figures entered twice, in two different systems;
- a step that happens only if someone remembers it;
- clients calling to ask how their file is coming along;
- a task nobody else can cover when its usual owner is away;
- requests that sit unanswered until somebody spots them.
Each one points to a workflow with a weak spot.
Map the routine before you change it
Before you change a workflow, or automate it, sketch the current version, warts and all. One page is enough. Write the trigger at the top. Below it, list the steps as they happen, one line each, with a name beside every line. Note each decision point and the rule behind it. Then circle every step where someone must use their judgment, because those are the ones you will protect.
Be honest about the workarounds. The step someone skips on busy days, or the spreadsheet only one person updates, is exactly what a new system would get wrong if nobody wrote it down.
For a fuller method, read our five-step mapping framework. Some teams build a prototype instead: a quick, rough version made to learn from, which shows where the gaps are. To decide which suits your routine, read when to document first and when to prototype.
What to automate, and what to keep with a person
Not every routine belongs with software. The best candidates share four traits:
- Repetitive. Each run looks like the last, with few surprises.
- Rule-based. You could write its rules down for a new hire, and they would get it right.
- Frequent. It comes round often enough that the minutes add up across a month.
- Costly to miss. A forgotten step loses a client, delays a payment or creates rework.
Appointment reminders, booking confirmations, requests for missing paperwork, progress updates sent to clients and re-typing the same data into a second system tend to pass all four.
Other steps belong with people, however often they happen. Anything needing judgment, such as a price, a piece of advice or the next move on a client's file. Anything that commits money or a legal promise, or is hard to undo. Any message where tone matters, such as bad news or a reply to a complaint. A well-built business workflow keeps those steps and prepares them: the information is gathered, the task lands with whoever owns it, and nothing moves forward until they approve.
Three routes to automation
Once you know which routine to start with, there are three broad routes. Much of the software involved now runs in the cloud, meaning on the internet instead of a computer in your office. Our explainer on cloud-based workflow automation covers what that means in practice.
Do it yourself
Many apps you subscribe to already have simple automations built in, including your CRM (the system that holds your client records and contact history), booking system and accounting software. There are also apps whose whole job is linking other apps together. This route suits a simple, low-risk routine and a colleague who enjoys the setup. The catch is upkeep. When an app changes, a home-made automation can stop working without telling anyone, which is why watching for silent failures matters. Our guide to running a more automatic business shows where to begin.
BPM software
BPM (business process management) is software for drawing your processes, running them and tracking each case until it is done. It suits larger teams where many people touch the same process. It also needs someone in-house to own the system: set it up, train staff and maintain it as things change. When the owner is also the office manager, that ownership is usually the hard part. We compare the two approaches in BPM software versus done-for-you automation.
Done for you
A specialist firm designs the workflow with you, builds it within your existing software, tests it and documents it in writing. You agree the rules, and which steps wait for your approval; the firm does the building, and can look after it afterwards. If your hours are worth more with clients than with software, take this route. Vertex offers exactly this. If you are weighing up outside help, read what working with an automation firm looks like.
Your next step
If you already know which routine costs you most, start there. If you are not sure, ask for a free 30-minute diagnostic consultation. The form takes a few details about your company and the work you want to automate. Expect a short call from our AI assistant, usually around ten minutes later during business hours, to learn about your company. If you would like to go further, we then pick a time for the consultation together.
In the consultation, we walk through one business workflow with you, step by step, and mark which steps software could carry and which should stay human. For the full range of what we automate, by department and industry, visit our services page.