The Global Hire That Nearly Sank a Startup

Every founder remembers their first hire abroad. Fewer like to talk about how close it came to ending them. What follows is a composite, but every beat of it plays out for real, and it almost always starts the same way: with a smart decision that quietly turns into an expensive one.

The smart decision

Running a startup today means being global almost by default. A two-person startup needs an engineer and cannot stretch to a Bay Area salary. They find someone brilliant in Manila, agree a monthly rate, and bring them on as a contractor. It is fast, it is cheap, and it works. Within a year the developer is the backbone of the product: working the startup’s hours, on the startup’s systems, to the startup’s roadmap, and for no one else.

Nobody in this story is careless. A contractor agreement is the obvious choice for a company with no foreign entity, no HR person, and no appetite for paperwork in a country the founders have never visited. They download a template, swap in the names, and send the first payment through a transfer app. The work is good. The invoices arrive on time. Nobody thinks about the agreement again.

What changes is the relationship, and it changes slowly. The developer starts with one feature. Then a second. Then they’re in the team chat, then in the Monday standup, then holding the on-call phone over a long weekend. A year in, they’re reviewing the next hire’s code and sitting in on product decisions. On paper, still a contractor. In practice, the startup’s first engineer.

The term sheet that exposed it

Then a seed investor wants in, and with the money comes diligence. That is where it comes apart. Philippine law does not let you decide who is a contractor by typing it into an agreement. Its courts apply a four-fold test, who hired the person, who pays them, who can dismiss them, and who controls how the work gets done, and the last one, control, is the decisive factor. By that test, the startup’s most important person is an employee, and has been for most of the year. Underneath it sits a harder rule still: a contractor doing core-business work who passes twelve months and one day of continuous service becomes a regular employee automatically, by operation of law, with no tribunal finding required. The developer had crossed that line months earlier.

The bill that follows is not small. As an employee, the developer was owed the employer share of three statutory schemes, social security (SSS), PhilHealth, and the Pag-IBIG housing fund, plus a thirteenth-month payment mandated by law, all backdated to day one. Together those land at roughly 22 percent of salary that was never paid, now due with late-remittance surcharges and interest stacked on each missed period. And because the contractor agreement never cleanly assigned intellectual property, the company’s core code was on uncertain footing at the exact moment an investor was inspecting it.

None of this surfaces on its own. It surfaces because the diligence request list, a spreadsheet that runs to dozens of rows, asks for every agreement with every person who has written code for the company, and for proof that the company owns what they wrote. It’s a routine question. Here, the answer isn’t.

The IP gap is the part that frightens investors most. Philippine copyright law generally leaves commissioned work with the person who created it unless the contract says otherwise, and a template agreement pulled off the internet rarely says it clearly enough. Someone investing in a software company is buying the software. If the founders can’t show a clean chain of ownership for the core codebase, the lawyers won’t let the money move until they can.

The signs were never hidden

  • Fixed hours set by the company rather than the worker.
  • Company email, tools, and systems as the daily workspace.
  • Standups, reviews, and a manager the person reports to.
  • Working only for this one client, month after month.
  • Following the company’s roadmap and quality bar, not delivering a self-contained project.

Any one of these points toward employment. The developer ticked all five, which is why no contract clause saying “independent contractor” would have survived a second look. For a real independent contractor, a contractor management platform keeps the paperwork and payments clean; this relationship was never that.

There’s a simple gut check here. Imagine the developer announced they were taking on a second client next month, setting their own hours, and handing the work to a colleague for a week. If the founders’ honest reaction is that none of that would be acceptable, they don’t have a contractor. They have an employee they never registered.

The scramble

This is where it gets costly. DOLE, the labor department, can impose fines of up to 500,000 pesos per violation, and misclassification stacks liabilities across several agencies at once. The bigger threat is security of tenure: a regular employee in the Philippines cannot simply be dropped, so a contractor arrangement that ends can be ruled an illegal dismissal, which puts back wages and even reinstatement on the table. The round stalls while lawyers work through it, the cleanup runs past a year of the developer’s pay, and for a few weeks the company hangs on whether the mess can be cleared before the term sheet expires. The maddening part is the arithmetic. Employing the developer properly from the start, through an employer of record in the Philippines, would have added that 22 percent and a provider fee, and nothing else. No backdated penalties. No IP scramble. No stalled round.

The founders learn a quieter lesson in those weeks too: the developer has options. A worker who discovers they’ve been owed benefits for a year has every reason to ask for them, and a regular employee in a dispute can take it to the National Labor Relations Commission. In this telling the relationship survives, mostly because the founders come clean early and offer to make it right. Plenty of founders aren’t that lucky, or that candid.

What to check before month twelve

If you have someone abroad on a contractor agreement right now, a short audit takes an afternoon and can save a funding round. Start with the calendar. Count the months of continuous service for everyone doing work at the center of your business, and flag anyone past nine months. Converting someone properly takes longer than most founders expect.

Then look at control, and be honest about it. Who sets their hours? Whose tools do they use? Who do they report to, and could they turn down a task without consequences? If every answer points back at you, the word on the contract won’t help.

Fix the IP next, whatever else you decide. A short confirmatory assignment, signed now and covering work already delivered, closes the gap investors care about most. It costs little, and most contractors sign it without fuss once you explain why.

Finally, choose the structure that matches how the work actually happens. A genuine freelancer on discrete projects can stay a contractor. Someone who works like an employee should be employed, either through your own local entity, which only pays off once you have a real team in that country, or through an employer of record that runs payroll, statutory contributions, and local contracts on your behalf.

The part worth remembering

The takeaway is not “do not hire abroad.” Reaching for global talent is one of the best moves a small company can make, and often part of the shift from growing to scaling. The takeaway is narrower and more useful: the label on a contract counts for little against how the work is really done, and in the Philippines the clock runs out at twelve months whether you are watching it or not.

Wherever the hire sits, whether in Manila or the engineering hubs of Taiwan, the local rules decide the relationship, not your paperwork, and an hour spent learning them before the first hire is the cheapest insurance a founder will ever buy.

Founders who ship physical products learn the same lesson at the border, where customs rules, not the invoice, decide what clears. It’s why teams moving goods internationally lean on freight forwarding management software to keep their documents in line with each country’s regulations. Hiring across borders deserves at least that much attention.

Most near-death startup stories are about running out of money or losing a co-founder. The quiet ones, the kind nobody puts in a pitch deck, are about a classification that was wrong for a year before anyone looked. This one is entirely avoidable, and the fix is boring, which is exactly what you want from the part of your company that employs people.