DEV Community: Priyom Sarkar

What Separates the Best EOR Provider from the Rest? 7 Questions Every Global Employer Should Ask

Priyom Sarkar — Tue, 28 Jul 2026 12:05:00 +0000

Hiring in a new country is exciting.
Choosing the wrong employment partner isn't.
Last month, I was speaking with the founder of a fast-growing SaaS company.

They had already found three excellent engineers in India.

Funding wasn't the problem.

Finding talent wasn't the problem.

The problem was much simpler.

"We have two EOR providers shortlisted. Which one should we choose?"
At first glance, both providers looked identical.

Both promised compliance.

Both promised payroll.

Both claimed they could onboard employees in less than a week.

Both had polished websites.

Both had impressive client logos.

But after about twenty minutes of conversation, it became obvious that one provider was significantly better suited for the business than the other.

Not because they had more features.

Because they answered better questions.

That's when it struck me.

Most companies don't struggle because they can't find an Employer of Record.

They struggle because they don't know how to evaluate one.

If you're trying to find the best EOR provider, stop comparing feature lists for a moment.

Start asking better questions.

The Best EOR Provider Isn't the One That Says "Yes" to Everything

One thing I've noticed is that weaker providers try to impress you with speed.

Great providers try to educate you about risk.

There's a huge difference.

The second answer may sound less exciting.

It's actually far more valuable.

The best EOR provider doesn't hide complexity.

They explain it.

Question #1: Who Is Actually Employing My Team?

This sounds obvious.

Surprisingly, many companies don't ask it.

An Employer of Record becomes the legal employer of your workforce while your company manages their day-to-day work.
Question #2: How Do You Stay Compliant When Regulations Change?

Here's something founders often underestimate.

Employment laws aren't static.

Payroll regulations evolve.

Tax requirements change.

Statutory obligations get updated.

Compliance isn't something an EOR does once.

It's something they continuously maintain.

One question I like asking is:

"What happens if employment regulations change next month?"

The answer tells you far more than a product demo ever will.
That relationship should be crystal clear.

If a provider struggles to explain this structure in simple terms, that's usually a warning sign.

The best partners make complicated things feel simple.

Question #2: How Do You Stay Compliant When Regulations Change?

Here's something founders often underestimate.

Employment laws aren't static.

Payroll regulations evolve.

Tax requirements change.

Statutory obligations get updated.

Compliance isn't something an EOR does once.

It's something they continuously maintain.

One question I like asking is:

"What happens if employment regulations change next month?"
The answer tells you far more than a product demo ever will.

The Best EOR Provider Should Think Like an Operator

One thing I've learned while building HR technology is this:

Founders don't buy software.

They buy confidence.

Confidence that payroll runs on time.

Confidence that contracts are compliant.

Confidence that employees have a great experience.

That's why I don't evaluate an EOR based only on features.

I evaluate them based on operational maturity.

Think about it like this.

Obviously, that's not how vendor selection actually works.

But the mindset is surprisingly similar.

Operational confidence always beats feature count.

Question #3: What Happens After the Employee Is Hired?

Many buying conversations stop at onboarding.

That's a mistake.

Hiring someone is the beginning of the relationship.

Not the end.

Ask yourself:

How will payroll queries be handled?
How quickly are support requests answered?
Can employees access their own documents?
How are leave requests managed?
What happens if an employee resigns?

The employee experience matters just as much as the hiring experience.

A poor HR experience eventually becomes an employer branding problem.

The Best EOR Provider Creates Invisible Operations

This might sound strange.

The best operational systems are the ones employees barely notice.

Nobody wakes up hoping payroll will work today.

They simply expect it to.

Nobody celebrates accurate compliance.

They assume it already exists.

That's actually the goal.

Good operations are almost invisible.

Great EOR providers make them feel effortless.

Question #4: Can Your Platform Scale With Us?

Hiring five employees is one challenge.

Hiring fifty is another.

Hiring across multiple countries?

That's an entirely different conversation.

One of the best questions you can ask is:

"If we triple our workforce next year, what changes?"
A mature EOR should already have an answer.

Growth shouldn't require rebuilding your HR operations from scratch.

Question #5: What Technology Do Employees Actually Use?

Not every EOR invests equally in technology.

Some still rely heavily on spreadsheets and email.

Others provide employees with self-service tools, digital onboarding, document access, payroll visibility, and mobile-first experiences.

Technology isn't just about convenience.

It's about reducing friction.

The less employees need to contact HR for routine questions, the more productive everyone becomes.

Question #6: Is the Pricing Transparent, or Just Attractive?

One thing I've learned from evaluating software vendors is this:

The lowest monthly price rarely tells the full story.

An EOR relationship isn't just another SaaS subscription.

You're trusting a partner with employment contracts, payroll, statutory compliance, employee documentation, and ongoing HR operations.

That makes transparency far more valuable than a discount.

Instead of asking:

"Can you reduce your pricing?"
Try asking:

"Can you explain every cost we'll incur over the next 12 months?"
You'll be surprised how revealing that question is.

The best EOR provider doesn't win because it's the cheapest.

It wins because there are no unpleasant surprises six months later.

Question #7: What Happens When Something Goes Wrong?

Here's a scenario nobody talks about during a sales demo.

An employee's payroll doesn't arrive on time.

Or a tax deduction looks incorrect.

Or an employee resigns unexpectedly.

