Boutique planning firms love the phrase “everyone does everything.” For a while it sounds noble: collaborative, flexible, sleeves-rolled-up. Then the workload changes and the phrase starts sounding expensive.
You can usually see the shift in the hiring language. A firm wins more work, opens a project manager role, and asks for strong writing, editing, research, analysis, CEQA familiarity, entitlement management, policy fluency, and the ability to juggle multiple deadlines in a small team where everyone wears many hats. That is not just a hiring preference. It is an operating model announcing its limits.
The real issue is not that boutique firms need versatile people. They do. The issue is that they often ask the same people to do two very different kinds of work, then wonder why capacity disappears.
The Two Kinds Of Work
Planning deliverables usually contain a blend of expertise work and assembly work.
Expertise work is the reason clients hire the firm in the first place:
- entitlement strategy
- policy analysis
- community and stakeholder navigation
- environmental synthesis
- judgment about unusual sites, jurisdictions, and tradeoffs
Assembly work is everything that keeps those deliverables moving and coherent:
- formatting and template population
- precedent lookup
- section assembly
- review routing
- version management
- checklist completion
Both kinds of work matter. Treating them as interchangeable is where the trouble starts.
When a firm hires generalists to do all of it ad hoc, the repetitive work keeps masquerading as expert work. Senior people stay buried in review and reconstruction. Junior people stay dependent on whoever happens to remember the last version. Capacity goes up a little with each hire and then flattens again.
Where The Ceiling Shows Up
The signs are usually familiar.
The same few people become bottlenecks because only they know how a certain section should sound or where a certain precedent lives.
Quality drifts based on who is free that week.
Training never really ends because the work is always being re-explained in local context instead of supported by reusable structure.
And the firm starts confusing exhaustion with craftsmanship. (Those are not the same thing.)
This is why the “everyone does everything” model works beautifully at five people and starts straining much sooner than anyone expects. The model has a ceiling because ad hoc assembly has a ceiling.
What Better Infrastructure Looks Like
The firms that get through this phase do not eliminate judgment. They get much more deliberate about where judgment is actually needed.
They start building support around the repeatable parts:
- reusable CEQA language organized by issue and project type
- precedent libraries that are searchable by jurisdiction and scale
- standard section structures for reports and memos
- review workflows that route drafts with context instead of dumping them cold
That is the move. Not replacing the planners. Not flattening the work into mush. Just getting the repetitive assembly work out of everyone’s short-term memory and into something the firm can operate on purpose.
Finding The First Workflow
You do not need to systematize the whole firm at once. That is how these efforts die in committee.
Start with one deliverable type that is both high-frequency and pattern-heavy. In planning firms, that is often a CEQA section, an entitlement memo, a staff report, an environmental summary, or a recurring deck for public meetings.
The question I would ask is simple: what do you recreate from scratch every month even though the firm has already done some version of it twenty times?
That is usually the first candidate.
Take CEQA sections. In many firms an associate still has to hunt through old files, pull precedent language manually, adapt it, reformat it, and send it out for review. That is not all judgment. A good chunk of it is retrieval, assembly, and consistency work.
A stronger workflow would surface the relevant precedent automatically, preserve the surrounding structure, and show the reviewer what changed from the prior version. The planner still makes the project-specific calls. The system simply stops making them rebuild the scaffolding each time.
Boutique Does Not Have To Mean Bespoke Chaos
I understand why firms cling to the identity of being highly tailored, highly hands-on, highly flexible. Those are real strengths. But flexibility gets expensive when the firm uses it as an excuse to keep every repeated task handcrafted forever.
The boutique firms that scale well usually do one thing better than everyone else: they protect expert attention. They do not spend it on formatting drift, precedent archaeology, or version confusion if they can possibly help it.
That is the real shift. Not “becoming automated.” Not flattening the work. Just deciding that expertise should go toward the parts of the job that actually require expertise.
If the firm keeps winning work, that decision stops being optional.
I work with boutique planning firms to identify and build their first deliverable assembly workflows. The process starts with a First AI Workflow Audit that maps your current production patterns and identifies the highest-value opportunities for systematization. Get in touch if you’re navigating the growth trap and want to talk through your specific situation.