EOR for Stealth-Mode and Pre-Launch Startups: Hiring in Belarus Before You Can Reveal the Company Name

You raised the seed round. You want to hire two senior engineers in Minsk starting next week. But the parent entity is a Delaware shell called “Aurora Holdings III” that you’d rather no one saw on a Belarusian employment contract. The commercial name isn’t finalized. You don’t want a LinkedIn announcement that reverse-engineers your team’s next move for the ex-employer your CTO just left. And you haven’t opened a Belarusian bank account — because you don’t have a Belarusian entity yet.

For the three-to-twelve-month window between funding and public launch, hiring in Belarus without leaking your identity is technically harder than most founders expect — and it’s exactly what an EOR structure is designed to solve. Here’s what actually happens during the stealth phase, where the leaks are, and how to close them.

The short version

• Stealth isn’t one thing. It’s a spectrum from “product name concealed” to “existence concealed” — the setup needs to match the level.
• Direct hiring in Belarus leaks the parent name at seven different touchpoints: contracts, payroll, tax filings, Belgosstrakh, LinkedIn, communication tools, and the entity registration itself.
• EOR structures break every leak point where a public record would form. Your commercial name doesn’t appear on the employment contract, the payslip, or any state filing.
• You can start hiring in Belarus before you’ve finalized where the parent will be domiciled. The client of record on the EOR agreement can be updated later.
• Candidates should know the real client under NDA. Stealth is about public records, not about deceiving your own team.
• The stealth setup you build in week one is the setup you’re stuck with until it’s time to change. Get it right the first time.

What “stealth” actually means for hiring

Stealth isn’t a single mode; it’s a spectrum. Founders reach for it for different reasons, and the level of information containment they need is different at each level.

Level 1 — Parent entity concealed. The public knows the product name, but the corporate parent (holding, fund vehicle, SPV) doesn’t need to be findable.

Level 2 — Product name concealed. Nothing about what you’re building is public, but the employer’s brand exists.

Level 3 — Investors concealed. You don’t want the cap-table associations visible on Google — often because the investor mix telegraphs your vertical.

Level 4 — Team composition concealed. No LinkedIn announcements, no “I’m joining X” posts. The hiring pattern is the leak.

Level 5 — Existence concealed. Nothing findable, at all. Rare, but this is the mode for founders with specific competitive reasons to stay dark.

Direct hiring in Belarus punches a hole through every one of these levels at once. The employment contract carries the employer’s name. Salary transfers land in the employee’s bank statement showing the payer. Social contribution filings register your parent as an operator with the state. Employees update LinkedIn.

Paul Graham’s classic essay on how startups die doesn’t spend much time on stealth mechanics, but it captures the core dynamic: the fastest way to burn optionality in the early phase is to leak information at hiring speed. EOR is the structure that breaks that trail — because the employer of record on every document is the EOR provider, not you.

Where the trail leaks — and where EOR blocks it

Seven specific leak points show up in a direct-hire setup. All seven close under an EOR structure.

Employment contracts. Direct hire: the contract carries the parent’s full name. Under EOR: the contract is between the employee and the EOR provider — your commercial name never appears on a document any Belarusian body will see.

Payroll and salary transfers. Direct hire: transfers show the parent name in the employee’s bank statement, on the payslip, and in any downstream reference. Under EOR: the payer of record is the EOR provider.

Social security and tax filings. Direct hire: the parent has to register as an operator with Belarusian tax and social bodies, which creates a state record. Under EOR: all filings run under the EOR entity.

Belgosstrakh registration. For compulsory workplace-injury insurance, direct hire requires the parent to register with the state monopoly. Under EOR: already registered.

LinkedIn and public profiles. This one isn’t fully closable — employees ultimately control their profiles. But a good EOR partner helps set expectations at offer time: employees add the EOR as employer, state “stealth-stage startup,” or leave the field blank. Any of those is a clean signal for the market.

