Why a UK Field Service Software Startup Needs a Co-founder Agreement

A field service software startup can look simple at the beginning. One founder builds the platform, another brings industry contacts, and both assume they will sort the legal detail out later. That is usually where problems start. Founders often make three costly mistakes early on: they split shares without agreeing vesting, they rely on verbal promises about roles and decision-making, and they assume any code, client list or product idea automatically belongs to the company.

For a UK business selling software to trades, maintenance teams, installers or mobile workforces, those gaps can become serious fast. One co-founder may be handling integrations, another may be negotiating pilots with commercial customers, and both may be putting in very different amounts of time and money. If expectations are not written down before you sign customer contracts or accept investment interest, disputes can affect ownership, control and even the value of the business.

This guide explains what a co-founder agreement for field service software company founders should cover, the legal issues to check before you sign, and the mistakes that catch UK software startups out.

Overview

A co-founder agreement records the practical rules between founders before memories fade and pressure builds. For a field service software company, it should deal with ownership, work contribution, intellectual property, decision-making, founder departures and what happens if plans change.

• Who the founders are and what each person is expected to contribute
• How shares will be split, and whether vesting or milestones apply
• Who owns the software code, product roadmap, branding and customer materials
• Which decisions require unanimous approval and which can be made day to day
• What salaries, reimbursements or founder loans are expected
• How confidentiality, non-compete and non-solicit obligations will work
• What happens if a founder leaves, underperforms, becomes ill or stops contributing
• How founder shares can be transferred, bought back or diluted in future funding rounds
• How disputes will be handled before they damage the company

What Co-founder Agreement for Field Service Software Company Means For UK Businesses

A co-founder agreement is the founders' rulebook, not a formality. It gives the business a written position on ownership, control and responsibility before the first major disagreement.

For a UK field service software business, that matters because the product is usually built around a mix of software development, service workflow know-how and customer relationships. One founder may understand dispatch logic, quoting tools, job scheduling and mobile technician workflows. Another may be writing code, handling integrations or designing the data architecture. If those contributions are not documented, each founder can form a different view about what they are owed.

The agreement is separate from the company's constitutional documents, although it should work with them. If the startup is operating through a private limited company, the articles of association, any shareholders' agreement and share issue documents must line up with the co-founder arrangement. If they do not, you can end up with practical confusion over voting rights, board decisions and transfers of shares.

Why this matters more in field service software

The product in this sector often depends on operational detail that is hard to replace. A founder may bring a tested workflow from years in facilities management, plumbing networks, electrical services, HVAC operations or mobile maintenance scheduling. Another may have built the scheduling engine or AI-driven route optimisation that makes the software commercially useful.

That makes the main assets less obvious than a physical business. The value may sit in:

• source code and system architecture
• customer discovery notes and implementation playbooks
• integration logic for accounting, CRM or job management tools
• pricing models and sales scripts
• branding, domain strategy and product names
• pilot customer relationships and case study material

If ownership of those assets is left vague, problems can surface when a founder exits or tries to reuse parts of the business elsewhere.

What a good agreement usually covers

A useful co-founder agreement is specific about founder behaviour, not just high-level principles. Before you rely on a verbal promise, the document should spell out what each person is actually doing and what happens if that changes.

Most UK software founders should consider including:

• founder names, start dates and any pre-company work already done
• roles, responsibilities and expected weekly time commitment
• cash contributions, equipment contributions and whether any amounts are loans
• share allocation, vesting rules and any performance milestones
• board roles, reserved matters and day-to-day authority limits
• ownership and assignment of intellectual property created before and after incorporation
• confidentiality obligations and limits on using company information elsewhere
• restrictions on competing ventures or poaching staff and customers, where reasonable
• good leaver and bad leaver rules if someone departs
• deadlock resolution, mediation steps and exit options

How it fits with later legal documents

Your co-founder agreement is usually the starting point, not the only document. As the business grows, founders often need shareholder documents, employment contracts or service agreements, IP assignments, privacy paperwork and customer terms that reflect the same deal.

