A company of thirty people in one country can run HR on a spreadsheet, a shared drive and a good memory. It is not elegant, but the assumptions underneath it all hold: there is one employer, one holiday list, one leave policy, one notice period, one payroll relationship, one currency and one set of documents.
The second country breaks every one of those assumptions on the same day. That is why the second country, not the fiftieth employee, is the event that ends the spreadsheet, and why so many companies find themselves buying HR software in a hurry three weeks after making an offer abroad.
The seven things that go plural
The employer. A person is employed by a legal entity, not by your company as a concept. Which entity employs them determines the contract, the notice, the statutory position and, if it ever comes to it, who is named. If you do not have an entity there, someone else is the employer, which is what an employer of record is.
The holiday calendar. Public holidays differ by country and often by state or region inside it. The single company holiday list is now wrong for somebody, and the person it is wrong for is the newest and most isolated employee you have.
The leave rules. Statutory minimums, accrual, carry-over and what happens to a balance on exit all differ. A single leave policy applied everywhere is either generous in one place or unlawful in another, and you will find out which when someone leaves.
Notice and probation. Both are set by local law and local practice. A template contract carried across a border is one of the more expensive documents a small company can produce.
Payroll. Statutory computation is per country, per year, under rules administered by a different authority. There is no version where one arrangement covers both. You now have two relationships, two cut-offs and two formats.
Currency. Pay is quoted, budgeted and paid in a second currency, and someone has to decide whether the person or the company carries the movement. Whatever you decide, decide it explicitly and write it down, because the alternative is renegotiating it during a bad quarter.
The document set. What a joiner receives and what a leaver expects differ. In some markets the relieving letter and the experience certificate are things people genuinely need for their next job. In others they do not exist.
Each of these on its own is a morning of work. Together, arriving in the same fortnight, they are the reason the first international hire feels disproportionately hard.
The things that quietly stay singular
Here is the part that catches people out. While seven things go plural, four things must not, and the instinct under pressure is to split them.
The directory. One place holding every person, in every country, employees and contractors together. The moment there are two directories, there is no reliable group headcount, anyone who moves has two records, and every question about the whole company becomes a reconciliation. Whatever else you do in the second country, do not solve it by starting a second system.
The policy library. Common policies written once, with a short local annexe per country. Three drifting handbooks is a worse outcome than one imperfect handbook with three annexes.
The audit trail. One record of what happened, filterable by country. If the log is split, nobody can answer a question that spans both.
The exit. One export containing everything. Two systems means two migrations the next time you change anything.
The pattern is: operations go local, the record stays central. Everything that is genuinely determined by the jurisdiction should differ. Everything that is a property of your company should not.
Why it hits at the second country and not the fifth employee
Scale problems are gradual. You can feel a spreadsheet getting heavy at forty people and do something about it at sixty.
The second country is not gradual. It is a step change that arrives on a single date, and the reason is that most small company HR is built out of implicit singletons. The offer template assumes a notice period. The leave tracker assumes a holiday list. The onboarding checklist assumes a document set. None of those assumptions is written down anywhere, so none of them can be parameterised. They have to be found one at a time, usually by being wrong.
There is a second reason, less obvious. A single-country company can keep HR in someone’s head because there is one context to hold. The second country doubles the context and halves the overlap, and the person holding it is now wrong about half of what they know without any signal telling them which half.
The order that works
The general sequence for international hiring is covered in sequencing your first international hires: contractor first, employer of record next, your own entity last, with signals for when to move. What follows is the HR operations version of the same problem, once the hire is happening.
Before the offer. Decide the employment route and price it fully loaded, including employer contributions that do not appear in the salary. The employee cost estimator builds that from lines you name, and the contractor cost calculator does the equivalent for an engagement including fees and currency margin. Get the contract drafted locally rather than adapted from your home template.
Before the start date. Set up the second holiday calendar and the second leave policy properly rather than promising to sort it out later. Leave computed against the wrong calendar has to be recomputed for everyone affected, and that is a conversation with an employee rather than a database update. How to write a leave policy covers the decisions and the leave policy generator will draft one.
Before the first pay cycle. Agree the payroll relationship and the input format. This has a hard deadline that nobody sets, which is the first pay day.
Within the first month. Split the handbook into core and annexe. Decide the currency rule and write it down. Work out who reviews the local statutory obligations annually and put it in the HR compliance calendar.
Then there is the data question
One more thing changes at the second country that has nothing to do with employment law.
Your HR data now describes people in a jurisdiction with its own data protection regime, and it is probably stored in neither of the two countries involved. That is fine, and it is also a question you should be able to answer, because it will be asked, either by an employee or by a customer running diligence on you.
The distinction that matters is between residency as a setting on a shared global system and residency as a genuine deployment boundary. What a data region actually is sets out the four questions that separate them. For an Indian workforce specifically, the DPDP Act and employee data covers notice, the employment ground, retention and what to ask a vendor.
What we build for this, and what we do not
Capstan is a system of record designed on the assumption that countries are symmetric. Employees and contractors sit in one directory across entities. Leave policy attaches to an entity, region or grade, and holiday calendars apply per person’s work location rather than one national list for everyone. Onboarding and exit checklists are templated per role or entity. Changes are effective-dated, so a transfer between entities is history rather than an overwrite. The operational detail is in running HR across multiple legal entities.
What we do not do is the part people most want a single vendor to do. Capstan computes no statutory payroll anywhere, holds no rate, slab or formula for any country, and is not an employer of record. The Payroll module compiles inputs into a documented export for whoever computes in each country, and files their results back. That is a permanent boundary, and the argument for it is in why payroll should be a partner.
So if your second country problem is “who will employ this person”, we are not the answer. If it is “how do I keep one honest record of people across two countries without maintaining two systems”, that is exactly what this is for. Every price, including every module, is on the pricing page.
The short version
The second country makes seven things plural in one week and tempts you to split four things that should stay whole. Get the entity question decided and priced, set up the second holiday calendar and leave policy before the start date rather than after, agree the payroll input format before the first cut-off, and keep one directory no matter what.
Everything else about hiring abroad is administration. Those four are the ones that are expensive to undo.