The back bench versus the single hire: a cost and continuity comparison.
The comparison founders make most often when they first look at a Helm retainer is a straightforward one. They find a capable operator on Upwork, calculate the monthly cost at ten or fifteen hours a week, and set that number next to the Helm retainer. The Helm number is higher. The conversation usually starts there.
It is a reasonable comparison to make. It is also an incomplete one, and the parts it leaves out are where the real cost lives.
What the single hire actually costs
The visible cost of a single hire is the hourly rate multiplied by the hours. At the upper end of the Upwork market for a quality operations coordinator, that is somewhere between $1,500 and $2,000 per month for a part-time allocation. On paper, that is cheaper than a Tier 1 Helm retainer.
What that calculation does not include is the time spent finding the person. A serious search for a quality operator takes two to four weeks of active effort: writing the brief, reviewing applications, running interviews, checking references, and making the hire. For a founder already carrying the operational weight of the business, that time costs more than it appears on a calendar.
It also does not include the onboarding period. A new hire, however capable, needs context. They need to understand how the business operates, what the priorities are, where the systems live, and what good looks like in this specific environment. That transfer of context takes time, and during that period the founder is doing two jobs: running the business and building the operator's understanding of it.
And it does not include what happens when the hire does not work out. An operator who looked strong in the interview but turns out to be the wrong fit means the entire process starts again. The search, the onboarding, the context transfer. The founder absorbs all of it.
What the single hire does not cover
Beyond the cost calculation, there is a structural problem with the single hire that no price comparison captures: one person covers one function.
An operations coordinator handles execution and task management. An executive assistant handles the principal's time and communications. A systems builder handles the technical infrastructure. Each of these is a real and valuable function. None of them is the operating layer.
The operating layer is what sits across all of those functions: the coordination, the context-holding, the decision routing, and the connective tissue that makes individual functions work together rather than in parallel. When a founder hires one person to cover one function, the operating layer remains unstaffed. The coordination work, the decisions that require cross-functional context, the gaps between every defined role: those continue to sit with the founder.
This is why most founders who have made several hires over the course of a year or two are still carrying the business. Each hire was the right hire for what it was. None of them addressed the structural gap.
The continuity argument
The cost comparison also misses the continuity dimension entirely. A single hire is a single point of failure. When that person leaves, gets sick, or moves on, the function they covered disappears with them. The founder is back to carrying it, back to searching, back to the onboarding cycle.
A properly staffed bench does not have a single point of failure. The chief-of-staff function holds context across workstreams, which means that when a specialist role changes, the operating layer continues. The replacement guarantee means the search and placement is handled without the founder re-entering the hiring process. The systems and documentation built into the operating infrastructure mean that context lives in the process rather than in the person.
The cost of continuity is not visible until continuity breaks. Founders who have lost a key operator mid-project, mid-client-engagement, or mid-growth phase know exactly what that costs. It is not a line item on a spreadsheet. It is a set of weeks where the founder is both running the business and absorbing the gap.
What the retainer actually covers
A Helm retainer is not a markup on the cost of a single operator. It covers the operator, the vetting process that preceded the placement, the coordination layer that sits above the work, the replacement guarantee, and April's oversight of the bench. It covers the onboarding infrastructure that reduces the context-transfer period. It covers the operating methodology that reduces key-person dependency over time.
The founder paying a Tier 1 retainer is not paying for one person doing tasks. They are paying for a running operating layer, not a search process.
The comparison to a direct Upwork hire is understandable. It is also a comparison between two different things. One is a person. The other is infrastructure.
Where to start
The strategy session exists to map what the operating layer actually needs to look like for a specific business at a specific stage. The cost and configuration question gets answered there, with the full picture rather than a line-item comparison.