Small businesses hire these three titles almost interchangeably, and the mis-hire is expensive in both directions. The distinction that holds is not the task list. It is what each role is accountable for when something breaks.
I have sat on every side of this one. I have worked as a senior executive assistant carrying project scope, I have run delivery as a project manager, and I have watched owners hire an online business manager and hand them an inbox. The titles get used loosely because the day-to-day work genuinely overlaps: all three send the chasing message, build the tracker, and sit in the Monday meeting. If you compare the job adverts line by line you will not find the difference there.
You find it by asking a different question: when something goes wrong, who is answerable, and for what?
The distinction that actually holds
An executive assistant is accountable for one person functioning well. The calendar holds, the inbox gets answered or routed, the preparation exists before the meeting, the follow-through happens after it. The scope is a person, and the work is done by direct action.
An online business manager is accountable for the business running to plan day to day. This is the title people understand least, so let me be precise: an OBM is a manager of the whole back office, often fractional, who owns the operating cadence and the numbers that show whether the plan is happening. They manage contractors and team members, they own processes end to end, and they report against KPIs they are personally on the hook for. The scope is the operation.
A project manager is accountable for a defined piece of work shipping on time. A launch, a migration, a build. The scope has edges: a start, an end, a budget, a definition of done. A good PM is not promising to run your business. They are promising that this one thing lands, and that you hear about risk early instead of late.
| Role | Accountable for | Works through | Fails when |
|---|---|---|---|
| Executive Assistant | One person functioning well | Direct action | The executive absorbs work that should never reach them |
| Online Business Manager | The business running to plan day to day | People, process and KPIs | The owner is still the one chasing every loose end |
| Project Manager | One defined outcome shipping on time | A plan, a scope and a deadline | The project slips and nobody can say why |
All three send the follow-up message. The difference is what each one is answerable for when the follow-up was not enough.
Which one to hire, by symptom
Do not start from the title. Titles are what the last job advert you read happened to call it. Start from the symptom, because each role fixes a different failure.
Your own week is the bottleneck
Meetings collide, preparation does not happen, replies sit for days because you personally are the constraint on your own time. That is an executive assistant. It is also the cheapest of the three fixes and usually the first one worth making, because until someone owns your time, every other hire inherits the chaos.
The business only runs when you push it
You go on holiday and things stall. Contractors wait for you to assign work. Nobody else can say whether the month is on plan because nobody else is watching the numbers. That is an online business manager problem, and no amount of assistant hours fixes it, because the missing ingredient is not capacity. It is someone else holding the plan.
One defined thing has to ship by a date
A website rebuild, a system migration, an event, a product launch. The work has edges and a deadline, and it is currently drifting because everyone involved has a day job. That is a project manager, scoped to the project. When it ships, the engagement can end, and that is a feature rather than a flaw.
The rates reality
I am deliberately not quoting figures here, because rates for all three roles vary enormously by country, industry and seniority, and any number I print today will mislead someone next year. The relative structure, though, is stable and worth knowing.
OBMs typically price above EAs, and the gap is real. You are not paying for more hours of the same work. You are paying for management scope: someone who owns outcomes across the operation, carries KPIs, and takes decisions you would otherwise take yourself. Most OBMs work fractionally across a small number of clients, and they price like managers rather than like support.
Project managers scope per project rather than per month. A fixed engagement against a defined outcome, sometimes day-rated, sometimes a project fee. That makes them the easiest of the three to budget and the easiest to end well, because the end was defined on day one.
The trap is reading those price differences as a quality ranking. They are a scope ranking. A strong senior EA is not a cheaper OBM, and an OBM is not a premium EA. They are priced against different accountabilities, which is exactly why handing one the other's job goes wrong.
The hybrid truth
Here is what the clean three-way split leaves out: most small businesses do not need three people, and the single hire they actually need rarely matches one title cleanly.
In my experience the most common real need is an executive assistant who can carry project management scope. Someone who runs the executive's week as the baseline, and who can also take a defined piece of work, build the plan, chase the moving parts, and land it. Small businesses generate projects constantly: the rebrand, the new CRM, the hiring round. None of them individually justifies a dedicated PM, and all of them die when nobody owns them.
That hybrid is a real and available hire. It is what a strong senior assistant often already is, and it is usually the highest-return first operations hire a small business can make. The OBM hire makes sense later, when there is a genuine team to manage and a plan that needs holding while the owner steps back.
Most small businesses do not need an EA, an OBM and a PM. They need one person who runs the executive's week and can also ship a project. Hire for that, and say so in the advert.
What goes wrong
The most common failure I have seen is hiring the OBM title to get EA work done. The owner wants an inbox handled and a calendar held, but the advert says online business manager because it sounds more senior, and the salary offered sits somewhere confused in the middle.
It breeds resentment in both directions. The hire took the job to manage an operation and finds themselves booking travel, so they feel mis-sold and start quietly looking. The owner is paying manager rates for assistant output, so they feel overcharged and start quietly resenting the invoice. Neither party did anything wrong. The job was mislabelled before either of them arrived, and both are now paying for it. The same failure runs in reverse too: hiring an EA and then being disappointed that they did not restructure your operations uninvited. They were never accountable for that, and good ones know it.
The question that cuts through
Because the same titles cover such different jobs, the useful interview question is not about responsibilities. Whichever side of the table you are on, it is this:
What would I own that nobody else owns?
If the answer is a task list, it is a support role, whatever the title says. If the answer is an outcome with a date or a number attached, the title is probably honest. And if the answer cannot be produced at all, you have learned the most important thing early: nobody has decided what this job is, and the person hired will spend their first six months finding out the hard way.
The short version
An executive assistant is accountable for one person functioning well. An online business manager is accountable for the business running to plan day to day. A project manager is accountable for a defined piece of work shipping on time.
If you are hiring, name the failure you want to stop happening and let that choose the role. If you are the one being hired, ask what you would own that nobody else owns, and get it in writing. Everything else about these three titles is negotiable. The accountability is not.