EOR, BPO, staffing agency, embedded team: who employs, who manages, and who owns the outcome

A provider tells you they can have a senior accountant working alongside your controller next month. Depending on who is speaking, that means an employer of record, a BPO contract, a staffing agency placement, or an embedded seat. The proposals look close enough to compare on price. What you are buying in each case is a different thing.

Three questions sort them cleanly, and all three can be answered before anyone signs.

The three questions that separate the models

The three questions are these: who is the legal employer, who directs the work day to day, and who is accountable for the outcome.

Most evaluations start at rate and never reach any of them. That is the wrong order, because these three decide what happens on the days that actually cost money. The day priorities change and the work has to change with them. The day a person leaves. The day the number is short and somebody has to own why.

The first two questions get answered in the paperwork. The third one often gets answered nowhere at all.

EOR, BPO, staffing agency, embedded team: the grid

Here is how each of the four answers the three questions, and the work each one is genuinely built for.

• Employer of record. The EOR is the legal employer. You direct the work, and you are accountable for the outcome. An EOR exists to make employment lawful and administrable where you have no entity, which means payroll, statutory contributions, and local employment paperwork. It is a compliance instrument, and it is the right tool when you have already found the person and need a lawful way to employ them.
• BPO. The provider employs the staff, directs the staff, and is accountable to the specification you agreed. You stay accountable for whether the specification was the right one. That is the whole shape of the model. The spec is doing the job a manager would otherwise do, so the arrangement fits wherever the work can be written down completely and stays written down between reviews. Where that holds, a BPO is efficient in a way an embedded seat will never be.
• Staffing agency. The agency employs or contracts the person. You direct the work, and you are accountable for the outcome. What the agency sells is the search: it finds a qualified person faster than you would and carries the employment mechanics. It fits when the role is already well understood, you can onboard and run it yourself, and speed of sourcing is the binding constraint.
• Embedded team. The operator is engaged through the provider rather than by you. You direct the work day to day. Accountability for the outcome is split on purpose. You own the seat and what “done” means. The provider owns the environment around the seat, which is role health, standards, escalation, and whether the person is still there in two years. It fits recurring judgment work that depends on your context.

The first two questions get answered in the contract. The third one gets answered at quarter end, by whoever is left holding it.

Who the legal employer is, and why that is a separate question from who runs the work

The legal employer is whoever carries the employment obligations for that person, which covers payroll, statutory contributions, the termination process, and the liabilities that attach to employment where the person works. In each of the four models above, that party is someone other than you.

Worth being careful here. The answer is jurisdictional, it varies by country and by role, and in many places the way direction actually runs in practice matters as much as what the agreement says. Ask any provider you are evaluating to state the answer in writing, then have your own counsel read it against the country the person sits in. That conversation is short before signature and long afterward.

What the legal-employer answer does not tell you is how the work will run. An employer of record and an embedded team can sit behind similar employment structures and produce completely different working arrangements. Whether the person works inside your operation or behind a vendor boundary is its own decision, and we have written about embedded versus outsourced teams in depth.

Who is accountable for the outcome, and why that is the question that decides

Accountability for the outcome is the question buyers settle last and feel first.

With an employer of record or a staffing placement, it is yours entirely. That is a clean arrangement when you have the management capacity to carry it, and an expensive one when you assumed the provider was carrying part of it. With a BPO, the provider is accountable to the specification, so the outcome is only ever as good as the spec, and writing a good spec for judgment work is harder than doing the work.

With an embedded seat the accountability is split, and the split only holds if it is stated. You own what “done” means. Somebody has to own whether the seat stays healthy, which means whether the role still matches the work, whether standards hold, and whether drift gets caught while it is still small.

That layer has a name. In Operational Alpha I call it the interface: the way work moves between a person and a company, including the definition of done, the escalation path, the feedback rhythm, and who owns the health of the role. Every model above ships with some of it and leaves the rest to you. That gap between what the arrangement covered and what you assumed it covered is why most offshore work fails, far more often than talent is.

So run the grid on your own shortlist. Four models down the side, three questions across the top, and each provider fills in their own row in their own words. It takes twenty minutes, and it tends to sort the work as well as the vendors, because the model that fits work you can write down completely is rarely the model that fits the stream your controller has been quietly absorbing. That second sort is the own versus rent question, and the two decisions are better made together.

Quick answers

Kayana sits in the fourth row. We create Mini-GCCs for PE-backed middle-market companies, which means senior operators engaged through us, working inside your systems and your cadence, in seats you define. You direct the work and you own what “done” means. We own the environment around the seat, which is the part most arrangements leave unassigned. Voluntary turnover across our teams runs 3–5% in year one, and that number is the honest test of whether the environment is actually being run. Ask us the three questions. Ask them of everyone.

The full argument about designing the layer around the work is the book. Operational Alpha →