Or a government regulation changes halfway through the year.

What happens then?

That's when the quality of an EOR is truly tested.

Anyone can promise a smooth onboarding.

The real differentiator is how they respond when things become complicated.

One question I always encourage founders to ask is:

"Can you walk me through a real situation where something didn't go according to plan—and how your team handled it?"
You're not looking for perfection.

You're looking for maturity.

A Simple Framework I Use to Evaluate the Best EOR Provider

When people ask me how to compare EOR vendors, I don't start with features.

I start with five areas.

If a provider scores well across these five areas, pricing becomes much easier to evaluate.

Because operational quality compounds over time.

The Best EOR Provider Doesn't Remove Responsibility-It Removes Complexity

This is probably the biggest misconception I hear.

Some companies think choosing an Employer of Record means outsourcing responsibility.

It doesn't.

You're still responsible for building a great culture.

You're still responsible for hiring the right people.

You're still responsible for performance and leadership.

An EOR simply removes the operational complexity that comes with employing people in another country.

That's a much healthier partnership model.

One Lesson That Changed My Thinking

Early on, I assumed companies selected an EOR primarily because they wanted to hire faster.

After speaking with more founders, I realized speed is only part of the story.

What they really wanted was confidence.

Confidence that payroll would be accurate.

Confidence that employment contracts complied with local regulations.

Confidence that their employees would have a seamless experience from Day One.

Hiring quickly gets attention.

Hiring correctly builds sustainable businesses.

That's why the best EOR provider isn't simply the fastest provider.

It's the one that quietly removes friction from every stage of the employee lifecycle.

Final Thoughts

India continues to attract companies from around the world—not just because of its talent, but because of the opportunities it offers for long-term growth.

The challenge isn't finding great people.

The challenge is creating an employment experience that's compliant, scalable, and consistent.

Choosing the best EOR provider isn't a procurement decision.

It's an operational decision that influences how your business expands, how your employees experience your company, and how confidently you can grow in a new market.

At Asanify, we've had the opportunity to work with organizations at different stages of global expansion. One insight consistently stands out: the best hiring experiences are built on strong operational foundations, not just fast onboarding.

The right EOR won't just help you hire in India.

It will help you build a business that's ready to scale.

How to Choose the Best EOR Provider for Hiring in India: A Founder's Guide

Priyom Sarkar — Fri, 24 Jul 2026 11:44:04 +0000

Hiring in India has never been easier. Hiring correctly is where things get interesting.

Over the last few years, I've had countless conversations with founders looking to expand into India.

The conversations usually begin the same way:

"We've found great talent in India. Now we're trying to figure out how to hire them legally."

A few years ago, the answer almost always involved setting up a legal entity, opening bank accounts, navigating local registrations, and building payroll operations from scratch.

Today, the conversation has changed.

More businesses are asking a different question:

"How do we choose the best EOR provider?"

It's a smart question.

But it's also one that often gets answered with feature lists and pricing tables instead of business strategy.

The reality is this:

Choosing the best EOR provider isn't about selecting a vendor.

It's about choosing the right partner for your global expansion journey.

Why the Best EOR Provider Is About More Than Hiring

Many companies first discover Employer of Record (EOR) services because they want to hire quickly.

That's understandable.

However, hiring is only one part of international expansion.

The right EOR partner influences:

Compliance
Payroll accuracy
Employee experience
Speed of onboarding
Business flexibility
Expansion costs

Think about it this way.

You're not outsourcing recruitment.

You're entrusting another organization with becoming the legal employer of your team.

That's a decision worth evaluating carefully.

What Does an Employer of Record Actually Do?

Before comparing providers, it's worth understanding what an EOR actually manages.

A quality Employer of Record typically handles:

Local employment contracts
Payroll processing
Statutory deductions
Tax compliance
Benefits administration
Employee onboarding
Employment documentation
Regulatory compliance

Meanwhile, your company continues to manage daily work, performance, goals, and culture.

The employee works with your business every day.

The EOR manages the legal employment framework behind the scenes.

Best EOR Provider Checklist: Start with Compliance, Not Convenience

One of the biggest mistakes I see companies make is focusing entirely on speed.

"How quickly can we hire?"

It's an important question.

It just shouldn't be the first one.

Instead, ask:

How well does this provider understand Indian employment regulations?

Every country has unique compliance requirements.

India is no exception.

Employment laws involve multiple statutory obligations, payroll regulations, tax requirements, and documentation standards.

An experienced EOR should already have mature processes for handling these responsibilities.

The faster a provider promises to onboard employees, the more important it becomes to understand how they're maintaining compliance.

Speed without compliance creates risk.

Best EOR Provider Evaluation: Look Beyond Pricing

Pricing comparisons dominate most buying decisions.

Unfortunately, they rarely tell the full story.

Instead of asking,

"Which provider is cheapest?"

Try asking,

"Which provider reduces operational complexity?"

A lower monthly fee can quickly become expensive if it results in:

delayed payroll
compliance issues
slow employee onboarding
poor support
fragmented HR processes

The real return on investment comes from reducing administrative effort while creating confidence that everything is running correctly.

Operational efficiency often matters far more than headline pricing.

Best EOR Provider Selection Should Consider Employee Experience

One perspective that's often overlooked is the employee.

Imagine joining a company where:

onboarding takes weeks
payroll queries remain unanswered
leave requests require multiple emails
documents are difficult to access