Communication tools and infrastructure. Slack workspace names, Google Workspace domains, GitHub org names, Notion sites — all leak product identity if you don’t handle them deliberately. This is on you, not the EOR, but worth planning before day one.

The parent entity itself. Some founders haven’t finalized where the parent will be domiciled — Delaware, Estonia, UK, Cyprus, Singapore. Under EOR, you can start hiring in Belarus before that decision closes. Our hiring-in-Belarus guide covers the sequence in more depth.

What EOR provides in the stealth phase (and what it doesn’t)

Clarity on both sides matters.

What EOR provides:

• Legal employment of your Belarusian team, under the EOR’s own name.
• Employment contracts, offer letters, and payroll all under the EOR entity.
• All state-facing registrations and filings — tax, social contributions, Belgosstrakh — under the EOR.
• A commercial arrangement between the EOR and your parent (or SPV, or fund vehicle, or you personally in some setups) that can be structured lightly and doesn’t hit Belarusian public records.
• Onboarding materials that don’t require the parent name to appear where the Belarusian tax authority will see it.

What EOR doesn’t provide:

• Silence about the real client. Employees know who they’re working for — that gets handled at offer time under NDA, not hidden.
• Automatic IP protection. Assignment chains need to be drafted carefully, especially when the parent is unnamed or still forming.
• Cover for practices that are themselves illegal. Stealth is about identity containment, not about avoiding compliance.

Our EOR service handles the mechanics on the first list. The second list is where founder judgment stays required.

The offer-letter question — what employees know, and when

The most delicate part of stealth hiring is what the candidate sees at offer time.

The realistic setup: the employee signs an employment contract with the EOR. They know they’ll be doing engineering work for a client. The client identity is typically disclosed to the candidate under NDA before signing — otherwise you can’t recruit properly at any senior level. But none of that disclosure hits public records.

What can and cannot be kept from the candidate:

• What you’re building — can be disclosed under NDA, sometimes just described in categories (“consumer fintech,” “AI infrastructure”).
• Investors — same, handled under NDA.
• Corporate structure — usually irrelevant to the candidate, easy to keep confidential.
• Founder identity — hard to hide during interviews, and honestly shouldn’t be hidden. Senior candidates will refuse to sign without knowing.
• The EOR arrangement itself — should be disclosed clearly. Engineering candidates in Minsk are familiar with EOR structures and expect to see them at pre-launch companies.

Sam Altman’s startup playbook puts it plainly: the biggest hiring mistakes come from being cute about disclosure with the people you’re actually trying to hire. The stealth NDA is for the market, not the candidate.

Three flavours of stealth hiring — find yourself

Concrete scenarios, so you can locate yourself:

Scenario A: Funded, entity exists, product name not public. Parent exists under a working name that’s fine to disclose to counsel and banks but not to the market. EOR contracts employees under its Belarusian entity. Employees sign an NDA covering product name, investors, and roadmap. LinkedIn: employees show EOR as employer, or state “stealth-stage startup.” Both are legitimate and common in the Minsk market. Launch day: employees update to the real company name; the EOR arrangement can continue or migrate.

Scenario B: Funded, parent entity still being set up. The parent doesn’t exist yet in any usable form. Client of record on the EOR agreement can be a founder-owned SPV, an investor’s vehicle, or in some setups the founder personally under a service agreement. Hiring can start immediately — you don’t have to wait for Stripe Atlas or your equivalent incorporation service to finish before extending offers. When the parent is stood up, the client of record on the EOR agreement is updated. Employees see nothing change.

Scenario C: Not yet funded, pre-seed team assembling quietly. Riskier — founders often personally guarantee salary or use bridge financing during this phase. Some EORs will onboard on a founder-guaranteed basis; others require a corporate counterparty. Terms vary. Talk to the EOR up front. Scenario C is the one where structure matters most, because the alternatives to getting it right are expensive.

Contract mechanics that stay off the record

The specifics of how the client identity stays out of Belarusian records:

