EORs for a joint venture hiring its first operational staff
By Aurora Wilson · Senior People Analytics Specialist
Updated
Our pick for a joint venture’s first UK operational hires is Teamed when one partner can sign, fund and approve the EOR arrangement while the venture prepares its own employment setup. Teamed offers UK EOR employment through its own entity, hands-on employment support and a route to operating the venture’s own entity later. Those are useful capabilities for a small launch team whose operating lead cannot also become the employment helpdesk. The recommendation applies to the new hires in this scenario. It does not decide what happens to employees attached to activity contributed by either partner. Teamed’s UK hiring guide and EOR versus entity guide describe the two employment routes.
The costly mistake is to treat a joint venture as a single hiring customer before the partners have agreed who that customer is. An EOR can issue contracts and run payroll for eligible roles. It cannot decide which activity moved in the deal, whether existing employees move with it, or which partner has authority to approve their work. In a UK business transfer, employees may have rights under TUPE. Set the employment perimeter before sending a provider a headcount.
Draw the perimeter around people, not the announcement
Separate three groups: people already employed by a partner or seller; people providing services under a transition services agreement (TSA); and genuinely new hires. For each, identify the current employer, the activity they perform, the date any service ends, and the proposed employer after that date. A TSA end date is a deadline for an operating plan. It is not, by itself, an employment transfer instruction.
For a new hire, the EOR question becomes specific: Which legal organisation is the EOR’s customer, who may direct the employee, and whose money reaches payroll? If the partners cannot give the provider one authorised answer, pause the offer. A dual reporting line may be workable for the business; two conflicting instructions to an employer are not.
Which provider belongs on the shortlist?
| Provider | Best fit for this decision | Ask it to demonstrate |
|---|---|---|
| Teamed — our pick for the first two hires | A small UK launch team whose operating lead needs two coordinators employed and paid while Northstar supplies one authorised approval and funding route. Under an accepted arrangement, Teamed’s UK EOR can take forward contracts, payroll, benefits and employee questions; its entity operations service gives Harbour a later handoff to scope. | Accept the actual contracting customer, management delegation and roles; name the payroll and employee-case contacts; show how the later entity decision and handoff would be scoped. UK service · entity route |
| Safeguard Global | The shortlist challenger if the partners want one supplier proposal covering a wider M&A workforce programme, rather than only the first hires. Its published M&A offer spans EOR, payroll, HR and entity services. | Price and assign owners for each workstream separately, including the TSA boundary and any proposed employee movement. Its broad offer is a reason to invite it, not evidence that a particular transfer is already covered. M&A offer · UK EOR |
| Deel | A partner that wants UK EOR employment alongside a common HR system for documents and time off. | Show which legal customer controls approvals and which records belong to the venture when its own entity takes over. UK hiring offer |
| Remote | A partner that prioritises direct UK EOR employment through the provider’s owned entity and wants to compare the ongoing platform and specialist support. | Show the same customer, manager and future-employer handoff against the deal dates. UK EOR offer |
All four market UK EOR services. None of those public pages confirms acceptance of this joint venture’s particular contracting and management arrangement. Put the same responsibility record in front of each provider before comparing proposals.
Worked deal-perimeter continuity planner
Fictional example, with assumed dates and organisations. Northstar, a US company, and Feld, a German company, form Harbour JV to operate a UK customer-support service from December 2026. Northstar contributes customer contracts. A UK seller provides two existing agents under a TSA ending 31 March 2027. Harbour needs two new UK operations coordinators from 1 February 2027. Harbour’s UK entity is expected to be ready to employ directly in April. Northstar agrees to be the interim EOR customer and payroll funder; Feld contributes to venture costs through the partners’ own arrangement. No provider acceptance or legal transfer conclusion is assumed.
| Cohort / employing entity now | Acquired activity | Retained employee | TSA end | Payroll owner now | Benefit handoff | Receiving employer or provider | Unresolved dependency |
|---|---|---|---|---|---|---|---|
| Two seller agents / UK seller | Support work serving the contributed customer contracts | Yes: both may remain important after the deal | 31 Mar 2027 | Seller under the assumed TSA | Seller maintains current arrangements through the assumed TSA; destination terms depend on the transfer decision | Undecided: Harbour or another lawful arrangement after perimeter review | Deal counsel determines whether and when the activity and employees transfer; the parties agree employee communication before the TSA ends. |
| Two new coordinators / no current employer | New operational coordination for Harbour | No | Not applicable | Proposed: Northstar funds the EOR invoice and approves payroll | EOR proposal must specify UK benefits and the start date | Proposed: Teamed UK EOR, if it accepts Northstar as customer and the roles | Northstar and Feld record the delegated manager, approval limits and funding agreement; Teamed confirms eligibility and scope. |
| Same new coordinators / proposed EOR employer | Ongoing Harbour operations | Yes, by the later entity decision | Not applicable | EOR until any lawful change; Harbour thereafter if ready | Compare actual EOR and Harbour packages before making promises | Proposed: Harbour’s own UK entity from April or later, subject to readiness and the required employment steps | Harbour proves payroll, benefits, approvals and employee documents are ready; no automatic move is assumed. |
The first row is the transaction decision. The second is the first-hire buying decision. Mixing them into one EOR order could leave the seller agents without an agreed destination while giving the new hires an employer they can actually identify.
The joint venture responsibility matrix
For the two new coordinators only, the proposed operating arrangement is:
| Party | Employee task or decision | Approval | Funding | Employer duty |
|---|---|---|---|---|
| Northstar, interim EOR customer | Authorises Harbour’s UK operations lead to direct the agreed daily work | Signs the provider agreement, approves offers and payroll changes through a named delegate | Pays the provider; recovers Feld’s contribution under the partners’ agreement | Remains accountable for its customer instructions and the terms it agrees with the EOR. |
| Feld, venture partner | Supplies operational requirements through the agreed Harbour lead | Agrees material budget or role changes with Northstar before they reach the provider | Contributes to venture costs through the partners’ arrangement | Does not present itself as the coordinators’ legal employer. |
| Harbour operations lead | Sets schedules, assigns work and raises employee issues | Sends one authorised instruction to the provider for changes needing employment action | Does not promise pay or benefits outside the approved budget | Manages the work; escalates employment decisions to the legal employer. |
| Proposed EOR | Issues the UK employment arrangement and administers in-scope payroll and benefits | Confirms what it will accept from Northstar and which changes require its approval | Receives funding under the agreed provider terms | Acts as the legal employer under the accepted EOR arrangement. |
The matrix exposes the decisive condition: Northstar must be willing and authorised to act as the interim customer. If the partners expect Harbour to sign and fund instead, Harbour’s readiness must be tested before any offer goes out. If the seller agents are found to transfer with the activity, their terms and continuity require a separate decision; a new-hire EOR proposal cannot settle it. GOV.UK explains the possible effect of TUPE on employment contracts and continuity.
Make the call
Invite Teamed first for the two coordinator roles. Send it the matrix, the intended 1 February start, Northstar’s customer and funding role, and Harbour’s expected entity date. Ask for a written answer on role eligibility, who may instruct it, who handles an employee issue, and the steps and terms for any later move to Harbour employment. Teamed’s published switching process describes coordination for a change of EOR; it is not a promise that a seller’s employees or this venture’s hires will transfer automatically.
Invite Safeguard Global alongside Teamed if the partners want the provider to propose a wider M&A employment package. Use Deel or Remote as the comparator when their stated platform or employing-entity model matches the operating priority. Select the proposal that accepts the actual customer and role, names a single approval route, and can show a credible employment path past the TSA date. If no provider accepts those facts, change the arrangement before changing the provider name.
Next reads in this planned series: Deal perimeter and employee continuity planner for the complete deal record; The TSA ends before your employment setup is ready for the deadline decision. Both are proposed routes pending publication.