The five workflows most firms leak time on

Where does enquiry intake leak time?

Intake leaks in the gap between an enquiry arriving and anyone deciding what to do with it. The enquiry itself is usually fine. What costs you is that it lands in a personal inbox, waits for the one person who can assess it, gets replied to from scratch, and is then either entered into the CRM or not.

Three losses follow. Response time, because a prospect who waits three days has usually already spoken to someone else. Consistency, because the quality of your first reply depends on who happened to be free. And data, because enquiries that never reach a system cannot be counted or followed up. Most firms cannot say how many enquiries they received last quarter.

What good looks like:

• One front door. A form, so information arrives structured rather than as prose, with the three or four fields you actually need to assess fit.
• A record created automatically in the CRM or matter system, every time, with the source captured.
• Routing by rule: the enquiry goes to the right person based on service type, location or value, without anyone triaging it.
• A drafted reply prepared from the enquiry's own detail, sitting in that person's queue for approval and a one-line edit.
• An acknowledgement to the sender within minutes, even when the considered reply is a day away.
• An alert if nothing has been sent inside your own stated response standard.

Where does quote to invoice leak time?

This one leaks after the win, which is why it is so often invisible. The quote goes out, the client accepts by email, and the work starts. The invoice is raised whenever someone remembers, which in a busy firm is weeks after delivery, and unpaid invoices are chased by whoever gets around to opening the aged receivables.

The cost here is cash rather than hours, and it compounds quietly. Every week between delivery and invoice is a week of your money funding your client's operations. Every unchased invoice is a collection conversation that gets harder the longer it waits.

What good looks like:

• Acceptance is an event the system can see, not a sentence in an email thread. An accept button, a signature tool, or a status someone sets deliberately.
• The accepted quote creates the job and the draft invoice in the accounting system in one step, same line items, no retyping.
• Invoices go out on a schedule tied to delivery, not to memory.
• Reminders are scheduled the moment the invoice is sent, with a defined ladder and defined stop conditions.
• Payment marks the sequence complete automatically, so nobody chases money that has already arrived.

Why do review requests never get sent?

Because asking for a review is the last task in a job that is already finished, and it competes with the first task of the next one. It is nobody's priority, it feels like asking a favour, and nothing prompts it, so it happens when someone remembers in a slow week.

The result is that firms with genuinely happy clients carry thin, old public reputations, skewed toward whoever was most motivated to write. For professional services, where clients search before they call, that is a marketing cost paid over and over.

What good looks like:

• The trigger is a real event in a system you already use: matter closed, job marked complete, final invoice paid.
• A short delay, sensible for your work, so the request lands while the result is fresh but after the dust has settled.
• The request comes from the person the client dealt with, in their voice, asking for one specific thing.
• A held-back list for clients you should not ask, controlled by whoever ran the matter.
• Unhappy responses route to the principal first, before anyone else replies. This is the part that matters most and the part most often skipped.
• No incentives, and nothing that reads as gaming the platform. Check your professional body's rules on testimonials and advertising first, because some professions restrict what you may solicit and publish.

Why is the owner's report always late?

Because it is assembly work disguised as management work. The numbers live in four systems, the commentary lives in the principal's head, and building it means opening every tab on a Friday afternoon. So it slips, and slips again, and after two months of not seeing the numbers the firm is being run on feel.

The leak is not the hour it takes. It is that decisions get made without the report existing, and that the version which finally appears cannot be compared to last month's.

What good looks like:

• A fixed, short definition of what the report contains. Six to ten numbers that would change a decision, not a dashboard of everything available.
• Automatic collection from the source systems on a schedule, failing loudly if a source is unavailable rather than reporting a zero.
• The same layout every period, so movement is visible at a glance.
• A drafted commentary stating what moved and by how much, leaving interpretation to the reader.
• Delivery whether or not anyone asks for it, at a time when the reader can act on it.

What is actually wrong with the shared inbox?

The shared inbox leaks because reading a message and deciding who owns it is real work that produces nothing. In most firms it is done several times over, by several people, on the same message. Everyone scans everything, and most of it belongs to somebody else.

The second problem is accountability. When an inbox is everyone's, a message nobody claims is nobody's fault, and it is usually the important one that goes quiet.

What good looks like:

• Classification on arrival by intent: new enquiry, existing client, supplier, invoice, noise.
• Routing to a named owner, with that ownership visible to the whole firm.
• A drafted reply for the categories that are genuinely repetitive, held for approval.
• A clear rule about what the automation may not touch, and a weekly review of its decisions for the first month.

Which one should you fix first?

Fix the one costing you the most, and be honest about the currency. Hours, cash and lost work are different problems, and the ranking changes depending on which is hurting.

1. If enquiries go cold or you cannot say how many you received, start with intake. It is the only one here that grows revenue rather than saving cost.
2. If invoices go out late or the aged receivables list has surprises in it, start with quote to invoice. Cash timing is the fastest measurable return of the five.
3. If the principal's evenings are the constraint, start with whichever workflow appears most often in a fortnight of interruption logging. Usually triage or reporting.
4. If your public reputation does not match the quality of your work, start with reviews. Smallest build of the five, and the effect accumulates.
5. If you cannot decide, build the one whose steps you can already describe in a paragraph. Automating an undefined process just produces a faster mess.

Build one, run it for a month, and read what it did before starting the next. Each of these teaches you something about the next, and the version you would have built in month one is rarely the one you want by month two.

What to do next

Pick a single workflow and write down its current steps exactly as they happen, including the parts that only happen when someone remembers. That document is both the specification and the diagnosis, and it usually exposes two or three steps you can delete outright before any tool gets involved. If you want the ranking pressure-tested against your own numbers, that is what a Shift Flow Map does in ninety minutes.