Non-solicitation Clauses for New Zealand Asset Management Software Businesses

If you run an asset management software business in New Zealand, a non-solicitation clause can look harmless until it starts blocking growth, hiring plans, or client retention.

Founders often make the same mistakes: they accept a supplier or customer contract without checking who counts as a protected client, they agree to restrictions that run far too long, or they rely on a verbal assurance that the clause will only be used “reasonably”. That is where trouble starts.

A non-solicitation clause for asset management software business arrangements can affect customer handovers, channel partnerships, reseller deals, outsourced development, senior employee exits, and M&A activity. The wording matters because these businesses often deal with long sales cycles, sensitive client data, close account management, and specialist staff who know exactly how the platform works.

This guide explains what these clauses usually do, what New Zealand businesses should check before signing, where founders commonly get caught, and how to assess whether a restraint is likely to be workable in practice.

Overview

A non-solicitation clause is a contract term that restricts one party from approaching certain customers, staff, investors, suppliers, or other commercial contacts for a set period after a relationship ends. In an asset management software context, it is usually aimed at protecting client accounts, recurring revenue, confidential information, and hard-won business relationships.

In New Zealand, these clauses are not automatically enforceable just because they appear in a contract. The clause still needs to be drafted carefully, tied to a legitimate business interest, and reasonable in scope, duration, and the people or businesses it covers.

• Who is protected, such as current customers, former customers, prospects, staff, contractors, referral partners, or investors.
• What conduct is actually restricted, such as direct approaches, indirect approaches, responding to inbound enquiries, hiring attempts, or using intermediaries.
• How long the restriction lasts, and whether the period is realistically connected to your sales cycle and customer relationship length.
• Where the clause applies, especially if your software is sold across New Zealand and offshore.
• Whether the clause sits alongside confidentiality, intellectual property, privacy, and non-compete terms that overlap or conflict.
• How the clause defines solicitation, because vague drafting often causes the dispute.
• What exceptions apply, such as general advertising, existing relationships, or mandatory legal disclosures.

What Non-solicitation Clause for Asset Management Software Business Means For New Zealand Businesses

For New Zealand software businesses, a non-solicitation clause is mainly about protecting commercial relationships without overreaching. The key question is whether the clause fairly protects a genuine business interest, rather than simply trying to stop competition altogether.

Asset management software businesses often sit closer to their clients than ordinary SaaS providers. Teams may help with implementation, data migration, workflow configuration, compliance reporting, API integrations, and ongoing support. That closeness creates more opportunity for a departing employee, reseller, implementation partner, or contractor to move key accounts or staff.

Why these clauses come up so often in this sector

These businesses usually invest heavily in trust and specialised knowledge. A client may stay because your account lead understands its portfolio structures, permissions, reporting needs, and integration stack. If that person leaves and immediately targets the same client base, the business risk is obvious.

That is why non-solicitation clauses commonly appear in:

• employment agreements for senior sales, implementation, and customer success staff
• contractor agreements with developers, consultants, and implementation specialists
• reseller and referral partner agreements
• software licence and master services agreements where the provider and customer exchange personnel or access to end users
• share sale and business sale documents
• founder exit and shareholder arrangements

What the clause may cover

A clause can target more than customer poaching. In practice, founders often see three separate restraint ideas bundled together and should read them as separate risks.

• Client non-solicitation, which stops you or the other party from trying to win over named or defined customers.
• Staff non-solicitation, which restricts poaching employees or contractors.
• Supplier or partner non-solicitation, which can affect referral channels, integration partners, white-label arrangements, and subcontractors.

Those restrictions can matter even if you never planned to target anyone. A clause drafted too broadly might capture a passive LinkedIn message, a general industry event conversation, or a pitch to a prospect who was only loosely connected to the other party.

How New Zealand law usually approaches restraint clauses

New Zealand courts generally look at restraint clauses, including non-solicitation clauses, with caution. A business cannot simply prevent another party from competing because it wants to reduce commercial pressure. The clause usually needs to protect something legitimate, such as confidential information, customer relationships, or workforce stability.

The main issues are reasonableness and scope. A restraint that is too wide may be difficult to enforce. That can happen if it lasts too long, covers too many people, extends beyond the real commercial relationship, or goes further than necessary to protect the business.

For example, a 24 month ban on soliciting any person who was ever a prospect in your CRM may be much harder to justify than a 6 or 12 month restriction limited to active customers that a departing account manager actually dealt with in the past year.

Why this is different for asset management software businesses

The sector has a few features that make careful drafting more important. Sales cycles are often long, contracts can be sticky, and implementation work creates close operational access. Software providers may also handle or host sensitive data, even where the client remains the data controller in practice.