Even if your company culture is excellent, the employee's first impression may be shaped by administrative friction.

That's why the best EOR provider should support not only compliance but also the overall employee experience.

An EOR shouldn't simply process payroll every month.

It should provide technology that makes HR easier for everyone involved.

Consider whether the provider offers:

Employee self-service
Mobile accessibility
Leave management
Attendance integration
Payroll visibility
Compliance reporting
Secure document storage

Technology reduces manual work.

More importantly, it reduces uncertainty.

Employees shouldn't need to ask HR every time they want to understand a payslip or download an employment document.

Hiring one employee is relatively straightforward.

Hiring fifty is different.

One of the most valuable questions you can ask is:

"Can this EOR support our business twelve months from now?"

Growth changes everything.

The right EOR should grow alongside your business rather than forcing you to switch providers later.

Scalability is often underestimated during vendor selection.

The best EOR provider should create transparency for everyone involved.

That means:

clear pricing
defined responsibilities
documented processes
responsive support
straightforward reporting

Don't Evaluate an EOR Like Software

This is one mistake I find particularly interesting.

Companies often compare EOR providers the same way they compare software subscriptions.

Feature A.
Feature B.
Monthly price.

Done.

But an Employer of Record is fundamentally different.

You're evaluating an operational partner.

The relationship involves:

employment law
payroll
compliance
employee communication
ongoing administration

Success depends just as much on expertise and service quality as it does on technology.

Treating the evaluation like a software purchase often overlooks the factors that matter most.

The Right Partner Helps You Focus on Growth

One reason businesses choose an EOR is simple.

They want leadership teams focused on building products, serving customers, and growing revenue-not navigating unfamiliar employment regulations.

The right partner removes operational distractions.

The companies that succeed internationally aren't necessarily the ones with the largest budgets.

They're the ones that reduce unnecessary complexity.

An Employer of Record can support all of these goals-but only if you choose the right partner.

That's why selecting the best EOR provider should never be treated as a procurement exercise alone.

It's a strategic decision that influences your expansion journey from day one.

Final Thoughts

India continues to attract global businesses because of its incredible talent, growing technology ecosystem, and strategic importance.

But hiring internationally isn't simply about finding great people.

It's about building the right operational foundation.

The best EOR provider won't just help you employ people legally.

They'll help you create a smoother expansion experience-for your HR team, your finance department, your employees, and ultimately your business.

While building Asanify, we've had the opportunity to work with organizations navigating this exact journey. One lesson consistently stands out: companies don't just need an EOR-they need a partner that simplifies complexity while supporting long-term growth.

The technology will evolve.

Employment regulations will continue to change.

Business priorities will shift.

Choosing the right partner today makes adapting to those changes much easier tomorrow.

Thanks for reading!

If you're evaluating an Employer of Record for hiring in India, I'd love to hear what's influencing your decision.

Why Great HR Software Isn't About Features; It's About Making Policies Invisible

Priyom Sarkar — Wed, 22 Jul 2026 10:36:53 +0000

When you're a 10-person startup, policies feel unnecessary.Someone drops a message on Slack:

"Taking tomorrow off."

The manager replies:

"Sure."

That's it.

No approvals.

No workflows.

No confusion.

No documentation.

At that stage, speed matters more than structure.

But something interesting happens as companies grow.

The very processes that once made the organization agile begin creating friction.

Not because people stop communicating.

But because everyone starts interpreting the rules differently.

Growth Doesn't Break Culture. It Breaks Consistency.

I've noticed this pattern repeatedly while speaking with founders and HR leaders.

When teams reach 50, 100, or 300 employees, the biggest operational challenge isn't hiring.

It's consistency.

Questions that once had obvious answers suddenly become complicated.

Who approves leave?
Which attendance records are considered valid?
How are unused leave balances handled?
Why did payroll calculate this differently?
Which version of the policy applies?

None of these questions are difficult.

Until every manager answers them differently.

That's when operational complexity quietly begins to grow.

Most HR Problems Aren't Actually HR Problems

They're policy problems.

Take attendance as an example.

On paper, the policy is usually straightforward.

Employees should clock in through approved channels.

In reality, it becomes much messier.

One employee clocks in through a mobile app.

Another uses Slack.

Someone else uses a biometric device.

Another emails HR because they forgot.

Now imagine trying to explain six months later why one attendance record was accepted while another wasn't.

The issue isn't attendance.

The issue is that the policy exists in one place, while everyday work happens somewhere else.

Policies Should Guide People, Not Interrupt Them

Think about the software we use every day.

Google Maps doesn't ask whether you're allowed to make a turn.

It already knows.

Your banking app doesn't ask you to calculate transaction limits.

It applies them automatically.

Good software removes the need to remember rules.

The same principle should apply to HR.

Employees shouldn't have to memorize leave policies.

Managers shouldn't need to remember every approval exception.

HR teams shouldn't spend their day explaining processes that software could enforce automatically.

The best policy is often the one employees never have to think about.

Every Manual Exception Has a Cost

One manual correction isn't a problem.

A hundred manual corrections every month become an operational burden.

Consider how many requests HR teams receive that are almost identical.

"Can I correct yesterday's attendance?"
"How much leave do I have left?"
"Will this unused leave be paid out?"
"Why wasn't my attendance approved?"
"Which attendance source should I use?"

Individually, each request takes only a few minutes.

