Bring your own payroll: the case for unbundling

The first time someone asked us “but does it do payroll?” we said no, slightly apologetically. By the tenth time, we had reframed the answer: we do not build payroll ourselves. We integrate with the providers who already do it well in each region, and that distinction is the entire point.

This post is about why.

The category bug

Look at the HR software category from a distance. Rippling. Gusto. BambooHR. Deel. Personio. Bob. Keka. They span funding rounds, geographies, and feature breadths, but they share one architectural choice: they all bundle payroll.

Bundling payroll feels like a strength. It is the most regulated, most painful, most expensive part of employing someone. Owning it gives you stickiness, billing power, and a clear wedge into the customer.

It also locks you to a geography.

Payroll is not just software. Payroll is a license, a banking relationship, a tax filing schedule, and a labor-law interpretation, all stapled to software. When you build payroll for India, you have built India. To add Germany, you do not write a new module. You start a new company.

This is why so many “global HR” platforms either operate in one country well and the others badly, or operate through a thin layer of regional partners and call themselves global.

For HR software for distributed teams, that architecture matters. If your team is hiring across borders, the tool you choose should not become less useful every time you enter a new country.

What “everywhere except payroll” looks like

The interesting observation is what is left after you peel payroll off the stack:

• Onboarding: sign the offer, upload the documents, complete the checklists
• Asset management: laptops, software licenses, return on exit
• Documents and policies: acknowledge, e-sign, version
• Leave and time off: request, approve, balance
• Offboarding: exit interview, asset recovery, relieving letter

None of these are local in the same way payroll is local. The shape of an offer letter changes by country; the workflow of accepting one does not. The compliance text in an asset return policy changes; the act of returning a laptop does not.

Payroll is inherently local. Everything else is inherently universal. The category mistakes one for the other.

What we built instead

ORGOS is the universal layer. Onboarding, assets, documents, offboarding: one workflow, every country, configured by AI based on region and team size.

What we do not do is calculate net pay, file taxes, or move money. That part stays with a regional specialist, either one you already use or one of our integrated payroll partners in regions where we have them available.

In India, that might be Razorpay or Keka. In the UK, Pento or PaySpace. In the US, Gusto or Justworks. Inside ORGOS, you see one workforce. Behind the scenes, the right regional specialist handles each payroll piece. Where we have built an integration, payroll runs through that connection so you do not manage two separate vendor experiences.

We call this bring your own payroll. The “bring your own” part is literal: you keep what works for you. The integrations are there when you want a one-stop setup in a region we support.

This is the same philosophy behind our view of startup employee onboarding. The workflow should stay consistent even when the paperwork changes.

Integrated partners, where they exist

To be clear about what is actually available today:

In regions where we have an integrated payroll partner, you can choose that partner during setup. Employee data, leave balances, and offboarding events sync into payroll automatically. You see it as one experience even though two systems are doing the work behind the scenes.

In regions where we do not yet have an integration, you continue with whichever provider you use today. Nothing breaks. ORGOS still runs your onboarding, assets, documents, and offboarding. Payroll just happens in a separate tool.

Our integration footprint grows by region, not by feature. Adding a country is not a six-month rebuild of the entire product. It is a partnership and a configuration set. That is how a universal layer is supposed to scale.

The shape of the offer is the same in both cases: ORGOS is the layer you live in. Payroll happens in a regional specialist, sometimes invisibly through us, sometimes alongside us.

The objection, and the answer

The most common pushback we hear is: “Doesn’t that mean I am running two systems?”

In regions where we have an integrated partner, the answer is no. Payroll is plumbed into ORGOS and behaves like one stack. In regions where we do not yet have a partner, yes, you run two tools.

But you were going to anyway.

The choice is not “one tool or two.” It is “two tools with a unified layer on top, or two tools and a spreadsheet.”

If you employ in two countries today, you are almost certainly using one payroll provider per country plus a Google Sheet for everything else: leave balances, asset inventory, contractor agreements, signed policy versions, exit checklists. ORGOS replaces the spreadsheet, not the payroll provider.

Why partnerships work better than competition

The companies we would be “competing” with on payroll, the regional providers, are our natural partners instead. Their customers already ask them for onboarding and asset management. They do not want to build it. We do build it. Together we look like a stack, and where the integration is live, customers experience us as one.

This is not a positioning hack. It is how distributed people operations actually works inside companies that have figured it out: one specialist per regulated function, one universal layer for everything else, and clean integrations where they matter.

What this means if you are building across borders

A few practical takeaways, if you are hiring across countries right now:

• Do not pick a tool that promises payroll in country X “coming soon.” It either is or it is not, and the answer rarely changes on the timeline you need.
• Do not pay for an EOR you do not need. Employer-of-record services are useful when you genuinely cannot open a local entity. They are expensive when you can.
• Separate your universal layer from your payroll layer in your head. Once you can name them separately, the tooling choice gets easier.
• Pick the universal layer first. It is the one you keep when you swap payroll providers, and a good one will integrate with the providers you choose in each region.

ORGOS is the universal layer. We integrate with regional payroll partners where we can, and stay out of your way where we cannot yet. That is the most useful thing we can be.

Try ORGOS. It works with your existing payroll, or with one of our integrated partners where available.