• The employment contract between the EOR and the employee is standard, in the EOR’s name.
• The commercial agreement between the EOR and the client is a private contract between two commercial entities. It isn’t filed publicly.
• Payment flows are between the client (wherever it’s registered — Delaware, Estonia, UK, Singapore) and the EOR. The client’s name doesn’t touch the Belarusian banking system in any employee-visible way.
• IP assignment flows through the employment contract (assigning IP to the EOR) and then through the commercial agreement (assigning that IP to the client). The chain has to be airtight — a stealth setup with sloppy IP assignment surfaces at Series A diligence and slows the round.
• Data flows. Productivity tools, monitoring systems, code metrics, and communication archives all generate personal data during the stealth phase — governed by Belarusian Law No. 99-Z.
• Communications routing. Email domains, Slack workspaces, and GitHub orgs are your decision. If you want to stay truly dark, use domain names that don’t reveal the product name. Common stealth pattern: a codename domain used for the entire stealth period, retired at launch.

The data-flow question is worth spending time on before your first hire. Our monitoring guide covers what your policies need to include when your parent name isn’t in the room yet — particularly around cross-border transfer, which stealth setups get wrong more often than any other issue.

Launch day — coming out of stealth cleanly

The transition matters, and this is where founders underplan.

Employee announcement. Coordinated with the marketing launch. Employees update LinkedIn together on the same day — not one at a time over the previous week, which happens if you don’t set expectations early.

The EOR arrangement usually continues. Most stealth startups stay on EOR for another 12–24 months after launch, until team size or entity strategy triggers a change.

Or you migrate. The team can move to your own Belarusian entity or a different EOR, using coordinated employment transfer with continuous service acknowledged. Our earlier piece on M&A covers the mechanics — the same playbook applies to any planned transition, not just acquisitions.

Series A diligence. Investors at Series A will look at the employment chain — that the EOR contracts, IP assignment, and payment flows during the stealth phase were all clean. Sloppy stealth setups get flagged at diligence and slow the round; sometimes they force a full re-papering of contracts before close.

FAQ

Can we start hiring in Belarus if our parent entity doesn’t exist yet?

Yes. The client of record on the EOR agreement can be a founder-owned SPV, an investor vehicle, or in some setups a founder personally under a service agreement. When the parent is stood up, the client of record is updated. Employees see nothing change.

Do we have to tell the employee the real company name at offer time?

You should, under NDA. Modern senior engineering candidates in Minsk expect to know who they’re actually working for before they sign — recruiting at any level of seniority without that disclosure is very hard. The stealth NDA is for the market, not the candidate. First Round Review has good writing on hiring transparency worth reading before you make offers.

Will the employee’s LinkedIn show our company name?

Only if the employee chooses to put it there. Common patterns during stealth: employees list the EOR as employer, write “stealth-stage startup,” or leave the field blank. All three are legitimate signals in the Minsk tech market and none creates a searchable link back to your parent name. Set the expectation at offer time.

What if we change the company name after launch — do employment contracts need to change?

Under EOR, no. The employment contract is with the EOR, not your parent. What changes is the commercial-level naming (public brand, investor materials, employee LinkedIn) — all of that is your call and doesn’t touch the underlying employment relationship.

Does stealth hiring cost more than regular EOR?

Typically not. The mechanics of stealth are structural, not operational: the same employment contracts, payroll, and filings run either way, they just don’t reference your commercial name. There may be a small setup premium if your parent structure is unusual (e.g., founder personal guarantee), but ongoing costs match a standard EOR arrangement.

What happens to IP created during the stealth phase — does it flow to the parent cleanly?

Only if the assignment chain is drafted carefully. IP goes from employee to EOR (via employment contract) to client (via commercial agreement). Any break in the chain surfaces at Series A diligence and can hold up a round.

Get the chain reviewed before your first hire, not before your first term sheet. Talk to our team if you want a review of your setup before it’s too late to fix.