Collectively, they consume hours every week.

As organizations grow, the hidden cost isn't processing these requests.

It's repeatedly answering the same questions.

Mobile Has Changed Employee Expectations

Employees already manage banking, travel, healthcare, and shopping from their phones.

Naturally, they expect HR to work the same way.

Nobody wants to wait until they're back at their desk just to apply for leave or check a payslip.

The expectation isn't simply "mobile access."

It's immediate access.

Employees increasingly expect HR interactions to happen wherever they are—not wherever the office happens to be.

Good Systems Don't Just Store Policies

They Apply Them.

There's a fundamental difference between documenting a policy and enforcing it.

Many organizations have excellent policy documents.

The challenge is ensuring they're applied consistently.

A leave policy shouldn't depend on which manager receives the request.

Attendance shouldn't be interpreted differently across teams.

Payroll outcomes shouldn't vary because of manual calculations.

The software should understand the policy and apply it consistently.

That's when compliance stops being reactive and becomes part of everyday operations.

The Shift From Administration to Automation

For years, HR technology focused on digitizing paperwork.

Forms became portals.

Spreadsheets became dashboards.

Approval emails became workflows.

The next shift is more interesting.

Instead of asking HR teams to remember every rule, modern systems are beginning to apply those rules automatically.

That doesn't replace human judgment.

It removes repetitive decisions so HR professionals can focus on the situations that genuinely require context and empathy.

Automation isn't about eliminating people.

It's about eliminating unnecessary repetition.

What We're Learning While Building HR Technology

One of the biggest lessons we've learned while building Asanify is that customers rarely ask for more features.

They ask for fewer exceptions.

They want confidence that leave policies are applied consistently.

That attendance records remain trustworthy.

That payroll reflects the right outcomes.

That employees can access HR services without waiting for someone to respond.

In other words, they want systems that quietly enforce policies in the background, allowing HR teams to focus on people instead of processes.

And I believe that's where the future of HR technology is heading.

Not toward more dashboards.

Not toward longer policy documents.

But toward software that understands organizational rules and applies them consistently, without employees needing to think about them.

Final Thoughts

As companies grow, complexity is inevitable.

Confusion doesn't have to be.

The organizations that scale well aren't necessarily the ones with the most detailed policies.

They're the ones that make those policies easy to follow.

Because when employees spend less time figuring out how the system works, they spend more time doing meaningful work.

And that's what good software should enable.

Thanks for reading!

Employer of Record vs. Setting Up a Company in India: Which Is the Better Choice for Global Businesses?

Priyom Sarkar — Fri, 17 Jul 2026 12:15:21 +0000

Expanding into India is exciting. Deciding how to hire your first employee? That's where things get complicated.

One of the most common questions I hear from founders and business leaders is:

"Should we set up a company in India, or should we use an Employer of Record (EOR)?"

It's a fair question.

For many businesses, incorporating a local entity feels like the "proper" way to expand. But in reality, it's not always the most practical or the fastest option.

The right choice depends on your growth plans, hiring strategy, budget, and how quickly you want to enter the market.

Let's break down both approaches and when each makes the most sense.

Why This Decision Matters

Hiring your first employee in India isn't just about extending an offer letter.

You're making a strategic decision that will influence:

Hiring speed
Compliance responsibilities
Operational costs
Administrative workload
Long-term scalability

Making the wrong choice can slow expansion, increase costs, or create unnecessary operational complexity.

Option 1: Setting Up a Company in India

Incorporating an Indian entity gives your business complete control over local operations.

It also means your company becomes the legal employer.

That comes with responsibilities such as:

Registering the business
Managing statutory registrations
Running payroll
Issuing compliant employment contracts
Managing tax obligations
Handling employee benefits
Maintaining ongoing compliance

For businesses planning significant, long-term operations in India, this can be a worthwhile investment.

But it's important to understand that incorporation is just the beginning—not the finish line.

When Setting Up an Entity Makes Sense

You should consider establishing a local entity if you:

Plan to hire a large team in India
Intend to build a permanent business presence
Need a local office or physical operations
Want complete control over HR and payroll functions
Have the resources to manage ongoing compliance

If India is a core market in your long-term strategy, an entity often becomes the natural next step.

Option 2: Using an Employer of Record (EOR)

An Employer of Record allows companies to hire employees in India without establishing a local legal entity.

Here's how it works:

Your business selects the candidate and manages their day-to-day work.

The EOR becomes the legal employer, handling responsibilities such as:

Employment contracts
Payroll administration
Statutory compliance
Employee onboarding
Benefits administration
HR documentation

From the employee's perspective, they're working for your company.

From a legal and compliance perspective, the EOR manages the employment relationship in accordance with local requirements.

When an EOR Makes Sense

An EOR is often the better option if your business wants to:

Hire quickly
Test the Indian market
Build a small or growing team
Avoid the overhead of incorporation
Reduce administrative burden
Focus on business growth rather than local compliance

For startups and scale-ups, speed is often a competitive advantage.

Waiting months to complete entity setup before making your first hire isn't always practical.

Comparing Both Approaches

Neither approach is universally better.

The best choice depends on your business goals.

Here's what the real cost includes:

Time spent on setup
Internal legal resources
HR administration
Compliance management
Opportunity cost of delayed hiring

Sometimes the lowest upfront cost isn't the most efficient business decision.

