VA, OBM, COO, Chief of Staff: The Answer Is None of the Above (Until You Answer This First)

The question of who to hire first comes up constantly in founder communities. And the advice is everywhere and contradictory. Hire a VA first. No, hire an OBM. Actually, you need a COO. Some people say chief of staff. Others say project manager. A few say you should not hire anyone and just build more systems.

Every person giving this advice has a story of how their recommendation solved their problem. And they are all right — for themselves.

Here is the issue: the question “who should I hire first” is actually the second question. The first question determines whether any particular role is the right answer for your situation. And almost nobody is asking the first question.

The First Question

The first question is this: where is the actual bottleneck in my business right now?

Not where do I feel most overwhelmed. Not what takes the most time. Not what I dislike doing. Where does work back up? What function slows down or stops when I am unavailable? What is the one place where, if I removed my personal involvement, the business could not keep up with its own demand?

Every business has a primary bottleneck at any given stage. The right first hire is the hire that directly addresses that bottleneck. Any other hire — no matter how impressive the title — is a hire that does not solve the core problem.

This is why generic advice about who to hire first produces such inconsistent results. The founder who was drowning in admin hired a VA and got relief because admin was her bottleneck. The founder who had clients but chaotic operations hired an OBM and got relief because operations was her bottleneck. Both recommendations were correct. For those situations. Neither is universally correct.

The question is not “what worked for her.” The question is “what is actually constraining me.”

How to Find Your Real Bottleneck

Finding the bottleneck requires honest analysis rather than gut feeling. Gut feelings tend to identify where the most frustration lives, not where the actual constraint is.

A useful exercise: list every major function in your business — client delivery, operations and project management, sales and business development, marketing and content, finance, team management. For each one, ask: if I fully removed myself from this function for four weeks, what would break?

Not what would be inconvenient. Not what would require more effort from someone else. What would actually break in a way that cost the business money or clients or reputation.

That is your bottleneck. The function where your involvement is the difference between the business working and the business breaking down.

A secondary question: in the functions that would not break without you, is someone already managing them — or are they running on autopilot without real ownership? Both are different situations and point to different needs.

Four Scenarios and What They Point To

Most founders at the multi-six to seven-figure stage fall into one of four scenarios when it comes to their actual bottleneck.

Scenario one: the bottleneck is in delivery. The founder is still personally doing a significant portion of the client-facing work. Without her, deliveries would be delayed or quality would drop. In this case, the right first hire is a delivery hire — someone who can extend the founder’s capacity for the actual work clients are paying for. This might look like an associate, a junior team member, a licensed practitioner, or a specialist depending on the industry. The focus is on adding delivery capacity, not operational or administrative support.

Scenario two: the bottleneck is in operations. The business has clients, revenue, and even some team members, but the back end is constantly on fire. Deliverables fall through cracks. Systems are not being followed. The founder is spending hours on coordination, logistics, and chasing down things that should not need chasing. This points to an operations hire — someone who owns the machine that runs the business. An OBM or director of operations at the right seniority level, not a VA.

Scenario three: the bottleneck is in pipeline. Revenue is strong when the founder is focused on business development but drops when she is heads-down in delivery. She is the only person who can generate and close new business, and the cycle between full pipeline and empty pipeline is getting exhausting. This points to sales support — not necessarily a full salesperson, but someone who can maintain pipeline consistency so the founder’s delivery cycles do not crater the business development function.

Scenario four: the bottleneck is founder-as-decision-maker. The team is in place, operations are handled, delivery is running. But every significant decision still routes to the founder. Her approval is needed before things move. Her judgment is the quality control system for everything. Growth is constrained not by what the team can do but by what one person can decide. This is the scenario that points to a fractional COO or an operations leader at the function-owner level — someone who can hold decision authority across multiple domains so the founder can operate at the strategic level.

What These Roles Actually Are (Not What the Titles Suggest)

Part of what makes this question hard is that the titles are genuinely confusing. VA, OBM, director of operations, COO, chief of staff — these titles mean different things in different companies, are used inconsistently in the market, and often get applied to roles that are either over- or under-scoped relative to what the title implies.

A virtual assistant in most founder-led businesses handles administrative and task-level work. The work flows through them from the founder. They execute. They do not make decisions about what needs to happen or how.

An online business manager or director of operations, done well, owns an operational function. They are accountable for outcomes in that function. They make decisions within it. They manage the systems and, often, the people in their domain.

A fractional COO operates across all operational domains. They run the business with the founder rather than under her. They own strategic and operational decisions across functions. They are a leadership-level role, not an elevated operations manager.

The jump between these levels matters. Hiring a VA when you need an OBM gives you task execution when you need ownership. Hiring an OBM when you need a fractional COO gives you operational management when you need operational leadership. Getting the level wrong is often why hires do not deliver the relief the founder was hoping for.

The Question That Comes Before Role Selection

Before you decide what role to hire, ask one more question: what does this person need to own, not just do?

If the answer is a defined list of tasks, you are hiring at the task level. If the answer is a function, you are hiring at the ownership level. Most founders at this stage need ownership-level hires. But they default to task-level hires because task-level feels lower risk. Less ambiguity about the scope, less investment required, easier to undo if it does not work out.

The problem is that task-level hires for ownership-level needs produce exactly the frustration founders are trying to escape. More people doing things. No one actually owning anything. The founder still in the middle of every decision.

Know your bottleneck. Know the level of the role you need. Then find the person. In that order.

---

Enjoyed this article? Follow Nata on Instagram for more practical insights, behind-the-scenes lessons, and tools to help you lead your business with more clarity and less overwhelm.

→ Instagram: @accidentalceo.co
→ Website: AccidentalCEO