What a Tier 1 Helm engagement looks like week by week.
Most people understand the concept of a staffed bench. Fewer have a clear picture of what it actually looks like in practice — what changes in the first week, what is running by week four, and what the engagement looks like once it has found its rhythm.
This post walks through a Tier 1 engagement: one operator, one function, part-time allocation. It is the smallest configuration Helm offers and the most common entry point for founders who know they need support but are not yet ready to hand over the full operating layer.
What Tier 1 actually is
A Tier 1 engagement is a single vetted operator at ten to fifteen hours per week, handling a defined set of tasks within one function. Most commonly that is an operations coordinator or an executive assistant, depending on where the founder is carrying the most weight.
The operator is placed, onboarded to the client's systems, and coordinated by Helm. The founder does not manage the hiring process, the performance conversation, or the replacement search. They direct the work. Helm runs the bench.
The retainer sits between $2,500 and $3,500 per month. That is not what a direct Upwork hire costs at the same hours. It is what a vetted, managed, replaceable operator with Helm's coordination overhead and systems onboarding costs. The distinction matters and it is worth being clear about it from day one.
Before week one: the strategy session
Every Helm engagement begins with a paid strategy session. This is not onboarding. It is the diagnostic that makes onboarding possible.
In ninety minutes, the strategy session maps the founder's operating layer: what they are currently carrying, what is breaking, and where the highest-leverage point of intervention is. For most Tier 1 clients, the session surfaces one or two functions where the founder is spending significant time on work that belongs below them. The session produces a scoped bench recommendation and a retainer proposal.
The strategy session is paid separately and does not apply to the retainer. It is the qualification mechanism for both sides. The founder leaves with a clear picture of what changes and how. Helm leaves with enough context to place the right operator and brief them properly from day one.
Week one: systems access and operating context
The first week is not about output. It is about context transfer.
The operator is given access to the relevant systems: inbox, calendar, project management tool, CRM, communication platforms. Helm's onboarding process establishes the working rhythm, the communication preferences, and the decision boundaries. What the operator can action independently. What requires the founder's input. How handoffs work.
Most founders underestimate how much implicit knowledge they hold about their own business. The first week surfaces that knowledge and begins transferring it to the operator in a structured way. This is not a slow week. It is a necessary one.
Weeks two and three: the rhythm takes shape
By week two, the operator is handling recurring work with increasing independence. For an operations coordinator, this typically means owning project tracking, workstream updates, and the administrative layer that was previously sitting with the founder. For an executive assistant, it means owning calendar, inbox triage, and the communication layer the founder was managing directly.
The founder begins to notice the shift not in dramatic ways but in small ones. The Monday morning catch-up is shorter. The tasks that were waiting for their attention have already moved. The question that would have required a twenty-minute interruption has been handled.
This is when the coordination overhead starts to feel worth it.
Week four and beyond: the function is owned
By the end of the first month, the operator owns the function. Not in the sense that the founder is entirely removed from it, but in the sense that the function runs with continuity whether or not the founder is available on any given day.
The work moves. Decisions are made at the right level. The operator brings the founder into the picture when the situation requires judgment, not when it requires information that the operator could have found themselves.
This is the difference between a task-taker and an operator who owns a function. The task-taker completes what is given to them. The operator makes the function run.
What changes by month three
Month three is usually when founders notice the cognitive overhead shift. The tasks are fewer, but the more significant change is that the mental space previously occupied by those tasks has cleared. The founder is not anticipating what needs to happen, tracking whether it happened, or catching the things that fell through. The operator is doing that.
For most Tier 1 clients, month three produces one of two outcomes. The engagement continues at the same level because the scope is well-matched to the function that needed covering. Or the founder begins to see a second function where the same problem exists, and the conversation about Tier 2 starts naturally.
Neither outcome is the goal. The goal is a function that runs properly. What happens next follows from that.
What Tier 1 does not cover
A Tier 1 engagement is one operator, one function. It is not a complete operating layer. The connective work that runs across multiple functions, the coordination between an operations coordinator and a systems builder, the context-holding that a chief-of-staff function provides across all workstreams: none of that is part of a Tier 1 engagement.
This is not a gap in the model. It is the design. Some founders need one function covered and that is exactly what Tier 1 provides. Others need more, and the strategy session is where that determination gets made.
The right entry point
Tier 1 is the right entry point when the founder has one clearly defined function that is consuming disproportionate time, when they are not yet ready for a broader operating layer, and when the immediate priority is returning hours rather than transforming the infrastructure.
It is also an effective way to test the Helm model before committing to a larger configuration. The strategy session scopes the right entry point. For some founders that is Tier 1. For others it is higher. The session determines which.
If you are carrying one function that should not require your direct attention, that is where a Tier 1 engagement starts.