When evaluating expansion strategies, it's worth looking at the total operational impact, not just the invoice.

A Question Worth Asking Before You Decide

Instead of asking:

"What's the cheapest way to hire in India?"

Ask:

"What's the smartest way to hire based on where our business is today?"

If you're hiring one or two employees to validate a new market, your priorities are likely speed and flexibility.

If you're building a 200-person operation over the next few years, investing in a local entity may make more sense.

Your hiring model should support your business strategy, not dictate it.

A Trend I'm Seeing

More global businesses are treating expansion as a phased journey.

They don't always establish a legal entity on day one.

Instead, they:

Hire their first employees
Learn the market
Build initial operations
Validate business demand
Then decide whether incorporating makes strategic sense

This phased approach helps reduce risk while maintaining momentum.

It also gives leadership teams more time to understand the local market before making long-term commitments.

Final Thoughts

There isn't a universal answer to the question of Employer of Record vs. setting up a company in India.

Both models have their place.

The important thing is choosing the approach that aligns with your current stage of growth; not where you hope to be years from now.

Expansion should create opportunities, not unnecessary complexity.

The simpler you can make your hiring process while staying compliant, the more time you'll have to focus on what really matters: building your business.

How to Hire Employees in India Without Setting Up a Local Entity: A Practical Guide for Global Founders

Priyom Sarkar — Wed, 15 Jul 2026 11:53:45 +0000

If you're planning to hire your first employee in India, you don't necessarily need to incorporate a company there first.

That's one of the biggest misconceptions I come across when speaking with founders and leadership teams exploring India.

Many assume the process looks something like this:

Register a company
Open a bank account
Hire legal counsel
Set up payroll
Build HR operations
Then...hire your first employee

For large enterprises, that may be the right path.

But for startups, growing SaaS companies, and businesses testing the Indian market, it's often unnecessary.

Over the past few years, I've noticed that companies expanding into India are asking a different question:

"How can we hire quickly, stay compliant, and avoid months of legal setup?"

The answer often isn't incorporating a local entity first.

It's understanding the hiring options available.

Let's break them down.

Why India Continues to Be a Global Hiring Hub

India has become one of the most attractive destinations for international hiring, and it's not due to cost.

Companies are building product, engineering, customer success, sales, design, finance, and operations teams here.

Some of the reasons include:

A large, highly skilled talent pool
Strong English proficiency
Mature remote work culture
Growing startup ecosystem
Significant overlap with US, UK, European, and APAC time zones For many companies, India is no longer just an outsourcing destination. It's where they're building long-term teams.

The question is no longer whether to hire in India.

It's how to do it correctly.

The Common Mistake: Assuming You Need a Local Company First

This is where many expansion plans slow down.

A founder decides to hire one software engineer.

Their legal team starts researching incorporation.

Finance begins estimating setup costs.

HR starts looking for payroll vendors.

Weeks turn into months.

Meanwhile, the candidate accepts another offer.

The reality is that incorporating a company makes sense when you're committed to establishing a long-term legal presence.

But if you're hiring one employee, or even your first small team, there are other options worth considering.

Your Hiring Options

Generally, companies expanding into India consider three approaches.

1. Set Up an Indian Entity:

This gives you complete control over hiring and operations.

It also comes with responsibilities such as:

Company registration
Local directors and compliance requirements
Payroll administration
Employment contracts
Tax registrations
Ongoing statutory filings
HR infrastructure

For businesses planning significant long-term investment in India, this can be the right choice.

For early-stage expansion, it may introduce unnecessary complexity.

2. Hire Independent Contractors:

Many companies begin here because it's simple.

But simplicity can be misleading.

If a contractor works:

full-time,
under your supervision,
with fixed working hours,
using company equipment,
and functions like an employee, there may be a risk that the relationship could be viewed as employment rather than genuine independent contracting, depending on the facts and applicable laws.

This is one reason companies should carefully assess whether a contractor arrangement fits the role.

3. Use an Employer of Record (EOR):

This is the option many startups discover after researching international hiring.

An Employer of Record acts as the legal employer in India while your company directs the employee's day-to-day work.

In practical terms:

You choose the candidate.
You manage their work and performance.
The EOR handles local employment, payroll, statutory compliance, and HR administration.

This allows companies to hire without establishing a local legal entity first.

When Does an EOR Make Sense?

From the conversations I've had with founders, an EOR is often a strong fit when a company wants to:

hire one to twenty employees
enter the Indian market quickly
validate a new market before incorporating
avoid managing local compliance internally
reduce administrative overhead
focus on product and growth instead of legal setup It's not the right answer for every business.

But it's an option more founders should evaluate before deciding to establish a subsidiary.

Compliance Is More Than Payroll

One misconception I often hear is:

"As long as we pay employees on time, we're compliant."

Payroll is only one part of the picture.

Hiring employees in India also involves considerations such as:

employment documentation
statutory deductions
leave policies
notice periods
employee benefits
tax-related obligations
ongoing employment compliance

These requirements can vary depending on factors such as the employee's location and the applicable regulations.

Ignoring them can create unnecessary operational and legal challenges.

Speed Matters More Than Ever

One pattern I've seen repeatedly is that the best candidates don't stay available for long.

If your hiring process requires months of legal preparation before extending an offer, you're competing at a disadvantage.

Companies expanding internationally increasingly want hiring processes measured in days or weeks, not months.

