When to Use a Non-solicitation Clause in a Remote Work Software Contract in the UK

If you run a remote work software business, your contracts often give suppliers, consultants, resellers or implementation partners access to valuable relationships. That can include your customers, your team, your sales pipeline and the contacts you have spent years building. A non-solicitation clause can help protect those relationships, but founders often get this wrong.

Common mistakes include copying a broad restraint from a US template, using a clause that tries to stop all competition rather than targeted poaching, or dropping the clause into standard terms without defining who is actually protected. Another frequent problem is relying on a vague verbal promise that a contractor will not approach your clients after the project ends.

The real question is not whether a non-solicitation clause sounds useful. It is when to use one, what it should cover, and how to make it more likely to hold up under UK law. This guide explains where a non-solicitation clause fits in a remote work software contract, what to check before you sign, and the drafting mistakes that can create risk instead of protection.

Overview

A non-solicitation clause is usually worth considering when another business, contractor or senior hire will have real access to your customers, leads or staff and could use that access to divert relationships away from you. In the UK, the clause needs to go no further than reasonably necessary to protect a legitimate business interest, otherwise enforceability becomes a serious issue.

• Identify exactly who might be solicited, such as current customers, named prospects, employees or contractors.
• Match the restriction to a real risk, for example a reseller approaching your direct clients or a consultant recruiting your product team.
• Keep the duration and scope reasonable, with language tailored to the role and access involved.
• Separate non-solicitation from non-compete and confidentiality obligations rather than blending them together.
• Check the contract works with your data protection, confidentiality, IP and termination clauses.
• Review the clause before you accept the provider's standard terms or rely on a template contract review.

What Non-solicitation Clause for Remote Work Software Business Means For UK Businesses

A non-solicitation clause is a contract term that restricts one party from actively approaching certain people or organisations connected with the other party for a defined period. For a UK remote work software business, it is usually aimed at preventing poaching of customers, leads, employees or contractors after access has been given through the commercial relationship.

This is different from a non-compete clause. A non-compete tries to stop someone from carrying on a competing business or working with a competitor. A non-solicitation clause is narrower. It focuses on targeted approaches, such as asking your client to switch provider or asking your developer to leave and join the other party.

That narrower focus matters in the UK because restraints of trade are judged carefully. A clause is more likely to be enforceable if it protects a legitimate business interest and goes no further than is reasonably necessary. Courts generally do not uphold restrictions simply because one party wants broad commercial control after the contract ends.

When this clause is usually worth including

The clause is most useful where the other party will gain meaningful relationship access through the contract. In remote work software, that comes up often.

• A white-label partner or reseller gets visibility of your customer base and buying patterns.
• An implementation consultant works directly with your enterprise clients and becomes a trusted contact.
• A managed service provider supports your platform and deals with your customer success team.
• A senior contractor or agency meets your staff, learns reporting lines and later tries to recruit them.
• A channel partner receives details of warm prospects and could bypass you to close deals directly.

If the contract is low touch and the other party has no real exposure to your people or customers, the clause may add little value. Overusing restraints can make negotiations harder without giving you better protection.

What a legitimate business interest looks like

Before you sign a contract, ask what interest you are actually protecting. In this context, the strongest interests usually include customer connections, workforce stability and confidential pipeline information tied to relationship building.

For example, if a contractor is embedded in your sales process for six months and attends renewal calls with key accounts, you may have a real interest in stopping that contractor from contacting those accounts immediately after the project ends. If an outsourced head of engineering has direct contact with your senior developers, a limited restriction on soliciting those developers may also be justifiable.

What tends to be weaker is a generic attempt to stop the other party dealing with anyone in your sector. A restraint should be tied to relationships and access created through the contract, not used as a broad market-blocking tool.

Customer non-solicitation versus staff non-solicitation

These are often bundled together, but they raise slightly different issues. Customer non-solicitation is about protecting the goodwill and revenue stream connected to clients and prospects. Staff non-solicitation is about stopping disruption to your workforce and protecting investment in key personnel.

It often makes sense to draft them separately so the scope is clearer. A clause covering customers may refer to clients the other party had material dealings with during the final 12 months of the contract. A staff clause may be limited to employees or contractors in roles they had direct contact with, rather than everyone on your payroll.

Why remote work software contracts need special care

Remote work software businesses often rely on distributed teams, channel partnerships and recurring SaaS relationships. That creates a practical problem: your value is not only in code, it is also in account relationships, onboarding knowledge and your ability to keep teams and customers connected.

