What Buying Employment as a Service Teaches
Everything that worked ran down one leg of the triangle, and everything that failed had to cross or fell outside.
Ending the service agreement
Ending the person's employment
Moving them to your own entity
The person simply resigning
YoursThe provider'sCrosses the twoNeither contract
Four matters, and no share: what any one agreement covers differs by agreement. One crosses both, and the handoff is where these arrangements fail. Three endings, and only one of them is yours to start and finish.
Everything that worked in this arrangement ran down one leg of the triangle. Everything that failed either had to cross a handoff or sat in neither contract.
The practical lesson in “What Buying Employment as a Service Teaches” is that a third-party arrangement still leaves day-to-day management with the operating team. Used for tips to increase productivity, see the provider’s implementation guidance can make time and project context easier to review, provided the purpose is disclosed, access is limited and every consequential inference receives human review.
That is the whole of what fifty notes amount to, and it is worth stating plainly at the end.
For a separate perspective on “What Buying Employment as a Service Teaches”, consult the NIST cybersecurity resources. Compare it with the actual contract, country and operating process rather than using a general resource as a local conclusion.
What the product is genuinely good at
Being the employer in a country where you have none. Payroll, withholding, statutory entitlements, filings, a compliant contract, and the removal of an employer-side exposure you would otherwise carry badly.
Done well it is worth the money, and doing it yourself for one or two people is worse on every measure.
What it was never going to do
Manage anybody. Judge work. Build a career. Make somebody want to stay. Notice that they have stopped wanting to.
None of that was sold, none of it is priced, and expecting it is the single commonest source of disappointment with providers who are performing adequately.
The crossings, listed
Pay rises. Title changes. Notice variations. Bonuses. Contract amendments. Terminations. Transfers.
Each needs you, the provider and usually the person. Each takes weeks rather than days, and each is where an arrangement that feels fine suddenly does not.
Why crossings fail
Not malice and rarely incompetence. Three parties, a local legal document and a payroll cycle produce delay structurally, and the delay is invisible from where the person stands.
The mitigation is anticipation and narration: start earlier than feels necessary, and tell the person what you have done rather than what will happen.
Neither costs anything. Both are skipped by managers who are used to deciding and delivering in the same breath, which is every manager who has not done this before.
The matters outside both contracts
Belonging. Progression. Equity. Pay review. Recognition. Whether anybody notices they are unhappy.
Nobody owns any of them by default. Each has to be assigned to a named person in your company or it does not happen.
These, rather than the crossings, are what people actually leave over. The crossings are irritating; the absences are the reason somebody concludes there is nothing here for them.
The single highest-return hour
Deciding who in your company owns this relationship, briefing the line manager on what is theirs and what is not, and putting an annual pay review in a calendar.
Three things, one hour, done once. They prevent most of what the rest of these notes describe.
What to read before signing
The exclusions. The liability cap and what sits outside it. The indemnity and which entity gives it. The notice periods, both of them, against each other. The contract template.
Five items:
- The exclusions.
- The liability cap, and what sits outside it.
- The indemnity, and which entity gives it.
- The notice periods, both of them, read against each other.
- The employment contract template.
They determine almost everything that will matter later and they are all available before you commit to anything.
The questions to ask a provider
Do you employ directly here. What is the total cost of employment. Walk me through a salary increase. What happens at the end. What are you excluded from doing.
The answers separate providers better than price, and all five are answerable in one call.
Where this arrangement fits
A small number of people, in places you will not build an entity, for a period you can see the end of, doing work that is valuable without being the core of what you are.
Outside that, it drifts toward being a substitute for building a company somewhere, which is a thing it does poorly and expensively.
The honest cost
More than the quote: equipment, recruitment, benefits, the deposit, and somebody's attention. More at the end than at the beginning, because severance grows with service.
Budget all of it at the start. The arrangement is usually still worth it and the business case should be the real one.
The person's view of it
They are paid by a company they do not work for and managed by a company that has not hired them. Everything that makes a job feel like a job has to be supplied by you on purpose.
Most of it costs nothing. All of it is skipped by default, which is why the arrangements that work are the ones where somebody decided they would.
What this collection cannot settle
Whether you should be doing this at all. That turns on how many people, for how long, how central they are, what the alternatives cost in each country, and what your company intends to be in three years.
Nothing general answers it, and a provider is the wrong party to ask. What the fifty notes offer is a picture of the shape you would be buying into — three parties, two contracts, one relationship with nothing written behind it — so that the decision is made with the structure in view rather than discovered a year in, one crossing at a time.