That's one reason EOR models have become more widely adopted for global expansion.

Think Beyond Your First Hire

Many founders focus on hiring employee number one.

A better question is:

"What happens when we hire employee number ten?"

The hiring model you choose should support growth.

Can you onboard quickly?

Can payroll scale?

Can compliance keep pace?

Can HR operations remain consistent?

Thinking about these questions early can prevent significant operational headaches later.

My Biggest Takeaway

After speaking with companies expanding into India, one thing has become clear.

Hiring internationally isn't just a legal exercise.

It's a business decision.

The right approach depends on your goals.

If you're building a long-term subsidiary with dozens or hundreds of employees, establishing a local entity may be the right investment.

Looking for unanswered questions? Drop them in the comments, and I'll do my best to answer them—or even write a follow-up article on the topic.

How we connected off-page content to actual revenue with a small Calendly to HubSpot webhook

Priyom Sarkar — Wed, 24 Jun 2026 17:42:56 +0000

For a long time our demo bookings showed up in the CRM with a source of (direct). Someone read a Reddit answer, clicked through, booked a call, and as far as our data was concerned, fell out of the sky. We knew the off-page content was working. We could not prove which piece.

This is the writeup of the small thing we built to fix that. It is not clever. That is the point. Attribution does not need to be clever; it needs to actually fire on every booking.

The problem in one sentence

Calendly bookings landed in HubSpot with no campaign data, because the UTM parameters on the landing URL were not being carried through into the contact record. So every off-page channel collapsed into (direct), and we could not tell a Reddit-sourced demo from a Medium-sourced one from a podcast-sourced one.

The shape of the fix

Three pieces.

A strict UTM convention so every off-domain link is tagged consistently before it ever ships.
A Calendly webhook that fires on invitee.created.
A small handler that reads the UTMs off the booking and writes them onto the HubSpot contact's self_reported_sourcestandard UTM properties.

1. The UTM convention

The unglamorous part that makes the rest work. Every link we publish off-domain follows the same pattern:

https://asanify.com/<path>/?utm_source=<platform>&utm_medium=<type>&utm_campaign=<topic>_<yyyymm>&utm_content=<placement>

utm_source is the platform token, lowercase, single word: reddit, quora, medium, devto, linkedin. Crucially it is never website or our own brand name, because those collapse straight back to direct. We enforce this with a regex check in CI before any draft is allowed to ship:

import re

def verify_utms(text: str) -> list[str]:
    fails = []
    urls = re.findall(
        r'https?://(?:[a-z0-9-]+\.)*(?:asanify\.com|calendly\.com)[^\s\)\]"]*',
        text,
    )
    for url in urls:
        for p in ("utm_source=", "utm_medium=", "utm_campaign="):
            if p not in url:
                fails.append(f"missing {p}: {url}")
        if re.search(r"utm_source=(website|na|none|test)\b", url, re.I):
            fails.append(f"bad source value: {url}")
    return fails

If verify_utms returns anything, the draft does not publish. A missing UTM is treated as a defect, not a nice-to-have. We standardized the whole thing on a single conventions doc that every content producer reads, which is the boring governance move that actually held the data clean. The corridor pages these links point at live on our EOR hub.

2. The Calendly webhook

Calendly fires a webhook on invitee.created. The payload includes tracking, which carries through the UTM parameters present on the scheduling link. That is the whole trick: Calendly already captures them; you just have to read them and forward them.

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.post("/marketing/calendly")
def calendly_hook():
    event = request.get_json(force=True)
    if event.get("event") != "invitee.created":
        return jsonify(ok=True), 200

    payload = event["payload"]
    email = payload["email"]
    tracking = payload.get("tracking", {}) or {}

    utms = {
        "utm_source":   tracking.get("utm_source"),
        "utm_medium":   tracking.get("utm_medium"),
        "utm_campaign": tracking.get("utm_campaign"),
        "utm_content":  tracking.get("utm_content"),
    }
    upsert_hubspot_contact(email, utms)
    return jsonify(ok=True), 200

3. Writing it onto the HubSpot contact

The handler upserts the contact and stamps the UTMs, plus a human-readable self_reported_source the sales team can filter on without learning UTM syntax.

import requests, os

HS = "https://api.hubapi.com/crm/v3/objects/contacts"
HEADERS = {"Authorization": f"Bearer {os.environ['HUBSPOT_TOKEN']}"}

def upsert_hubspot_contact(email: str, utms: dict):
    source = utms.get("utm_source") or "direct"
    props = {
        "email": email,
        "self_reported_source": source,
        "utm_source": source,
        "utm_medium": utms.get("utm_medium") or "",
        "utm_campaign": utms.get("utm_campaign") or "",
    }
    # idempotent upsert by email
    requests.post(
        f"{HS}?idempotencyKey={email}",
        json={"properties": props},
        headers=HEADERS,
        timeout=10,
    )

A couple of things we learned the hard way. Make the webhook idempotent, because Calendly will retry on a slow response and you do not want duplicate writes. Return 200 fast and do the slow CRM work behind a queue if your handler is heavy, otherwise the retries pile up. And log the raw tracking blob for a while, because the first week we found a chunk of links in the wild that predated the convention and arrived with no UTMs at all, which told us exactly which old content to go back and re-tag.

What it changed