Founders can underestimate how much commercial leverage a consultant or service partner gains once they are in the room for onboarding calls, security reviews and renewal discussions. A well-drafted non-solicitation clause can help manage that risk, especially where your product is sold through longer sales cycles and relationship trust matters.

At the same time, these contracts frequently cross borders. If your template is borrowed from another market, the wording may be too broad for UK expectations. This is where founders often get caught, particularly before they accept the provider's standard terms without checking whether the restraint language has been adapted for the UK.

Legal Issues To Check Before You Sign

The main legal issue is enforceability. In the UK, a non-solicitation clause should be targeted, reasonable and linked to a legitimate business interest. If it is too wide, it may be difficult to rely on when you need it most.

Define who is protected

A vague clause that refers to “any clients, staff or contacts” invites argument. Before you sign, decide exactly which groups need protection and define them clearly in the written terms.

• Current customers.
• Former customers within a recent period, if there is a genuine reason.
• Active prospects or named leads in your pipeline.
• Employees.
• Contractors or consultants who are central to delivery.

For prospects, be careful. Trying to restrict approaches to anyone your business has ever contacted is often too broad. A better approach is to limit this to prospects with whom the other party had material involvement, or those in an active sales process during a defined period.

Be clear on what counts as solicitation

Not every future interaction is solicitation. The contract should make clear what behaviour is restricted. That might include directly approaching a customer to move services away from you, persuading an employee to resign, or using project access to make an offer outside the agreed channel.

You should also think about what is not meant to be caught. General advertising, responses to unsolicited approaches, or dealing with someone where no active encouragement took place may need separate treatment. If the clause is silent, disputes can become expensive and heavily fact-specific.

Set a reasonable time period

The duration should reflect the relationship risk, not just your preference. A short to moderate post-termination period is more likely to be defensible than a lengthy blanket restriction. What is reasonable depends on the role, sector and sales cycle.

For many software contracts, periods such as 6 or 12 months are commonly considered, but there is no universal safe number. A clause affecting a consultant with access to one key account may justify a different period from one affecting a strategic channel partner with access to dozens of customers and your roadmap discussions.

Limit the scope to relevant relationships

The clause should usually focus on people or businesses the restricted party had contact with, responsibility for, or confidential information about. That keeps the term tied to actual risk.

A broad ban on soliciting any customer of your group, anywhere in the world, regardless of contact, is harder to justify. A narrower ban on soliciting customers that the partner serviced or learned about through the agreement is easier to explain.

Check the clause against confidentiality and IP terms

A non-solicitation clause does not replace confidentiality protections. If the real concern is misuse of account data, pricing models, customer usage patterns or roadmap information, you also need strong confidentiality wording and sensible data access controls.

IP clauses matter too. In software deals, one party may have access to source code, product documentation, implementation playbooks and internal processes. While that is not the same as solicitation, the risks often overlap in practice. Your contract should deal with each issue separately so you are not forcing one clause to do too much work.

Consider data protection and practical evidence

If the other party processes personal data relating to your staff contacts, customer stakeholders or prospect lists, your data protection arrangements matter. The agreement should reflect who is controller or processor where relevant, what data can be used, and for what purpose. Misuse of contact data can support a broader contractual dispute, but only if your documents and systems are aligned.

Evidence also matters before any problem arises. If you later need to show that a person was protected by the clause, you will want clean CRM records, project access logs, contact ownership records and clear descriptions of who dealt with whom. Many disputes become difficult because the contract was drafted narrowly but the business kept poor records.

Think about group companies and subcontractors

Remote work software businesses often contract through one entity while services are delivered by affiliates or subcontractors. If you want protection for group customers or against solicitation by subcontractors, the contract needs to say so clearly.

Similarly, if the other party is allowed to use subcontractors, check whether the non-solicitation obligations flow down to them. Otherwise the restriction may be easy to sidestep in practice.

Plan what happens on termination

The clause should work with your termination rights and exit provisions. When the relationship ends, the contract should address return or deletion of contact lists, ongoing account handover, who can communicate with shared customers, and whether any exceptions apply during transition.

That is particularly important where the other party was customer-facing. Without a clean exit process, it can be harder to prove later that post-termination contact crossed the line into prohibited solicitation.

Common Mistakes With Non-solicitation Clause for Remote Work Software Business

The most common mistake is treating the clause as standard boilerplate. In reality, a useful non-solicitation clause depends heavily on who gets access to what, for how long, and why that access matters to your business.

Using a clause that is really a non-compete in disguise

Some contracts say “non-solicitation” but then try to stop the other party working in the same sector, dealing with all competing platforms, or servicing any similar customers. That can undermine the whole restraint.

