The most common story in law firm consulting goes like this: a firm is growing, the founder is overwhelmed, so they hire someone. The new hire is smart and capable. Three months later, the new hire is either underperforming or has already left. The founder concludes that finding good people is impossible.
The real problem is never the person. The real problem is that the firm had no infrastructure to absorb a new hire — no SOPs, no onboarding program, no defined role, no clear expectations. The hire was set up to fail before their first day.
This is the most expensive mistake in law, and it is almost universal.
Why firms hire before building systems
The logic is understandable: the founder is overwhelmed, the work is piling up, the obvious solution is another person. Hiring feels like a solution because it's concrete and immediate. Building systems feels abstract and slow.
But consider what actually happens when you hire into a firm without infrastructure. The new hire spends their first 30–60 days trying to figure out what they're supposed to be doing. They ask questions the founder doesn't have time to answer. They develop their own processes — which may or may not match how the firm actually needs to operate. The founder spends more time managing the new hire than they would have spent doing the work themselves.
At the 90-day mark, one of two things happens: the hire leaves, or they stay and become another source of founder dependency rather than a source of founder leverage.
The data point that matters: It costs 3–4 times an employee's annual salary to recruit, hire, onboard, and replace them. For a $50,000 role, that's $150,000–$200,000 in total cost if the hire fails. Most of those failures are infrastructure failures, not talent failures.
What "structure before scale" actually means
Structure before scale doesn't mean you can't grow until your systems are perfect. It means you build the minimum viable infrastructure for a new hire to succeed before you bring them on — not after.
For most law firms, that minimum viable infrastructure is three things:
A defined role with defined outputs. Not a job description with a list of duties — a role definition that specifies what this person will produce, how that output will be measured, and what success looks like at 30, 60, and 90 days. Without this, neither the new hire nor the founder has a shared understanding of what the role is for.
SOPs for the recurring workflows they'll own. If you're hiring an intake specialist, they need a documented intake process before day one. If you're hiring a billing coordinator, they need a documented billing workflow. These don't need to be exhaustive — they need to be complete enough that a new person can execute them without asking you every other question.
A configured technology environment. If your Clio isn't set up and your Lawmatics isn't running, a new intake specialist can't do their job effectively regardless of how good they are. The tech stack needs to be functional before the person starts — not configured by the new hire during their first weeks on the job.
The 48-hour test
Before you hire your next person, ask yourself this question: if I were completely unavailable for 48 hours right now, what would happen to my firm?
If the honest answer is "things would stop" or "things would go wrong" — you don't have a hiring problem. You have an infrastructure problem. Hiring another person into that environment scales the dependency, not the capacity.
The 48-hour test reveals the structural gap. If your intake process requires you to personally follow up with every new lead, a new intake specialist can't help you — because the process doesn't exist independently of you yet. If your billing process requires you to personally review and approve every invoice, a billing coordinator can't help you — because the process isn't documented and delegated.
The work that needs to happen before you hire is making those processes exist independently of you. Document them. Configure the systems that support them. Then hire someone to run them.
The sequence that actually works
At Bay Legal, we followed a specific sequence for every growth stage. It's the same sequence XPRTS recommends for clients:
First: Identify the highest-leverage role — the hire that would create the most capacity for the highest-value work. Usually this is an intake specialist (freeing up attorney time) or a billing coordinator (recovering leaking revenue).
Second: Document the workflows that role will own. Not exhaustively — but well enough that someone can execute them with minimal guidance.
Third: Configure the technology that supports those workflows. If intake is the role, Lawmatics needs to be running. If billing is the role, Clio billing needs to be fully configured.
Fourth: Define the success metrics for the role. What does a good intake specialist produce? What are the KPIs? How will you know at 90 days whether this hire is working?
Fifth: Build a 30/60/90-day onboarding program that ramps the new hire into those workflows systematically rather than all at once.
Then: Hire.
This sequence adds 2–4 weeks to your timeline. It eliminates the most common cause of hire failure and dramatically increases the likelihood that the person you bring on becomes a genuine source of leverage rather than another management burden.
What this means for remote staff
The infrastructure-first principle is even more critical for remote hires than for in-office staff. A remote intake specialist operating without SOPs, without a configured Lawmatics pipeline, and without a clear definition of their role will fail — not because they're remote, but because the foundation isn't there.
This is why XPRTS builds the infrastructure before deploying staff. We configure Clio. We build the Lawmatics pipeline. We write the SOPs. We define the role and the onboarding program. Then we place a trained person into that infrastructure — and the hire succeeds because the foundation supports them.
The XPRTS staff who train inside Bay Legal's live environment succeed for the same reason. They're not dropped into a chaotic firm and told to figure it out. They're trained inside a working system and then deployed into a similar working system at a client firm.
Ready to Implement This at Your Firm?
Request a free Strategy Review. We'll identify your primary bottleneck and deliver a specific written recommendation within 48 hours.
Request a Free Strategy Review →