Answer
What AI workflows are useful for a business with five employees?
The ones that cover the hours nobody is available, and the ones that stop a job depending on one person being there.
Capturing enquiries when nobody can answer, sending the routine messages that get forgotten, and turning what people do into records. At this size the constraints are coverage and one person holding everything.
At this size the business has two structural weaknesses and neither is throughput. The first is coverage: there are hours, and sometimes days, when the person who could handle something is unavailable, and what arrives then is lost or delayed. The second is concentration: each function is held by one person, so their absence, distraction or departure removes a capability entirely.
That makes capture the first workflow. Every enquiry, whatever channel it arrived through, into one place with the details recorded. This addresses both weaknesses at once — nothing is lost during the gaps, and what arrived is visible to whoever is available rather than to whoever received it. It is also the prerequisite for measuring anything, and businesses of this size usually cannot say how many enquiries they received last month.
Response during the gaps is the second. An acknowledgement that takes the details and states when a person will follow up keeps an enquiry alive that would otherwise go to a competitor. The commitment has to be one the business meets on its worst day, and the value comes from the alternative being silence rather than from the reply being good.
Routine outbound is the third and is the cheapest thing on the list. Appointment confirmations, payment reminders, follow-ups on quotes, the annual service prompt. These fail in small businesses not because they are hard but because they depend on someone remembering during a busy week, and the whole value is that a schedule does not have a busy week.
Record-keeping is the fourth and is the one that addresses concentration directly. Notes from a job, what was agreed on a call, what a customer asked for: turning these into written records rather than leaving them in one person's memory is what makes the business able to operate when that person is not there. Making the capture cheap — a voice note that becomes a record — is what makes it actually happen.
What is not worth building at this size is anything requiring ongoing attention. A portfolio of automations needs someone to watch it and there is nobody, so the arrangement should be a small number of things that either work or fail visibly. The right count is two or three, chosen deliberately, and the discipline of stopping there is worth more than any individual addition.
With five people nothing fails because of capacity; it fails because the one person who knew was on a job.
Siddharth Sharma, Context Theory
Related questions
Is a business this size too small to bother?
The opposite in one specific respect: the coverage gaps are proportionally largest here, so the value of something answering when nobody can is highest. What is genuinely too small is a programme — a systematic adoption effort — because there is nobody to run it. Two workflows and no programme is the shape that fits.
Should a business this size hire someone to set it up?
For a specific, bounded piece of work with the knowledge left behind, that can be sensible. For an ongoing arrangement, be careful: at this size an external dependency for something the business runs daily is a fragility, and the arrangement should end with someone inside able to operate what was built.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
| Leads cold past 5 minutes | 93% | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · 1.25M inbound leads across 2,241 US firms · verified
2026 speed-to-lead benchmark · derived: 100% − 7% responding within five minutes · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Workflow | At five people the binding constraints are coverage during hours when the relevant person is unavailable and concentration of each function in one individual, rather than total capacity. | Identifying which functions in the business would stop entirely if a single named person were away for a week. |
| Response | Unified capture addresses both weaknesses simultaneously, because nothing is lost during unavailable periods and what arrived becomes visible to whoever is free rather than to whoever received it. | Asking how many enquiries arrived last month and through which channels. |
| Buying behaviour | Routine outbound messages fail in small businesses because they depend on someone remembering during a busy week, so the value of scheduling them comes from a schedule not having busy weeks rather than from any capability. | Counting how many due follow-ups, reminders or prompts were missed in the last busy period. |
| Constraint | A portfolio of automations requires ongoing observation that a business of this size does not have, so the workable arrangement is a small deliberately chosen number that either work or fail visibly. | Naming who would notice each proposed automation stopping. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one