Most solo consultants make the same mistake when they decide to scale: they hire someone before they document anything. Then they spend three months training a person to do work the consultant has never written down.
The path that actually works is operations first, hire second. By the time you bring on an associate or a delivery partner, the systems should already exist for them to plug into.
The Five Systems That Have to Exist First
1. The Pipeline
A real pipeline that anyone could open and read. Stages defined, criteria for moving between them written down, and a forecast model that produces a number anyone can interpret. Build this before you hire someone to run it.
2. The Follow-Up Cadences
Every cadence — proposal follow-up, post-engagement nurture, review request — written, templated, and automated. The first hire should not be writing emails from scratch. They should be picking from a library you have already built.
3. The Onboarding Workflow
A documented sequence of every touch from contract signature through week one. Welcome packet, kickoff agenda template, first-deliverable structure. New people should be able to onboard a client without your involvement.
4. The Delivery Templates
If your engagements have artifacts — strategy documents, reports, frameworks — those need to be templates, not blank pages. The associate should be filling in templates, not inventing structure on every project.
5. The Reputation System
Reviews, referrals, and case studies on automatic triggers tied to engagement milestones. Without this, growth is permanently throttled by your own willingness to ask.
What the First Hire Should Do
Most consultants hire a junior delivery person first. That is usually backwards. The first hire should run the operations of the practice — pipeline hygiene, follow-up cadences, client communications, scheduling. This frees you to do the work that only you can do: discovery calls, senior-level delivery, relationship management.
If the first hire is a delivery person, you have created a second consultant who needs the same operational scaffolding you do. If the first hire is operations, you have created leverage.
“Boutique firms that grow predictably almost always built the operations stack before the second person walked in the door. The ones that struggle did the opposite.”
The Compounding Effect
Once the five systems exist and one operations person is running them, growth becomes a math problem instead of a willpower problem. Add a delivery hire when the pipeline justifies it. Add another when the second is full. Each addition is incremental — not a rebuild of the entire firm.
Key takeaways
- 01Build the operations stack before the first hire, not after
- 02The five systems are pipeline, cadences, onboarding, delivery templates, and reputation
- 03Each system makes the next one easier — order matters
- 04The first hire should run operations, not deliver client work
- 05With the stack in place, growth becomes a math problem instead of a willpower problem