Once this was live, the source breakdown on demo bookings stopped being a mystery. We could finally see which off-page channel was actually producing booked calls instead of just traffic, and we reallocated effort accordingly. The number that surprised us most was how much of our demand was coming from AI assistants citing our content, which only became visible because the source value was specific instead of a generic bucket.

We write more about how that AI-citation channel works for us on our EOR hub.
Nothing here is hard engineering.

The leverage is entirely in two things: a UTM convention you actually enforce, and a webhook that fires on every booking with no exceptions. Get those two right and your "where do demos come from" question has a real answer.

Modeling statutory payroll across 100+ countries without hardcoding a nightmare

Priyom Sarkar — Mon, 25 May 2026 12:47:46 +0000

If you have ever tried to compute net pay in more than one country, you know the trap. The first country goes fine. You write a function, it works, you ship it. The second country breaks half your assumptions. By the fifth you have a tangle of if country == "X" branches and a payroll engine nobody wants to touch.

This is a write-up of how we model statutory payroll rules across a large set of countries as data rather than code so that adding a corridor is a config change and not a deploy.

The core mistake: rules as code
The naive version looks like this, and it is fine until it is not.

def net_pay(gross, country):
    if country == "IN":
        pf = min(gross * 0.12, 1800)
        esi = gross * 0.0075 if gross <= 21000 else 0
        return gross - pf - esi
    elif country == "PH":
        sss = ...  # different brackets entirely
        philhealth = ...
        return gross - sss - philhealth
    # ... and so on, forever

Every new country is a code change, a review, a deploy, and a fresh chance to break the countries you already support. Statutory rates also change mid-year, so you are redeploying for what should be a data update. This does not scale past a handful of corridors.

The shift: rules as a declarative schema

The better model treats every statutory deduction or contribution as a typed rule record. A rule has a country, an effective date range, a base it applies to, a calculation method, and bounds. The engine stays generic and just interprets rules.

{
  "country": "IN",
  "component": "provident_fund_employee",
  "effective_from": "2024-04-01",
  "effective_to": null,
  "base": "basic_plus_da",
  "method": "percentage",
  "rate": 0.12,
  "cap_base": 15000,
  "rounding": "nearest_rupee"
}

The engine reads the applicable rules for a country and a pay date, sorts by dependency, and applies them. Adding a country becomes "write its rule records." Changing a rate mid-year becomes "close the old record with an effective_to, open a new one." No deploy.

def compute(gross, components, country, pay_date):
    rules = rule_store.applicable(country, pay_date)
    ctx = {"gross": gross, **components}
    results = {}
    for rule in topological_order(rules):
        base = resolve_base(rule["base"], ctx, results)
        results[rule["component"]] = apply_method(rule, base)
    return results

The three things that actually bite you

The schema is the easy part. Here is where real-world payroll fights back.

The "base" is never just gross. Provident fund in India applies to the basic plus dearness allowance, not the total gross. Some contributions apply to a capped base, some to uncapped. If your rule cannot express "what amount does this percentage apply to," you will hardcode exceptions within a week. The basefield has to be a first-class, composable concept, not an afterthought.
Effective dating is not optional. Statutory rates change, and they change on government timelines, not yours. You will run payroll for May with May's rates and re-run a correction for March with March's rates in the same week. Every rule needs a validity window, and the engine must select rules by pay date, never "latest."
Ordering and dependency. Some deductions are computed on the amount after another deduction. Tax often depends on the contributions already taken. Treat rules as a dependency graph and resolve in topological order. A flat loop over rules will silently compute tax on the wrong base in exactly the countries where it matters most.

Why we publish the human version too

The engine is internal, but the statutory logic behind it is exactly what a company hiring in a new country needs to understand before they commit. So the same rule data that drives the calculation also drives the country guides we publish. When the provident fund cap changes, the engine and the public page update from the same source, which means the documentation cannot drift away from the system.
If you want to see the human-readable side of this, the country pages on the global employer of record hub lay out the statutory components per country, and the India corridor in particular goes deep on the contribution mechanics.

Takeaways if you are building this

Model statutory rules as effective-dated data records, not branches in code.
Make "base of calculation" a first-class field. It is the thing that breaks first.
Select rules by pay date, never "most recent," or your corrections will be wrong.
Resolve dependencies in topological order so downstream deductions read the right base.

The payoff is that onboarding a new country stops being an engineering project and becomes a data task a compliance analyst can own. That is the difference between covering five countries and covering a hundred.

Hiring Engineers in South Korea Without Setting Up a Company There

Priyom Sarkar — Thu, 16 Apr 2026 02:30:00 +0000

South Korea came up in three separate client conversations last month. Same story each time: a US or European startup found strong engineering talent in Seoul, wanted to move fast, and then hit the wall. Legal said they'd need a Korean entity. Finance said that's $30,000 and six months. The candidate had two other offers.

I've been running an HR tech company for several years, and Korea is one of the markets where I see this pattern repeat constantly. So here's the practical breakdown for anyone evaluating it.

Why South Korea Is Worth the Effort

Seoul has one of the deepest engineering talent pools in Asia. Salaries are competitive on absolute terms. A senior software engineer runs $4,000 to $6,000 USD per month all-in, which is roughly 40-60% of a comparable US hire.

The country has near-universal broadband, one of the highest internet penetration rates globally, and a workforce that's culturally comfortable with remote collaboration (especially post-COVID).

The catch is compliance. Korean employment law is detailed, strictly enforced, and strongly favors the employee. If you're used to US at-will employment, Korea will surprise you.

