You've probably had this moment already. A customer needs faster support, the product backlog is getting silly, and your calendar looks like a game of Tetris gone wrong. So you think, right, time to hire.
That's when founder brain collides with employer reality. You're not just choosing a person. You're stepping into New Zealand employment law, payroll rules, leave entitlements, contractor risk, and the odd clause that looks harmless until it absolutely isn't.
For tech founders, that jump feels weirdly bigger than raising a round. Code can be patched. A broken employment process tends to come back with paperwork, stress, and a very human mess attached to it. And because New Zealand's employment rate was 66.7% in the first quarter of 2026, the labour market you're hiring into is active and established, not some loose free-for-all (Trading Economics on NZ employment rate). That matters. People have options, and the law assumes employers should know the basics before they start building teams.
The first hire usually starts with excitement and mild panic. Maybe you've just signed a big client. Maybe your SaaS product has enough traction that support tickets now arrive while you're asleep. You tell yourself you just need “a bit of help”.
Then the practical questions land. Employee or contractor? Full-time or part-time? What goes in the contract? What checks are fair? What can you ask, and what should you leave well alone?
A lot of founders treat the first hire like a bigger freelance gig. That's understandable. It's also where things go sideways. If your new developer is working to your schedule, using your systems, and becoming part of the way you deliver work, then you're not just adding capacity. You're building an employment relationship, with all the obligations that come with it.
Before you make an offer, get organised on role scope, reporting lines, and vetting. A sloppy hiring process creates downstream problems fast. One vague promise in an interview can turn into a real dispute once someone's on payroll.
If you want a sensible checklist for the screening side, Digital Footprint Check's hiring guide is useful for thinking through references, background checks, and process hygiene without turning your startup into a corporate maze.
Practical rule: Hire slower than your stress level wants, and document faster than your optimism thinks you need to.
The company structure matters too. If you're still figuring out whether you should be operating personally or through a company, sort that out before the team grows. The legal and admin knock-on effects are real, especially once wages and tax enter the chat. This breakdown of sole trader vs company in NZ is a handy starting point.
Founders often talk about culture as if it appears later, after ten staff and a values workshop. It doesn't. It starts with your first job ad, your first contract, and whether your first team member feels clear or confused.
That's the thread running through good NZ employment law practice. It's not only compliance. It's signal. Clear terms tell people you're serious. Fair process tells them you're safe to work with. And that helps you hire better people.
This is one of the biggest founder traps in NZ employment law. You call someone a contractor, send them a neat agreement from DocuSign, and think the issue is sorted.
It isn't.
The label helps only if the actual relationship matches it. The law looks at substance. Not your preference, not the invoice template, not the fact that “everyone in startups does it this way”.
A lot of tech businesses use contractors for perfectly sensible reasons. You might need a React Native specialist for a short build, a designer for a brand refresh, or a fractional growth lead. That can be fine. But if the person behaves like staff in every meaningful way, the paperwork won't save you.
To make the distinction easier to grasp, this visual captures the basic split founders need to think about first.
The major shift is the 2026 gateway test for contractor classification. If a worker meets specific criteria in their written agreement, they are automatically a contractor. That change has altered the risk picture for startups in a big way, especially app-based businesses and tech companies that rely on flexible labour models (Ogletree on New Zealand's employment relations changes).
The criteria matter. The written contract needs to line up with genuine independence. The worker must have freedom to work for others. There must be no availability requirement. They need the ability to subcontract. They can't be terminated for refusing tasks. And they must have the opportunity to get independent advice.
That sounds tidy on paper. In practice, plenty of founder arrangements fail the smell test.
Let's make it less legal and more real.
| Situation | More likely contractor | More likely employee |
|---|---|---|
| Short project build | A specialist builds one feature, sets their own hours, works for other clients | A dev works only for you and joins sprint planning every week |
| Control | They decide how the work gets done | You direct the work day by day |
| Substitution | They can send another qualified person | You hired that specific person and no substitute is acceptable |
| Commitment | Task-based, independent delivery | Ongoing role inside your operating rhythm |
A freelance penetration tester who comes in for a security review is one thing. Your “contractor” customer success lead who works every weekday, reports into your head of product, and uses your Slack, Notion, Linear, and Google Workspace like everyone else? That's a different story.
If someone looks like part of the machine room, there's a fair chance the law will treat them that way too.
Three mistakes show up again and again:
And there's another wrinkle from the recent reforms. For high-income roles, some dismissal protections have shifted, but that does not mean every senior person should be pushed into contractor status. Different issue, different risk. Mixing those up is how people get into trouble.
Before you send an offer, ask these questions:
Contractors can be the right move. Employees can be the right move. The bad move is pretending the law bends to your spreadsheet.
You make an offer on Tuesday, they accept on Slack, and by Monday they are in your codebase, in your customer tools, and asking whether they can work from Queenstown for six weeks. If the agreement is still “coming soon”, you are already behind.
In New Zealand, the employment agreement is not admin. It is the document that sets the rules before the first awkward conversation about scope, hours, pay, IP, remote work, or notice. For tech founders heading into the 2025 to 2026 law changes, that matters even more. Hiring risk is shifting. Pay transparency is shifting. The old habit of grabbing a template from a US startup blog was shaky before. Now it is a liability.
Founders often treat the contract as paperwork to finish after the candidate says yes. That is backwards.
The signed agreement needs to be in place before work starts, especially if you want clauses that depend on proper process, such as a trial period. If your new hire starts first and signs later, you have thrown away an advantage you cannot easily get back. I have seen this happen in fast-moving teams where everyone is busy and “we'll sort docs this week” sounds harmless. It is not harmless when the first performance issue shows up in month one.
A good agreement also saves time later. It answers the boring questions once so your team is not improvising policy in DMs.
If a founder sends me an agreement to review, I look for plain language first. Not clever drafting. Clarity.
The agreement should state:
Short contracts can still be good contracts. Vague contracts are the expensive ones.
Two updates matter straight away for startups.
First, trial periods are set to become available again for all employers from 22 December 2025. That gives early-stage companies more room to manage hiring risk, but only if the clause is drafted properly and agreed before employment begins. A half-baked reference in an offer email will not save you.
Second, pay secrecy clauses became unenforceable in 2025. Employees can discuss their pay. If your contract still says they cannot, that clause is outdated. If a manager punishes someone for talking about remuneration, you may have a much bigger problem than a bad template.
That combination is where founders need to be sharp in 2025 and 2026. You can use trial periods to reduce hiring risk. You cannot use confidentiality language to shut down lawful pay discussions. One change gives you an option. The other removes one.
Founder note: If a clause only works when nobody challenges it, rewrite the clause.
Startup reality carries weight. A clean contract on paper does not help much if your actual setup says something else.
If the agreement says the role is office-based but the person is permanently remote, fix the mismatch. If the contract says standard hours but the team expects after-hours incident response, write that properly. If the role includes handling customer data in offshore tools, your confidentiality and systems clauses should reflect that. This plain-English guide to GDPR and New Zealand privacy issues for digital businesses is useful if your team works across borders or inside a stack full of overseas SaaS tools.
I would also check that the agreement lines up with the rest of your documents. Offer letter, policies, onboarding checklist, equity docs, contractor paperwork for mixed teams, and payroll setup should all point in the same direction. Founders get into trouble when each document was written by a different person at a different stage of the company.
Use an NZ agreement drafted for NZ law. Update it for the current reforms. Keep it readable. Attach the policies that matter. Make sure the person signing on behalf of the company is the right one. Then store the signed copy somewhere your ops lead can find it six months later.
What fails is familiar. Overseas template. Undefined role. Messy IP wording. Remote work handled by verbal promises. Trial period clause added too late. Salary confidentiality language copied from old precedent docs. None of that feels urgent when hiring is going well. It gets expensive fast once the relationship comes under pressure.
It usually hits on an ordinary Tuesday. A developer asks why their leave balance looks wrong. Someone else is unsure whether a public holiday should have been paid because they worked odd hours the week before. Payroll is due in two hours, and suddenly a back-office task is eating founder time.
That is the core day-to-day job under NZ employment law. Once the hire is made, the risk shifts to repeated decisions made under pressure.
The baseline rules are straightforward enough. As noted earlier, the minimum wage increased from 1 April 2025. Employees also get paid annual leave after 12 months of continuous service. The hard part is not knowing that. The hard part is setting up payroll, timesheets, and leave tracking so the rule gets applied properly every single time.
I have seen tidy companies on basic tools and messy companies on expensive ones. Xero, MYOB, or a payroll provider can all work. None of them save you from bad inputs.
Founders should be checking a few things with boring consistency. Are hours recorded accurately for people whose time varies? Are leave settings correct from day one? Are public holidays being treated properly for part-time staff and anyone with an irregular pattern? Can someone in finance or ops explain the numbers without guessing?
That last point matters. If an employee queries a payslip and the answer is vague, trust drops fast.
A workable rhythm looks like this:
The 2025 to 2026 shift for tech startups is less about a brand-new payroll rule and more about scrutiny. Contractor status, flexible work patterns, offshore teams, and variable hours all create more edge cases. If your hiring model has changed, your payroll setup probably needs attention too.
Leave sits on the balance sheet and in your delivery plan. Ignore it long enough and it becomes both a people problem and a finance problem.
A growing startup can carry a surprising amount of leave liability without noticing. Then summer hits, two engineers want time off, one team lead wants to cash up a week, and payroll costs spike while output drops. None of that is unusual. The mistake is treating leave as a culture topic instead of an operational one.
Some entitlements also call for maturity from the business, not just box-ticking. Employees affected by domestic violence have specific leave and flexible work protections under New Zealand law. Peninsula New Zealand's employment law guide gives a useful overview of those obligations and other day-to-day employer duties.
People remember how the company behaved when life got hard.
A few problems come up again and again in early-stage teams:
One niche point is still worth knowing. Partial strikes have specific rules around deductions, and improvising here is risky. It does not come up often in startup life, but if it does, get advice before touching pay.
The founder move here is simple. Build a pay and leave process that still works when the company is busy, stressed, or short-handed. That is what keeps ordinary admin from turning into legal cost.
No founder enjoys this part. Hiring feels full of possibility. Exits feel heavy, awkward, and personal. Still, if you run a company long enough, you'll deal with underperformance, conduct issues, role changes, or a relationship that just doesn't recover.
The instinct is often speed. Rip the plaster off. Move on. That instinct is exactly what creates grievance risk.
A fair process is not theatre. It is your defence, your evidence, and often your last chance to avoid turning a bad employment situation into a worse legal one.
Founders sometimes think certainty is enough. “We know they're not performing.” “Everyone can see the issue.” “It's obvious.” Maybe. But employment disputes usually turn on process as much as substance.
A fair process usually includes:
If you skip one of those steps, you weaken your position. If you skip two, you're asking for trouble.
One major change raised the stakes dramatically. The Crimes (Theft by Employer) Amendment Act 2025 makes intentional wage theft a criminal offence, and serious cases involving over NZD 1,000 of unpaid wages can lead to up to seven years' imprisonment (Buddle Findlay on wage theft and employment law changes).
That is a genuine line in the sand. Deliberately withholding wages or entitlements is no longer just a civil headache. It can become a criminal matter. The law focuses on intentional non-payment without reasonable excuse, not honest admin mistakes. But founders should not take comfort in that distinction if their payroll habits are sloppy and undocumented.
Recent amendments also changed how personal grievance remedies can be reduced where the employee contributed to their own dismissal. In some cases, remedies can be reduced by up to the full amount. That doesn't let employers run roughshod over process. It means contribution matters more than it used to.
There's also confusion around high-income employees. Some founders hear about the threshold affecting unjustified dismissal claims and assume senior staff lose all grievance rights. They don't. Different claims can still remain available. That nuance matters when you're hiring senior engineers, product leads, or executives on hefty packages.
A messy exit is rarely caused by one bad meeting. It usually starts weeks earlier, when no one writes things down and everyone hopes the issue will sort itself out.
Good founders don't treat termination like a script from an American TV show. They treat it like a serious business process involving a real person.
A few habits help more than people think:
If you need a practical process map to sanity-check your approach, HR's guide to employee termination is useful as a plain operational reference. It's not NZ-specific legal advice, but it does help founders avoid the classic “we improvised the exit” blunder.
The first time a founder gets caught here is usually mundane. Someone tweaks their back working from a kitchen bench for three months. Payroll has been running off a spreadsheet nobody trusts. A great offshore candidate is ready to start, then somebody finally asks whether they can lawfully work in New Zealand. None of that feels like startup drama until it lands on your desk at once.
That is the job once you employ people. You are not just hiring talent. You are running a workplace, a payroll function, and in some cases a visa risk process.
Founders in software sometimes underweight health and safety because nobody is climbing scaffolding. That is a mistake. Your risks are different, not lower by default.
Remote work is the obvious example. If someone works from home, you still need a sensible process for workstation setup, incident reporting, work hours, and flagging problems early. Mental harm and fatigue also belong in the conversation, especially in startups where release pressure can implicitly become the norm.
Keep it practical. Ask what hazards exist in your actual business, document the basics, and make sure managers know what to do when an issue is raised. A lightweight system that people use beats a polished policy nobody reads.
Payroll errors have a way of exposing every weak spot in the company. If leave is set up badly, deductions are wrong, or records are patchy, staff notice fast and Inland Revenue can too.
Good founders treat payroll as infrastructure. Use a proper system. Reconcile it. Make sure someone owns it. If your accountant, ops lead, and founder all assume somebody else is checking the details, nobody is checking the details.
This matters more with the 2025 to 2026 changes in play. Startups are reviewing pay transparency, contractor settings, and higher-scrutiny worker classifications at the same time. If your records are messy, fixing one issue often reveals two more.
Hiring across borders can be smart. It can also create false confidence.
A Slack profile that says "based in Auckland soon" is not proof of work rights. A contractor invoice from overseas does not automatically remove New Zealand employment risk. A founder intro is not immigration due diligence. Check what visa the person holds, what work it allows, where they will perform the work, and whether the role setup matches the legal reality.
For founders weighing remote and relocation models, this guide to the digital nomad visa discussion in New Zealand is a useful starting point. It helps frame the difference between someone visiting, someone working remotely, and someone you are effectively employing here.
One more practical point. Immigration, tax, and employment status often overlap. If the arrangement later falls over and you end up in an exit process, the paperwork gaps usually show up there too. That is one reason I tell founders to read HR's guide to employee termination even before they think they need it. Clean onboarding and clean records make the hard conversations far less messy.
Monday morning, your first engineer starts. By lunch, they have a laptop, Slack access, and a Jira login. By Friday, you realise nobody checked the signed agreement, payroll settings, KiwiSaver setup, or whether the contractor label in your old template still makes sense under the tougher 2025 to 2026 scrutiny. That is how small admin gaps turn into expensive cleanup.
Founders do not need a perfect HR stack on day one. They do need a repeatable process that catches the basics every time.
Use this as the minimum standard before and after each hire:
One practical point from experience. The highest-risk hires are often the ones that feel the easiest. A former colleague helping part-time. A founder's referral working remotely from another country. A "contractor for now" who joins standups every day and works only for you. Those are the setups that need the closest review.
Do not run employment compliance off random blog posts and stale Google Docs. Keep three official sources close at hand:
If you are hiring beyond New Zealand, navigating international employment law is useful background reading. Cross-border hiring changes the risk profile fast, and founders usually feel that only after the relationship gets messy.
What works is disciplined admin. Correct status. Current agreements. Accurate pay. Clean records. Fair process.
What fails is startup optimism posing as a system. "We'll sort it after the raise" is not a process. "They're basically a contractor" is not a legal test. "We used the same template last time" is not a review.
The founders who handle this well treat compliance like product ops. Set the process once. Run it the same way every hire. Review it when the law shifts, especially with the 2025 to 2026 changes now reshaping hiring, contractor risk, and compensation settings for NZ startups.
If you're building or scaling a tech company in New Zealand or Australia, NZ Apps is worth a look. It covers the regional app and SaaS market in a way founders can use, from practical guides to company roundups and market context that helps when you're hiring, expanding, or trying to get your name in front of the right local audience.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options