Co-founder Agreements for Digital Health Platforms in New Zealand

If you are building a digital health platform with one or more co-founders, the legal risk usually starts long before your first customer contract. Founders often make three expensive mistakes early: they split shares on a handshake, leave ownership of code and clinical workflows unclear, and assume everyone has the same view on privacy, regulation, and decision-making. Those gaps can become serious problems when you raise money, sign with providers, or one founder leaves.

A co-founder agreement for digital health platform businesses helps set the rules while everyone is still aligned. In New Zealand, that matters even more where your product may involve health information, software development, claims about clinical outcomes, and relationships with clinicians, providers, or enterprise customers. The agreement is not just about who gets what. It is about who owns the platform, who can make key calls, what happens if someone stops contributing, and how disputes are handled before they damage the business.

This guide explains what a co-founder agreement should cover, the legal issues to check before you sign, and the common mistakes digital health founders make in New Zealand.

Overview

A well-drafted co-founder agreement sets expectations before pressure builds. For a digital health platform, it should deal with ordinary founder issues like equity and decision-making, but it also needs to address health-sector risks such as data handling, product claims, intellectual property ownership, and responsibilities for compliance.

The right document gives investors, customers, and future team members more confidence because the founders have already dealt with the hard questions.

• Who the founders are, what each person is contributing, and whether those contributions are cash, code, product design, clinical expertise, networks, or full-time labour
• How equity is split, whether vesting applies, and what happens if a founder leaves early or stops contributing
• Who owns source code, datasets, brand assets, clinical content, research inputs, and other intellectual property
• How major decisions are made, including spending, hiring, product pivots, fundraising, and entering regulated or high-risk partnerships
• What confidentiality rules apply, especially around health information, commercially sensitive material, and pre-launch product information
• What founders must do about privacy, marketing claims, security practices, and sector-specific legal obligations
• What restrictions apply if a founder competes, solicits customers or staff, or uses company assets for another venture
• How disputes are managed and how a founder can exit, sell shares, or be removed in defined circumstances

What Co-founder Agreement for Digital Health Platform Means For New Zealand Businesses

A co-founder agreement is the private rulebook between the people building the business together. In a New Zealand digital health company, it usually sits alongside your company constitution, share issue documents, employment or contractor agreements, and any later shareholders agreement.

At the earliest stage, founders often have different assumptions about what is “fair”. One person may think an idea deserves equal ownership. Another may think only current effort counts. A third may be contributing credibility through clinical relationships or regulatory know-how. The agreement forces those assumptions into writing before you rely on a verbal promise.

Why digital health platforms need more than a standard founder template

Digital health businesses have a few pressure points that ordinary software startups do not always face. The platform may process sensitive health information, connect practitioners and patients, support care decisions, or market itself using outcome-based claims. That means the founders need to be clear not only about ownership and shares, but also about compliance responsibilities.

For example, your agreement may need to record who is responsible for:

• product governance and approval of new features that affect patient or practitioner use
• privacy compliance and responses to data access requests or breaches
• clinical oversight, where the platform includes practitioner input, triage logic, or health content
• review of advertising and promotional claims under New Zealand fair trading rules
• security standards and vendor decisions for hosting, integrations, and third-party tools

If these responsibilities are left vague, founders can end up arguing about accountability after something goes wrong.

How it fits with your company records

Many founders incorporate a company through the Companies Office and issue shares soon after. That is a useful structural step, but registration alone does not answer the hard commercial questions between founders. The Companies Act framework and basic corporate records do not usually set out vesting, bad leaver outcomes, confidentiality obligations, or who owns the MVP code if it was written before incorporation.

This is where founders often get caught. A developer may have built the original platform through another entity. A clinician founder may have created decision trees, assessment questions, or treatment content before the company existed. A product founder may have registered domain names or purchased software subscriptions personally. Unless the agreement and related assignment documents deal with those issues clearly, the company may not actually own the assets investors think it owns.

What this means in practice

For New Zealand businesses, a co-founder agreement for digital health platform ventures should be practical enough to use when tension appears. It should answer real founder-moment questions, such as:

• Can one founder sign a pilot with a clinic or insurer without the others?
• What happens if the technical founder goes part-time after six months?
• Does the company own the code written before incorporation?
• Who can approve marketing statements about health outcomes or practitioner benefits?
• What happens if a clinician founder leaves and starts a similar service?
• Can a founder be forced to sell shares if they seriously breach privacy or confidentiality obligations?

If your agreement does not give a workable answer to those questions, it is probably too generic.

Legal Issues To Check Before You Sign

The key legal issues are ownership, control, compliance, and exit. A good agreement should reduce ambiguity on each of those points before you sign a contract, speak to investors, or accept the provider's standard terms with a major customer or health-sector partner.

1. Equity split and vesting

Equal ownership is common, but it is not automatically fair or sensible. The better approach is to match equity to expected contribution, risk, time commitment, and strategic importance, while also recognising that contributions can change quickly.

Vesting is especially useful where one founder is joining for future effort rather than delivering a completed asset on day one. Vesting means shares are earned over time, often with a cliff period. This reduces the risk of a departed founder keeping a large stake after only a short contribution.

You should also define leaver outcomes. For example:

• what counts as a good leaver and a bad leaver
• whether the company or other founders can buy back unvested or vested shares
• how the buyback price is set
• whether resignation, misconduct, incapacity, or failure to meet agreed milestones changes the outcome

These provisions often matter more than the initial percentage split.

2. Intellectual property ownership

The company should own the platform assets it depends on. For digital health startups, that can include much more than software code.

Make sure the agreement and any separate assignment documents deal with:

• source code, repositories, scripts, and technical architecture
• UX designs, wireframes, and brand assets
• clinical protocols, questionnaires, training materials, and written content
• datasets, labels, and structured information created for the platform
• algorithms, scoring logic, and product workflows
• domain names, social handles, and app store accounts

If a founder created any of these before the company existed, the company may need a specific assignment. If a founder is contributing through a separate service company, that also needs to be documented properly. Otherwise, ownership can remain with the founder or their entity rather than the startup.

3. Privacy and health information responsibilities

Where your platform collects, stores, or uses health information, privacy issues are not a side note. Founders should agree who is responsible for privacy governance, internal processes, and external communications if something goes wrong.

In New Zealand, health information is particularly sensitive. Your founder arrangements should align with your operational reality, including:

• who approves collection and use practices
• who handles access and correction requests
• who investigates incidents and notifiable privacy events
• what minimum security expectations apply
• whether a founder can use or access data outside agreed business purposes

A founder should never be left assuming they can use platform data for side projects, research, or future ventures unless the business has expressly agreed to that use and the relevant legal requirements are met.

4. Roles, authority, and reserved matters

Every founder should know what they control and what needs joint approval. This matters in digital health because one rushed commercial decision can create compliance or reputational problems.

Reserved matters are decisions that cannot be made unilaterally. These might include:

• issuing new shares
• taking on debt
• signing major customer, supplier, or channel contracts
• changing the product in a way that affects clinical use or patient risk
• outsourcing core development or data processing functions
• approving public statements about medical effectiveness or outcomes
• selling key intellectual property

This section should also cover day-to-day authority so the business can still move quickly.

5. Founder commitments and side projects

Many early-stage founders are part-time. That is not necessarily a problem, but it should be stated clearly. The agreement should record expected time commitments, key deliverables, and whether outside work is allowed.

Health-tech businesses are particularly exposed to conflict issues. A founder may consult to a hospital, own another software tool, or advise a clinic group that could become a customer or competitor. The agreement should require disclosure of conflicts and explain how they are handled.

It should also cover restraints carefully. Non-compete and non-solicit provisions need to be drafted reasonably to improve their enforceability. Overreach can make them less useful.

6. Confidentiality and sensitive know-how

Confidentiality clauses matter from day one, especially before you sign NDAs with partners or begin customer pilots. Your co-founder agreement should make clear that confidential information includes technical architecture, pricing, business plans, customer lists, investor discussions, and product material that could reveal health workflows or service design.

Where a clinician founder brings practitioner relationships or care-model know-how, founders should be realistic about what is confidential, what is personal expertise, and what the company can continue using if that founder leaves. Careful contract drafting around that boundary can prevent a later fight.

7. Dispute resolution and exit mechanics

The main goal is not to predict every dispute. It is to stop a disagreement from paralysing the company.

Your agreement should address:

• what happens if founders deadlock on a major decision
• whether mediation is required before formal steps are taken
• who can trigger a sale process or buyout discussion
• when a founder can transfer shares and who gets first refusal
• what happens on death, long-term incapacity, or serious misconduct

A startup can survive a disagreement. It is much harder to survive silence about how a disagreement gets resolved.

Common Mistakes With Co-founder Agreement for Digital Health Platform

The most common mistake is using a generic startup document that ignores the health context. That usually leaves the founders exposed on data, clinical content, and product responsibility even if the equity clauses look fine.

Assuming the company owns everything automatically

It does not. Incorporating a company and issuing shares does not transfer pre-existing intellectual property into the business. If code, content, workflows, or datasets were created before incorporation, or through another entity, ownership needs to be assigned properly.

This issue often appears during due diligence. Investors or buyers ask for proof that the company owns the platform, and the paperwork is missing or inconsistent.

Leaving privacy and compliance outside the founder discussion

Some founders treat privacy, security, and regulatory issues as matters for later customer contracts. That is too late. In digital health, privacy and product governance decisions are often made by founders long before formal policies or a privacy notice are drafted.

If one founder is pushing rapid growth and another assumes stricter controls apply, the business can end up making promises it cannot safely keep.

Using equal shares to avoid a hard conversation

An even split can work, but it should be a considered decision, not a shortcut. Founders often avoid discussing changing workloads, future dilution, vesting, and exit consequences because the conversation feels uncomfortable early on.

The result is usually worse later, especially if one founder becomes full-time, one remains an adviser in practice, and one controls the core product assets.

Ignoring founder employment or contractor status

A co-founder agreement is not always enough on its own. If founders are also working in the business day to day, they may need separate employment agreements or contractor agreements. Those documents help cover IP created during service, confidentiality obligations, remuneration, and termination rights.

This matters before you spend money on setup or commit to salaries because the legal position can become unclear if work starts informally.

Being too vague on who can bind the business

A digital health startup may deal with clinicians, software vendors, researchers, and enterprise customers early. If the agreement does not say who can sign what, one founder may commit the company to pricing, service levels, integration work, or data-use terms that the others never approved.

Before you sign, authority limits should be clear in writing.

Forgetting future fundraising

Investors often expect clean cap table logic, vesting, clear IP ownership, and workable transfer rules. If your founder arrangements are overly informal, fundraising can slow down while everyone renegotiates under pressure.

The best time to fix this is when relationships are good, not when a founders term sheet is on the table.

FAQs

Is a co-founder agreement legally binding in New Zealand?

Yes, if it is drafted and signed properly, a co-founder agreement can be legally binding. It should be consistent with your company records and any later shareholders agreement.

Do digital health founders need anything besides a co-founder agreement?

Usually, yes. Many businesses also need share issue documents, IP assignments, confidentiality terms, employment or contractor agreements, privacy documents, and customer or supplier contracts.

Should founder shares vest?

Often, yes, especially where equity is being granted for future effort over time. Vesting can protect the business if a founder leaves early or does not deliver what was agreed.

Who should own the platform IP?

In most cases, the company should own the key intellectual property used to operate and grow the platform. That usually requires written assignments if assets were created before incorporation or through another entity.

What if one founder brings clinical expertise rather than code or cash?

That contribution can still be valuable, but the agreement should describe it clearly, including expected involvement, deliverables, and whether equity is tied to ongoing participation, milestones, or vesting.

Key Takeaways

• A co-founder agreement for digital health platform businesses should do more than split equity. It should cover ownership, control, privacy responsibilities, compliance decision-making, and founder exits.
• New Zealand digital health startups need clear written terms on intellectual property, especially where code, content, workflows, or datasets were created before incorporation.
• Vesting, leaver provisions, and transfer rules can prevent major disputes if a founder reduces their involvement or leaves early.
• Reserved matters and authority limits help stop one founder from binding the business to risky contracts, product changes, or public claims without approval.
• Privacy, confidentiality, conflicts of interest, and side-project rules should be addressed early because health-sector businesses handle sensitive information and often involve overlapping professional relationships.
• Founder arrangements usually work best when paired with related documents such as IP assignments, share documents, and employment or contractor agreements.

If you want help with equity vesting, intellectual property assignments, privacy and confidentiality terms, or founder exit provisions, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.