Why services firms break
at predictable sizes.
Growth pain isn't random. Services firms break at similar sizes because the same mechanisms fail at the same thresholds. Knowing the thresholds lets you pre-empt — instead of reacting when the crisis hits.
20 people · status breaks
At ten people, partners know every case. At twenty, they don't. At twenty-five, they know they don't, and start asking for status three times a day. Status automation is the first cure.
40 people · handoffs break
At forty, you need standardised handoffs because tribal knowledge runs out. The people who "just knew" what to do next have been joined by people who don't. Handoff templates become essential.
80 people · systems break
At eighty, your email-plus-Excel approach can't scale. Some cases get lost. Some deadlines slip. Proper systems of record become necessary — but chose cheap and portable, not enterprise-grade.
The crisis isn't the headcount. It's the moment the old mechanism stops working and you haven't yet built the new one.
Three disciplines to master.
Every services firm of 20+ needs three disciplines, in this order: status, ownership, handoffs. Getting them right doesn't require software — but software helps enforce them at scale.
Status
Every case has a clear state, visible to everyone who needs it, updated automatically where possible. "I'll check and get back to you" should become rare, not the default.
Ownership
Every case has exactly one owner at each stage. When the owner changes, the handoff is explicit, recorded, and acknowledged. No orphaned cases; no "I thought you had it" moments.
Handoffs
Handoffs are templated: here's what the next owner needs (status, pending items, context, deadline). The sender fills the template; the receiver acknowledges. Friction drops; trust rises.
A baseline partners accept.
Before you invest in workflow automation, measure the current state. Not precisely — roughly. Three numbers beat an expensive audit every time.
These three are enough. Re-measure after automation; track the delta. Partners trust numbers they understand and can verify. A 40-page audit produces less trust than three numbers on a napkin.
- Median response time (first substantive reply, not auto-ack). Measure over 2 weeks.
- Handoffs per case (how many times does a case change owner from start to finish?). Sample 20 cases.
- Partner hours/week on operational admin (status calls, handoff clarifications, routine check-ins). Estimate.
What to automate first.
Automate in the order of leverage. The ROI varies wildly — some automations pay off in two weeks, others never. Here's the order that works consistently across services firms we've analysed:
1. Status visibility
A shared board that auto-updates from email, CRM, DMS. Near-zero friction to view. Usually ready in 4–6 weeks.
2. Intake routing
Automatic classification and owner assignment for new cases. Eliminates "who should take this?" meetings. 4–6 weeks.
3. Handoff templates
Structured handoffs via forms or Teams/Slack bot. Enforces discipline without bureaucracy. 2–3 weeks.
4. Follow-up automation
Automatic nudges for pending items, escalation on SLA breach. 4–6 weeks. Partners love this one most.
Patterns across law, tax, audit, consulting.
The specific systems differ — DATEV in tax, RA-MICRO in law, proprietary PSA in consulting — but the automation patterns are strikingly similar. Here's what we've seen working across industries:
Law firms
Intake + handoff templates + beA integration. Typical saving: 30 % of partner operational time in 3 months.
Tax advisory
Client onboarding + document collection + DATEV integration. Typical saving: 40 % of admin time.
Audit firms
Engagement tracking + document workflows + review status. Typical saving: 25 % of manager operational time.
Consulting
Project status + resource routing + client updates. Typical saving: 35 % of operational admin.