Three Things That Trip Up Foreign Companies

1. The 52-hour workweek cap is a hard law.

Standard hours are 40/week. Overtime caps at 12 additional hours. Total: 52 hours maximum. This isn't a guideline. Violations carry criminal liability for the employer. If your engineering culture is "always on," you need to set explicit expectations for Korean hires, or you're exposed.

Source: Korea's Labor Standards Act (LSA), Articles 50-53. Enforced by the Ministry of Employment and Labor (MOEL).

2. The Retirement Allowance will catch you off guard.

After 1 year of continuous employment, every Korean employee is legally entitled to 30 days of average wage per year of service, paid as a lump sum when they leave. This is called 퇴직금 (toejik-geum). It cannot be waived by contract.

In practice, this adds roughly 8.3% of monthly salary as an ongoing accrual. If you don't accrue it monthly, you'll face a large surprise payment at termination.

Source: Korea's Worker Retirement Benefit Guarantee Act.

3. Termination requires justifiable cause.

This is not the US. You cannot terminate at will. Korean employees can appeal dismissals to the Labor Relations Commission, and reinstatement is a real remedy. Courts enforce this strictly.

For performance-based terminations, you need documented evidence, a formal improvement process, and multiple warnings. For redundancy, the bar is even higher: prove managerial urgency, demonstrate you exhausted alternatives, and consult with employees in advance.

Minimum notice: 30 days written, or 30 days' pay in lieu.

What It Actually Costs

Here's the real employer cost breakdown for a Korean hire earning KRW 6,000,000/month (~$4,500 USD):

Component	Rate / Amount
Gross salary	$4,500/month
National Pension (NPS)	4.5% ($203)
National Health Insurance (NHI)	3.545% ($160)
Employment Insurance (EI)	0.9-1.65% (~$50)
Workers' Compensation (WCI)	0.7-18.6% (tech is low end, ~$35)
Retirement Allowance accrual	~8.3% ($374)
Subtotal statutory	~$822/month

Total employer cost before any service fees: roughly $5,322/month. That's about 118% of gross salary.

If you use an Employer of Record (EOR) provider, add $400 to $1,500/month per employee for the service fee. So your realistic all-in cost is $5,700 to $6,800/month for a $4,500 base salary.

Sources: National Pension Service 2026 contribution schedule, National Health Insurance Service 2026 rates, Korea Workers' Compensation & Welfare Service (COMWEL).

EOR vs. Setting Up a Korean Entity

For most startups hiring 1-10 engineers in Korea, an EOR is the practical path. Quick comparison:

	EOR	Korean Entity (Yuhan Hoesa)
Time to first hire	2-5 days	3-6 months
Setup cost	$0	$15,000-$50,000
Ongoing admin	Handled by EOR	You need local accounting, tax filings, potentially a Korean director
Compliance risk	EOR's liability	Yours
Best for	1-15 employees, market testing	15+ employees, long-term strategic presence

The break-even point where entity setup becomes cheaper than EOR fees is usually around 15-20 employees. Below that, EOR wins on cost, speed, and flexibility.

Worth noting: winding down a Korean entity is also complex and expensive. If your Korea plans change, EOR gives you a cleaner exit.

Things to Verify Before Choosing an EOR Provider

If you go the EOR route, ask these questions before signing:

Do they handle year-end tax adjustment (연말정산)? This is a February obligation. Some EORs outsource it and charge separately.
Are Workers' Compensation and Employment Insurance included in the quoted fee, or billed as extras?
What's their actual termination support process? You want a team that has handled Korean Labor Relations Commission disputes, not a generic compliance desk.
Do they issue bilingual contracts (English + Korean)? Korean is the governing language for regulatory purposes, so you need both.
How do they handle the Retirement Allowance accrual? Good providers accrue from Day 1. Bad ones back-load it and leave you with a surprise bill.

My Experience

Disclosure: I'm the founder of Asanify, which offers EOR services in South Korea (among other countries). So factor that bias in.

What I can share from our client engagements: most first hires in Korea are fully onboarded within 48-72 hours. The bilingual contract generation and statutory registrations (NPS, NHI, EI, WCI) are the parts that slow things down if you try to do them yourself.

Asanify is rated #1 globally for ease of use on G2 in the EOR category. We handle the onboarding, payroll, and compliance digitally through WhatsApp and a web portal. If you're evaluating providers, also look at Deel and Remote, they have wider country coverage if you're hiring in 20+ markets simultaneously.

The honest answer is: for 1-5 engineers in Korea, any reputable EOR will save you significant time and money vs. entity setup. The differences between providers come down to pricing transparency, onboarding speed, and how well they handle Korean-specific obligations like the Retirement Allowance.

TL;DR

South Korea has excellent engineering talent at 40-60% of US costs
Compliance is strict: 52-hour workweek cap (criminal liability), mandatory Retirement Allowance (~8.3% monthly accrual), and termination requires justifiable cause
Total employer cost: roughly 130-135% of gross salary before EOR fees
For 1-15 hires, EOR beats entity setup on cost, speed, and flexibility
Break-even for entity: ~15-20 employees
Verify your EOR handles year-end tax, Workers' Comp, and Retirement Allowance accruals natively

If you have questions about hiring in Korea, happy to answer in the comments. I've seen enough edge cases at this point to have opinions on most of them.