What an OBM actually does (and why it's not a glorified VA)

If I had a dollar for every time someone confused an OBM with a VA, I could probably retire early. I get it. The online business space is full of people with similar-sounding titles doing wildly different things, and if you're a founder trying to figure out what kind of support you actually need, the noise is genuinely unhelpful.

So let me just cut through it.

A Virtual Assistant executes. You tell them what to do, they do it. Tasks in, tasks out. That's not a criticism at all. Great VAs are worth their weight in gold and the right VA at the right stage can completely change how your week feels. But they're working in your business, not on it. They need direction, a clear brief, and someone to quality-check the output. That someone is usually you.

An Online Business Manager is deeply strategic. We look at the whole picture. What's working, what's not, where the bottlenecks are, and what needs to change so the business can actually grow without you personally holding every thread together. We don't wait for the task list. We build the system that makes the task list unnecessary.

The confusion is understandable

Part of the problem is that OBM has become a bit of a catch-all title online. You'll find people calling themselves OBMs who are essentially doing admin support at a slightly higher level. You'll find others who are genuinely operating as fractional COOs, sitting in strategy meetings, managing senior team members, and making real operational decisions. The title covers a massive range.

What I'd encourage any founder to look at is not the title but the scope of work and the level of thinking involved. Are they waiting to be told what to do, or are they proactively identifying problems and bringing solutions? Are they managing tasks, or are they managing outcomes? Are they working to your brief, or are they helping you build the brief in the first place?

That distinction matters more than whatever someone calls themselves on their website.

What I actually do inside a founder's business

When I step into a new engagement, I'm not waiting for a task list. The first thing I do is assess. Where are the systems? Who owns what? What's documented and what exists only in the founder's head? Where are the bottlenecks, and are they process bottlenecks or people bottlenecks? What's the founder spending time on that they shouldn't be, and what's falling through the cracks because nobody owns it?

That diagnostic lens is something a VA isn't typically brought in to do. It requires a different level of access to the business, a different level of trust, and a different kind of thinking.

From there, the work varies depending on the founder and the stage of the business, but broadly it looks like this.

Where it gets interesting for me personally

I'm also a certified life coach and NLP practitioner. I don't lead with that because this isn't a coaching business. It's an operations business. But it shapes everything about how I work, and I think it's worth being honest about why.

Most operational problems aren't actually operational. I've said this before and I'll keep saying it because it's true and it changes everything about how you approach a fix. The chaos in a business is usually a symptom. The founder who can't stop being the bottleneck is often dealing with a very human difficulty around letting go of control. The team that's not performing is often dealing with unclear expectations or communication that doesn't actually land. The system that keeps breaking down is often breaking because the humans inside it haven't been properly set up to use it.

I see all of that. I'm trained to see it. And knowing what I'm actually looking at means I reach for the right solution instead of rebuilding the system and watching the same problem reappear three months later.

That's the part that's hard to put in a scope of work. But it's also the part that makes the biggest difference to how things actually change.

What working together actually looks like

Some founders stop there. They take the plan and run with it themselves, or they bring in their existing team to implement. That's completely fine and it's still a genuinely useful piece of work.

Most don't stop there. Because once you've seen the full picture clearly, the next question is usually: okay, so who's going to build this? And that's where the retainer or the 90-Day Sprint comes in.

Why I keep the client numbers small

This is intentional and it matters. I don't take on ten retainer clients and spread myself thin across all of them. I work with a small number of founders at a time because that's the only way I can actually show up properly.

Real operational support requires real access. It requires knowing your business well enough to make good decisions, to catch things before they become problems, to push back when something needs pushing back on. You can't do that at scale. Or rather, you can try, but what you end up delivering isn't OBM work. It's managed task coordination, and that's not what I do.

If you're looking for someone to hand a list to and check back in on at the end of the week, I'm genuinely not the right fit. If you're looking for a trusted second-in-command who will care about your business the way you do and bring the experience to back it up, that's exactly what I'm here for.

The question I get asked most

How is this different from just hiring a full-time operations manager?

A few ways. First, cost. A senior ops hire is a significant fixed overhead, salary, benefits, management time, the risk that it's not the right person. A fractional engagement is a fixed investment with a clear scope and no ongoing employment commitment.

Second, speed. A new hire takes time to onboard, learn the business, and start adding value. I've done this enough times that I hit the ground running. The diagnostic lens I bring to a new engagement means I'm adding value from week one.

Third, flexibility. Your business needs will change. The level of operational support you need at one stage isn't necessarily what you need six months later. A fractional arrangement can flex with that in a way a full-time hire can't.

And fourth, honestly, the coaching layer. A traditional ops manager is focused on the operational mechanics. I'm focused on those and on the human dynamics underneath them. That combination is unusual and it's the thing my clients consistently say made the biggest difference.

So, do you need a VA or an OBM?

If you need tasks done efficiently and reliably: VA.

If you need someone to run the operational side of your business, build the systems, manage the team, and give you a clear and honest picture of what's actually happening: OBM.

If you're genuinely not sure which one you need, sit with this question. Are your problems about capacity, not enough hands to get things done? Or are they about clarity, not enough structure, not enough systems, not enough visibility into what's working? Capacity is a VA problem. Clarity is an OBM problem.

Most founders who come to me think they have a capacity problem. When we get into it, it's almost always a clarity problem. And no amount of extra hands fixes that.

That's a good place to start.