A solo fractional practice can grow past one operator without becoming an agency. The trick is subcontracting specific capabilities to trusted specialists without building fixed-cost headcount. This playbook extends the fractional practice hub into the staffing layer: how to pick the capabilities, how to structure the contracts, how to protect the client relationship, and how the margin math actually works.
Why the subcontractor path exists
A solo practice hits a capacity ceiling around four engagements. You can push it higher by working more hours, but the quality drops and the burnout clock starts. At that point, most operators make one of two moves. Hire staff and become an agency. Or cap the practice at solo and accept the revenue ceiling.
There is a third path. Subcontract the specific capabilities that show up repeatedly in your sprints, keep the client relationship, and pay the subcontractor well enough that they treat your engagements as priority work. The capacity ceiling moves from "hours in your calendar" to "hours in your calendar plus trusted specialists you can dispatch." The practice stays solo at the ownership layer while scaling at the delivery layer.
The reason this path is underused is that most operators conflate it with becoming an agency. It isn't. An agency has fixed-cost staff, a margin that shrinks when utilization drops, and a layer of management between the buyer and the person doing the work. A solo practice with subcontractors has variable cost, no idle-time risk, and the operator is still the single point of contact on every engagement.
The subcontractor path is one of the distinct answers to the portfolio-scaling question discussed across the engagement shapes article. Rather than adding fifth and sixth simultaneous engagements (which break the context-switch math), the operator increases output per engagement by dispatching specific capabilities.
The capabilities worth subcontracting
Not every capability should be subcontracted. The test is: does this capability appear in more than half of my sprints, and is it distinct enough that a specialist does it faster and better than I do?
For my practice, three capabilities pass that test. The first is deep Shopify theme Liquid work. I can write Liquid, but a specialist who writes it every day of the week ships the same feature in a third of the time at higher quality. The second is creative production at volume. Motion graphics, frame-by-frame asset generation, production design work. A specialist with the right toolchain can turn around 40 assets in the time it takes me to build the art direction for 10. The third is complex data infrastructure work. BigQuery dashboard builds with dbt models underneath. I've built them; a specialist builds them cleaner.
What I do not subcontract: anything strategic, anything that touches the client relationship, and anything where the client is paying specifically for my judgment. That preserves the thing the buyer hired. Every hour of my time that the buyer sees is spent on the work the buyer valued enough to contract for. The subcontractor's hours are invisible to the buyer because they are compressed into output rather than exposed as a team member.
The single-point-of-contact rule
The most important rule in the subcontractor playbook is that the buyer never talks to the subcontractor. Ever. Not in a kickoff meeting, not in a status email, not in a slack channel. The buyer's entire experience of the engagement is with the operator who closed the sale.
This rule is the structural difference between a solo practice with subcontractors and an agency. In an agency, the buyer sees the team. In a solo practice, the buyer sees one operator. The work is delivered by the operator even when parts of it were produced by specialists.
The rule is strict. The subcontractor does not know the client's name if they don't need to. The subcontractor's deliverables come to the operator, who reviews them, edits them, and hands them to the client as the operator's own work. The subcontractor invoices the operator, not the client. The operator is on the hook for quality, timeline, and any conversations about either.
This is enforceable because the subcontractor is being paid to produce work, not to build a client relationship. A good subcontractor prefers the setup because it removes account-management overhead from their life. A bad subcontractor resents it and will eventually try to bypass. That's a disqualification, not a negotiation.
The contract structure
Every subcontractor relationship needs three documents. A master services agreement, a non-circumvention clause, and a per-engagement statement of work.
The MSA covers the basics: ownership of work product (transfers to the operator upon payment), confidentiality, indemnification boundaries, payment terms, and the non-circumvention language. The non-circumvention clause specifies that the subcontractor will not solicit the operator's clients during the engagement or for a defined period after (usually 12 to 24 months). If the subcontractor does engage with the client independently, there are liquidated damages. This clause exists because the subcontractor will see the client's work and might be tempted to pitch them directly. The clause makes that a structural mistake for the subcontractor.
The SOW is per-engagement. It describes what the subcontractor will deliver, when, for how much. Fixed price, not hourly. Hourly subcontracting collapses the margin structure that makes the practice work.
The margin math
The math is the part that determines whether subcontracting is sustainable or a way to lose money quietly.
The operator's billing rate for work the subcontractor will produce has to be high enough to cover the subcontractor's fee plus a margin that covers the operator's review, client-management, and risk load. The numbers I run look like this. The subcontractor is paid a market rate for their specialty, usually between $80 and $180 per hour or a fixed project price that maps to that band. The operator bills the client at a rate that covers the subcontractor plus a 40% to 60% margin. That margin pays for the operator's time reviewing the work, the risk of being on the hook if the subcontractor's work falls short, and the overhead of managing the relationship.
If the margin is thinner than 40%, the operator is effectively working for free on the subcontractor's hours. The first time the subcontractor's work needs significant rework, the engagement goes negative. A 40% minimum margin gives enough cushion to absorb one round of rework without going underwater.
A productized sprint makes this math cleaner. Because the sprint has a fixed price and a fixed scope, the subcontractor's piece can be priced at a fixed amount. The operator knows exactly what the subcontractor costs on each sprint, and the pricing has been set to cover it with margin. No hourly estimation, no variable cost surprises.
“A margin thinner than 40% means the operator is working for free on the subcontractor's hours.
”
The vetting process
Finding subcontractors who can deliver inside a solo practice's structure takes work. The pool of talented specialists is large. The pool of specialists who can deliver inside someone else's process, ship on time without micromanagement, and respect the single-point-of-contact rule is much smaller.
The vetting process I run has three steps. First, a paid trial on a small scoped deliverable. Usually $800 to $2,000, with a clear SOW and a 2-week timeline. The subcontractor produces the work, I review it, and I evaluate not just the quality but the process. Did they communicate on the cadence we agreed? Did they surface risks early? Did the final deliverable match the scope? That first engagement screens out about 70% of otherwise-talented specialists.
Second, a medium-sized engagement inside a real client sprint, where the work matters but the blast radius is bounded. This tests whether they can hold scope when it changes slightly under pressure and whether their review process produces work that is ready to hand to a client.
Third, if those go well, a regular partnership with a standing rate and priority access. The subcontractor knows they can count on a baseline of work from me; I know they'll prioritize my engagements when I need turnaround.
This process takes three to six months from first contact to reliable partnership. That feels slow, but the cost of a bad subcontractor on a live client engagement is higher than the cost of slow vetting. Skipping the trial step is the single most common way this setup breaks.
What the client never sees
From the client's perspective, the engagement has one person on it. The operator. Every status update comes from the operator. Every deliverable is signed off by the operator. Every question goes to the operator.
Behind that surface, the operator is dispatching work to the right specialist, reviewing their output, editing as needed, and integrating it with the work the operator produced directly. The client sees a unified deliverable on the schedule. They do not see the architecture underneath.
This is not deception. It is a structural choice about how the practice is shaped. The client hired the operator. The operator is delivering what the client hired for. The mechanics of how the operator assembles the work are not relevant to the client's outcome.
Some buyers ask directly whether the operator uses specialists. The honest answer is yes, and the honest explanation is that specialists make the work better. The buyer is buying the operator's judgment, strategy, and accountability, all of which stay with the operator.
When the subcontractor path breaks
Three failure modes show up in practice.
The first is when the operator cannot bring themselves to review the subcontractor's work thoroughly enough. The deliverable goes out with flaws the operator would have caught if they had produced it themselves. The client catches the flaw, the credibility is damaged, and the engagement suffers. Fix: review time for subcontracted work has to be scheduled at the same density as the operator's own work, not treated as a faster version of production.
The second is when the operator starts sending work that should have stayed in-house. Strategic work, client-facing deliverables, anything with nuance. The subcontractor produces something technically correct and spiritually wrong. The client feels it. Fix: discipline about what goes outside and what stays inside. Strategic work stays in.
The third is when the subcontractor takes on more client work than they can handle and the operator's engagements slip on their cadence. Fix: have two or three vetted subcontractors per capability, so no single subcontractor's capacity is a single point of failure.
How this connects to the practice OS
The subcontractor layer is infrastructure. It belongs in the practice operating system alongside the intake templates, SOW skeletons, and credential hygiene systems. A vetted subcontractor is an expensive asset to build; losing track of which ones are available and which engagements they're best suited for is organizational malpractice.
The subcontractor playbook also affects engagement shape selection. Sprints subcontract cleanly because the scope is fixed. Advisory retainers don't subcontract because the buyer is paying for the operator's judgment directly. The four engagement shapes dictate which subcontracting moves are available.
Frequently asked questions
How do I find subcontractors in the first place?
Referrals from other operators, direct outreach to specialists whose work you admire, and conversion from freelancers who have delivered adjacent work to your past clients. Upwork and Toptal exist but usually produce worse fits than referrals. The vetting bar matters more than the sourcing channel.
What if a subcontractor wants to be a full partner instead?
That's a different conversation. If the subcontractor's contribution genuinely warrants partnership, formalize it as an equity arrangement with a legal structure, not as a fluid "we're partners now" vibe. Most partnership conversations with subcontractors are the subcontractor asking for a bigger share without the risk of partnership. Decline those.
Can I subcontract to another fractional operator?
Yes, but be careful about overlap in your client bases. Two fractional operators subcontracting to each other in the same vertical is functionally a small agency with extra steps. Works when the capability sets are genuinely complementary. Breaks when they overlap.
How much work do I need to subcontract to justify the overhead?
The breakeven is around 20-30 hours/month of subcontracted work. Below that, the vetting and relationship-management overhead eats the margin. Above that, the math works. If you're only subcontracting occasionally, keep it to trusted one-off specialists rather than trying to build a subcontractor bench.
What about international subcontractors?
The math works better internationally because the rate arbitrage is larger, but the communication overhead can be higher depending on timezone and language fit. For my practice, the subcontractors who have worked out have been a mix of US-based specialists for strategic-adjacent work and international specialists for production-heavy capabilities.
Sources and specifics
- The three subcontracted capabilities (Liquid, creative production, data infrastructure) are the ones I actually subcontract in my practice.
- The 40% margin floor is from running the math across multiple engagements. Below that, a single rework consumes the margin.
- The three-step vetting process (paid trial, bounded real engagement, standing partnership) is the current protocol. Each specialist who became a standing partner went through all three steps.
- The non-circumvention clause language came from a fractional-ops-adjacent MSA template I commissioned from a solo-practice attorney in 2024.
- The availability page shows current engagement load; the products page shows which sprints have been productized and therefore subcontract cleanly.