If your concern is poaching, draft for poaching. If your concern is competition, take advice on whether a separate and narrower restriction is justified. Blurring the two often weakens your position.

Failing to define prospects properly

Founders often want prospect protection because pipeline relationships are valuable. That is understandable, but badly defined prospect wording can become overreach.

For example, “any prospective client introduced directly or indirectly” may be too uncertain. A better approach may be to cover prospects who were identified in writing, allocated to the partner, or involved in a live opportunity within a recent and defined period.

Ignoring mutuality where it would help negotiations

Not every contract needs a mutual restriction, but some deals are easier to close if both parties accept sensible no-poaching rules. If the relationship is collaborative and each side is exposing key contacts, a one-sided clause can create friction and delay.

That does not mean both sides need identical wording. It means you should think commercially before you sign, rather than assuming your preferred wording will pass without discussion.

Leaving out carve-outs

Reasonable carve-outs can make the clause clearer and more workable. Without them, you may capture ordinary business activity you never intended to restrict.

• General advertising not directed at protected individuals.
• Responses to approaches not actively encouraged by the restricted party.
• Recruitment through broad public campaigns where there was no targeted contact.
• Customers already known to the restricted party independently, where that can be evidenced.

Carve-outs need careful drafting. If they are too broad, they swallow the clause. If they are too narrow, they create arguments over routine conduct.

Forgetting the people side of enforcement

Contracts do not enforce themselves. If your account managers, founders and procurement leads do not know the clause exists, practical breaches can happen unnoticed.

Make sure the right internal people know:

• which counterparties are bound by non-solicitation obligations,
• which customers or staff groups are covered,
• what signs of poaching to escalate, and
• what records to preserve if concerns arise.

This is especially important in remote businesses where relationship ownership can be spread across Slack, email, CRM systems and shared video calls.

Relying on the clause without checking the wider contract

A non-solicitation clause works best as part of a broader contract structure. Founders sometimes focus on that one term and ignore the rest of the document.

Problems often appear where the agreement also needs:

• confidentiality obligations that survive termination,
• clear limits on use of customer data and prospect information,
• IP ownership and licence wording for implementation materials,
• termination rights if the relationship breaks down, and
• dispute and notice clauses that make enforcement practical.

If those pieces are weak, the non-solicitation clause may give less protection than you expect.

Copying employment-style restraints into a commercial contract

Employment and commercial restraints are related but not identical. A clause taken from a senior employment contract may sit awkwardly in a SaaS partner agreement or consultancy arrangement.

The commercial context, bargaining position, access profile and wording all matter. Before you rely on a template, check that it matches the type of relationship you are actually documenting.

FAQs

Is a non-solicitation clause enforceable in the UK?

It can be, if it protects a legitimate business interest and is no wider than reasonably necessary. Overly broad clauses are more vulnerable to challenge.

Should a remote work software contract include customer and employee non-solicitation?

Often yes, where the other party will have real access to your customers, prospects or team. The two protections should usually be drafted separately so the scope is clear.

How long should a non-solicitation clause last?

There is no fixed answer. The period should reflect the genuine relationship risk and be reasonable for the role and contract context. Many businesses consider 6 to 12 months, but the right period depends on the facts.

Does non-solicitation stop a party from working with competitors?

No, not by itself. Non-solicitation usually targets active poaching of protected customers or staff. A wider ban on competition is a different type of restriction and needs separate consideration.

Can standard supplier terms be enough?

Sometimes, but standard terms are often too generic. Before you accept the provider's standard terms, check definitions, duration, carve-outs, subcontractor coverage and how the clause fits with confidentiality, data protection and termination wording.

Key Takeaways

• A non-solicitation clause is most useful when a counterparty will gain meaningful access to your customers, prospects, employees or contractors through the contract.
• In the UK, the clause should protect a legitimate business interest and be limited to what is reasonably necessary in scope, duration and wording.
• Customer and staff non-solicitation clauses are usually clearer and more defensible when drafted separately.
• The strongest drafting identifies who is protected, what conduct counts as solicitation, what carve-outs apply and how long the restriction lasts.
• For remote work software businesses, the clause should work alongside confidentiality, data protection, IP, subcontractor and termination provisions.
• Templates copied from other markets or from employment contracts often create avoidable problems in commercial software agreements.
• Before you sign, tailor the clause to the actual relationship risk rather than treating it as standard boilerplate.

If you want help with contract drafting, restraint clause negotiation, confidentiality terms, and termination protections, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.