That is especially relevant for software businesses processing job, address, contact and technician data. If one founder controls product development and another controls customer onboarding, responsibilities around privacy compliance, data handling and security need to be clear in practice. A co-founder agreement will not replace customer contracts or UK GDPR documents, but it helps stop internal confusion about who is accountable for what.

Legal Issues To Check Before You Sign

The key legal issues are ownership, control, exits and enforceability. If those points are unclear before you sign, the agreement can create more arguments than it solves.

Share split and vesting

An equal split sounds fair, but it is often agreed too quickly. In early stage software companies, founder contributions can change dramatically after the first six to twelve months. One person may still be building full-time while another returns to a day job or contributes mainly introductions.

Vesting helps deal with that. Instead of treating all founder shares as fully earned on day one, vesting can mean shares are earned over time or become vulnerable to buyback if a founder leaves early. That way, a departing founder is less likely to walk away with a large stake they no longer support.

Before you sign, check:

• whether shares are issued immediately or over time
• whether there is a cliff period before any shares are treated as earned
• what happens if a founder resigns, is removed or becomes unable to work
• whether the company or other founders can buy back unvested or vested shares
• how future investment rounds may dilute each founder

Intellectual property ownership

The software does not automatically belong to the company just because it was built for the startup. If code, branding, workflow designs or implementation templates were created before incorporation or on personal devices, ownership should be dealt with clearly.

This point is especially important where a technical founder has reused libraries, frameworks or modules from earlier projects, or where an industry founder has brought in customer forms, checklist templates or operating methods from previous work. Some material may be owned personally, some may belong to a past employer, and some may have third-party licence conditions attached.

The agreement should address:

• what each founder created before the company existed
• what pre-existing material is being licensed or assigned to the company
• who owns new code, documentation, designs and branding created for the business
• whether open source software is used and on what terms
• what assistance a founder must give later to confirm or perfect ownership

Decision-making and authority

Founders usually get along until a high-pressure decision arrives. A software startup may need to sign a major customer on discounted terms, commit to a development roadmap, hire staff quickly or accept an exclusivity request from an implementation partner. If no one knows who can approve what, conflict follows.

A co-founder agreement should separate routine decisions from reserved matters. Routine decisions might sit with the relevant founder or board member. Reserved matters should require both founders or a higher voting threshold.

Examples of reserved matters may include:

• issuing new shares or options
• taking on debt or entering founder loans
• changing the business model or target market
• selling key intellectual property
• hiring or dismissing senior employees
• approving a sale of the company
• signing long-term strategic contracts

Confidentiality and restrictive obligations

Founders often share sensitive product and customer information casually. That is risky where one founder remains involved in other businesses or advisory roles. The agreement should make it clear what is confidential and what can be used outside the startup.

Restrictions on competition and solicitation can also be useful, but they need to be carefully framed. In the UK, restrictive clauses are not automatically enforceable just because they appear in a contract. They should go no further than reasonably necessary to protect legitimate business interests.

Leaver provisions and disputes

The hardest conversations are usually the most valuable. If a founder loses interest, misses deadlines, behaves improperly or faces long-term incapacity, the agreement should say what happens next.

Before you sign, think about:

• how voluntary resignation is handled
• what counts as serious misconduct or material breach
• how shares are valued on exit
• whether there is a compulsory transfer process
• whether mediation must happen before court action
• who controls the company's systems, passwords and customer accounts during a dispute

Common Mistakes With Co-founder Agreement for Field Service Software Company

The most common mistake is treating the agreement as a friendship document instead of a risk document. Good founders use it to deal with awkward scenarios before they happen.

Assuming equal shares mean equal commitment

Two founders can both deserve meaningful ownership without contributing in the same way. One may commit full-time coding and product management. Another may bring customer access and industry credibility but only part-time effort. If the agreement does not reflect that reality, resentment can build once the workload becomes obvious.