That means a restraint clause is rarely just about sales. It may connect closely with:

• confidential information and source code access
• client data and Privacy Act 2020 obligations
• service levels and transition support at the end of the contract
• ownership of custom configurations, templates, and integration work
• post-termination obligations for return or deletion of information

Before you sign a contract, look at the whole package. A narrow confidentiality clause with an overly broad non-solicitation clause can still create a serious commercial problem.

Legal Issues To Check Before You Sign

Before you accept the provider's standard terms, pin down exactly what business interest the clause is trying to protect and whether the drafting matches that purpose. If the clause goes further than needed, it may create unnecessary risk now and a costly dispute later.

Who counts as a protected customer or contact?

This is where founders often get caught. Some contracts define protected persons so broadly that they include anyone who ever received a proposal, attended a demo, was introduced in a meeting, or appeared in a shared pipeline.

A better clause usually narrows the group by reference to objective criteria, such as:

• customers receiving services at the termination date
• customers the restricted party materially dealt with during a stated period
• prospects in active negotiations, clearly defined
• employees or contractors engaged in the business at termination

If the clause uses broad labels like “clients, customers, leads, contacts, or associated entities”, ask for tighter written terms before you sign.

What exactly is “solicitation”?

The word sounds simple, but disputes often turn on this definition. Direct poaching is the obvious example, but contracts can also try to catch indirect conduct.

Check whether solicitation includes:

• direct contact by phone, email, message, or meeting
• contact through another staff member or related company
• responding to an approach made by the customer first
• general advertising or public announcements
• pitching services that overlap only partly with the original deal
• hiring discussions initiated by the employee or contractor

If a clause says you must not “solicit, canvass, entice away, deal with, service, accept business from, or interfere with” protected persons, the practical effect may be much broader than a standard non-solicit.

How long should the restraint last?

The period should be long enough to protect real goodwill, not long enough to freeze ordinary competition. For many software relationships, a short to moderate period may be easier to justify than a lengthy restriction, especially where customer contracts renew annually or the departing person did not control the full relationship.

Duration depends on context, including:

• how long customer relationships normally take to transfer
• whether the restrained party had senior strategic access
• how quickly confidential information becomes stale
• whether the business has other protections, such as confidentiality and IP clauses

Graduated or cascading periods sometimes appear in restraint drafting. These need careful handling because poor drafting can create uncertainty rather than protection.

Is the geographic scope sensible?

For cloud software businesses, geography can be awkward because services are delivered online. A nationwide or international restraint may still be challenged if the business relationship was narrower than that.

Look at where customers are actually based, where the person worked, and whether the clause really needs a territorial limit at all. A customer-based definition may sometimes be clearer than a blunt territorial ban.

Does the clause overlap with confidentiality, privacy, and IP obligations?

A well-drafted contract separates different risks instead of rolling them into one vague restraint. If your real concern is misuse of customer lists, product roadmaps, pricing, or integrations, a clear confidentiality clause may do much of the work. If the issue is access to client data, your privacy notice and information handling terms matter just as much.

For asset management software businesses, check the contract position on:

• who owns customer data and derived analytics
• what confidential information includes
• what happens on termination to stored or exported data
• whether subcontractors can retain know-how or reusable code
• whether the restricted party can use de-identified learnings or generic experience

Does the clause allow ordinary business activity?

A restraint should not stop a business from carrying on legitimate work that has nothing to do with unfairly targeting another party's relationships. This matters where your business serves overlapping customer segments, such as fund managers, advisers, custodians, or enterprise finance teams.

Before you sign, think about whether the contract should expressly permit:

• general marketing not targeted at protected persons
• dealing with existing clients you already serviced before the contract
• responding to public tenders
• hiring through broad recruitment campaigns rather than targeted approaches
• work for clients who approach you without prior prompting

These carve-outs need careful wording. A promise that the other side will “be sensible about it” is not enough once a dispute starts.

Who in your business is actually bound?

Some software contracts try to bind the company, its founders, group companies, employees, and contractors in one sweep. That can create practical problems if the business grows, restructures, or uses offshore personnel.

Check whether the clause binds:

• only the contracting entity
• individual directors or founders personally
• related companies and future affiliates
• subcontractors and implementation partners

If the wording is broad, you may be taking on obligations you cannot fully control.

What happens if the clause is breached?

The contract may allow urgent court action, damages claims, indemnities, withheld payments, or termination rights. Some clauses also interact with earn-outs, deferred consideration, or bonus payments in business sale and senior executive arrangements.

Before you rely on a verbal promise, read the remedy section closely. The practical risk is not just whether the clause would ultimately hold up in court. The immediate problem can be an injunction threat that disrupts a client move, staff hire, or transaction timetable.