This is where founders often get caught before they sign customer contracts or start discussing investment. Investors and commercial partners tend to ask who owns what and why. If the answer is vague, that can damage confidence.

Leaving pre-incorporation work undocumented

Many field service software products start as side projects, consultancy tools or custom solutions for one early client. Later, the founders decide to build a standalone product. If the original codebase, UI components, workflow templates or name were created earlier, the company may not own them automatically.

The risk is higher if a founder previously did similar work as an employee or contractor. Another party may claim rights in part of the product, or the founder may simply assume they can take the material elsewhere if they leave.

Ignoring what happens if one founder keeps consulting

Industry founders often continue consultancy work while the software business grows. That can be commercially sensible, but only if boundaries are clear. Without them, there may be arguments about who owns new process improvements, customer contacts or data insights developed through that consulting work.

The agreement should make clear:

• whether outside work is allowed
• what conflicts must be disclosed
• which opportunities must be offered to the company first
• how company time, contacts and information can be used

Using generic templates that miss software-specific issues

A basic founder template may mention shares and confidentiality, but miss the issues that matter in software. Field service platforms often depend on integrations, implementation support, ongoing development, data mapping and service-level promises to customers. If the founders are not clear on who handles those areas and who can commit the business, internal tension can become a legal problem.

A generic document may also say little about open source usage, moral rights waivers, assignment of future IP, or restrictions on reusing code after exit. Those details can matter a great deal if the product gains traction.

Forgetting the agreement must match company documents

A founder document is not much help if the articles, cap table and board paperwork say something different. For example, the co-founder agreement might describe a buyback right on departure, but the share documents may not support that process cleanly. Or the founders may think certain decisions need unanimous approval, but the directors' authority under the company paperwork says otherwise.

Before you rely on the signed agreement, make sure it aligns with:

• the company's articles of association
• share allotment and transfer documents
• any shareholders' agreement
• director appointment records
• employment or consultancy terms for each founder

Failing to revisit the agreement after the first real milestone

A founder deal agreed around an early prototype may no longer make sense once the company has paying customers, staff, investor conversations or a changed product focus. Field service software businesses often pivot from one user group to another, such as moving from small trades to enterprise maintenance teams. That can change each founder's role substantially.

The agreement should not sit in a drawer untouched. Review it when there is a funding round, a material change in workload, a founder joining or leaving, or a shift in strategic direction.

FAQs

Is a co-founder agreement legally binding in the UK?

It can be, if it is drafted as a binding contract and signed properly. Whether a particular clause is enforceable depends on the wording, the facts and how it fits with company law documents.

Do we still need one if we trust each other?

Yes. Trust is exactly why founders should record expectations early, while everyone is aligned. The agreement reduces the chance of future misunderstandings about shares, roles and exits.

Should a field service software startup use vesting?

Often yes, especially where founders are contributing different amounts of time, money or technical work. Vesting can help avoid a situation where an early leaver keeps a large equity stake without ongoing involvement.

Does the company automatically own code a founder writes?

Not always. Ownership depends on when, how and under what arrangement the code was created. Clear assignment wording is usually needed, particularly for pre-incorporation work or material developed outside employment.

When should founders put this agreement in place?

Ideally at the start, before you sign a major contract, issue shares, accept external investment interest or rely on assumptions about ownership and decision-making.

Key Takeaways

• A co-founder agreement for field service software company founders should be signed early, before assumptions harden into disputes.
• The document should deal clearly with share split, vesting, founder roles, decision-making and what happens if someone leaves.
• Intellectual property is a major risk area for software businesses, especially where code, workflows or branding existed before the company was formed.
• Restrictions on competition, confidentiality and customer solicitation should be tailored carefully and kept reasonable.
• The agreement should match the company's articles, share documents and any wider shareholder arrangements.
• Founders should revisit the agreement when the product, workload, funding position or team changes.

If you want help with founder equity terms, intellectual property assignment, leaver provisions, shareholder document alignment, and contract review, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.