Common Mistakes With Non-solicitation Clause for Asset Management Software Business

The most common mistake is treating the restraint as boilerplate. In this sector, a few words can change whether the clause protects legitimate relationships or creates a major drag on hiring, sales, and exit plans.

Accepting a broad definition of customer

Founders often focus on pricing, service levels, and liability clauses, then skim over restraint wording. Later, they discover the clause captures prospects, former clients, related entities, and anyone introduced during the term.

That is especially risky where enterprise deals involve parent companies, subsidiaries, advisers, and implementation consultants. One customer relationship can expand into a much larger restricted pool than expected.

Ignoring staff non-solicitation because the immediate deal is customer-facing

A software business may sign a partner or outsourcing agreement thinking only about clients. Then a dispute starts because one side hires a solutions architect, implementation lead, or account manager from the other.

If the agreement includes staff non-solicitation, make sure it is proportionate and clear. There is a big difference between preventing a targeted raid on a team and banning any hire of any person who worked for the other business at any time.

Assuming general industry marketing is safe

It may not be. If the clause is drafted broadly enough, a targeted campaign aimed at a defined market segment could still be argued to amount to indirect solicitation. This matters in niche B2B software markets where the pool of likely buyers is small and identifiable.

If you need freedom to advertise generally, respond to public procurement, or market to a class of financial services businesses, spell that out before you sign.

Using the same clause for employees, contractors, and commercial partners

These relationships are different and should not be treated as interchangeable. A clause that may be arguable in a founder sale agreement can be excessive in a junior employment agreement. A restriction suitable for a reseller may make little sense for a short-term developer contractor.

Templates create trouble when they ignore the nature of the relationship, the seniority of the person involved, and the real commercial risk.

Overlooking the interaction with privacy and data access

In asset management software, customer information can be highly sensitive. A business may think a non-solicitation clause solves the problem, when the bigger issue is who can access client lists, usage data, account contacts, export tools, and reporting history after termination.

Where data access is the real pressure point, the contract should also deal properly with:

• role-based access controls
• return, deletion, and retention obligations
• limits on using customer data for marketing
• audit rights and security expectations

Relying on verbal explanations during negotiation

A salesperson or counterparty might say the restraint is “standard” or only aimed at deliberate poaching. If the written contract says something broader, the written version is what matters most.

Before you sign, ask for wording changes, examples, or carve-outs in the document itself. Side conversations rarely give enough protection.

Missing the issue during investment or sale due diligence

Investors and buyers often review key customer, founder, and staff agreements closely. A badly drafted restraint can reduce flexibility around team moves, transition arrangements, and revenue assumptions.

If you are preparing for a raise, acquisition, or strategic partnership, clean up unclear non-solicitation wording early. It is much easier to fix before the transaction timetable starts.

FAQs

Are non-solicitation clauses enforceable in New Zealand?

Sometimes, yes, but not automatically. The clause usually needs to protect a legitimate business interest and be reasonable in its scope, duration, and operation.

Can a non-solicitation clause stop a former employee from working for a competitor?

Not by itself. A non-solicitation clause usually targets approaches to customers, staff, or contacts. A separate non-compete clause would deal more directly with working for a competitor, and those clauses also need careful scrutiny.

Does responding to an inbound client enquiry count as solicitation?

It depends on the drafting. Some clauses only ban active approaches, while others also restrict accepting business from protected clients. That distinction matters and should be reviewed before you sign.

How long should a non-solicitation clause last?

There is no single safe period. The right duration depends on the role, the customer relationship, the sales cycle, and the other protections in the contract. Longer is not always better.

Should asset management software businesses use the same restraint clause in every agreement?

No. Employment, contractor, partner, reseller, customer, and sale agreements create different risks. The clause should match the relationship and the actual business interest being protected.

Key Takeaways

• A non-solicitation clause for asset management software business arrangements should protect real customer, staff, and partner relationships without blocking ordinary competition.
• In New Zealand, these clauses are more likely to be effective when they are tied to a legitimate business interest and are reasonable in scope, duration, and who they cover.
• The biggest drafting issues are usually the definition of protected persons, the meaning of solicitation, the length of the restraint, and the available exceptions.
• For software businesses, restraint wording should be reviewed alongside confidentiality, privacy, data handling, IP ownership, and termination rights.
• Founders often get caught by broad boilerplate wording, verbal assurances that do not match the contract, and hidden staff non-solicitation restrictions.
• Before you sign a contract, assess the practical effect of the clause on sales, hiring, partnerships, outsourcing, and future investment or exit activity.

If you want help with contract drafting, restraint clause negotiation, confidentiality terms, and data handling provisions, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.