Service agreements for UK startups: a practical guide

What a service agreement does

A service agreement sets out the commercial terms under which your startup will perform work for a client. It could cover anything from a one-off software build to ongoing marketing retainers. Unlike website terms and conditions, which govern how visitors use your platform, a service agreement defines a specific project or ongoing engagement between two businesses.

For a startup with no in-house legal resource, having a clear, written agreement reduces the risk of disputes, late payment, and scope creep. It also proves what was agreed if things go wrong. Even with small jobs, a short document signed by both sides is far better than a chain of vague emails.

When you definitely need one

You should use a service agreement whenever you start paid work for a client that involves deliverables, deadlines, or repeat performance. It is particularly important if:

• The client will provide you with data, materials, or access to their systems.
• Your work creates intellectual property the client wants to own.
• The project has multiple phases or depends on client input.
• You are working on a time-and-materials rather than fixed-price basis.

A well-drafted agreement can be used repeatedly. Once you have a template you trust, you can tailor the scope of work for each client and send it out with minimal friction.

Key clauses every startup should include

The parties

Name the legal entities correctly. For a UK client, use their registered company name and number from Companies House. If you trade as an individual or partnership, use your full legal name and address.

Scope of work

Describe what you will do and, just as importantly, what you will not do. Be specific. For a website build, list the pages, functionality, and deliverables. For consultancy, define the number of hours, reports, or advice sessions included. This section is your best defence against scope creep. A simple bulleted list often works better than lengthy paragraphs.

Timetable and milestones

State the start date and either a completion date or a sequence of milestones with estimated delivery. If the project depends on the client providing materials or feedback, make clear that the timetable will extend if they are late. This protects you from being blamed for delays you did not cause.

Fees and payment terms

Set out whether you charge a fixed project fee, an hourly rate, or a monthly retainer. Include:

• What the price includes (and what it does not, such as third-party software licences or travel).
• When invoices will be issued (e.g., on signature, at milestones, monthly in arrears).
• Payment due date. 30 days is standard in the UK, but for a small startup, 14 days or payment on receipt may be more practical.
• Late payment interest. Under late payment legislation, you can claim statutory interest at 8% above the Bank of England base rate plus reasonable recovery costs. Mentioning this in the agreement gives you a contractual right to charge it without fuss.

Client responsibilities

List anything the client must do for you to complete the work, such as provide logos, content, API access, or feedback by agreed dates. If the client fails to do so, the timeline adjusts and any extra cost you incur is payable by the client.

Intellectual property

This is often the trickiest clause. Decide who owns the work you create. Typically, the client will want full ownership of deliverables created specifically for them. You may want to retain ownership of your pre-existing tools, code libraries, or methodologies. The agreement should:

• Confirm that you grant the client a licence (or assign ownership, if agreed) only upon full payment.
• Carve out your pre-existing IP and grant the client a licence to use it as part of the deliverables.
• Clarify that you can use general skills, know-how, and techniques learned during the project for other clients (unless confidential information is involved).

If you are unsure about the IP position, ask a solicitor to review this section. Getting it wrong can make it difficult to reuse your own code or approach.

Confidentiality

Both sides may share sensitive business information. A short mutual confidentiality clause requires each party to keep the other’s information secure and only use it for the project. Exclude information that is already public or independently developed. This is simpler than signing a separate NDA for every engagement — you can build it straight into the service agreement.

Limitation of liability

As a small company, you need to cap your financial exposure if something goes wrong. Most service agreements for UK startups limit total liability to the fees paid under the agreement, or to a fixed amount such as the value of your professional indemnity insurance. This does not remove liability for death, personal injury, fraud, or anything that cannot be limited by law. It does, however, protect your business from a claim that could exceed your revenue from the project.

Consult a solicitor to check the cap is enforceable and appropriate. A badly drafted limitation clause can be ineffective.

Termination

Make clear how either party can end the agreement. Common approaches:

• For convenience, with 30 days’ written notice (for ongoing engagements).
• For a material breach that is not remedied within, say, 14 days of being notified.
• Immediately if one party becomes insolvent.

State what happens on termination: what work you will hand over, what the client must pay for work done up to that date, and how long the confidentiality obligations survive.

Data protection

If you will process personal data on the client’s behalf, you may need a data processing agreement (DPA) alongside your service agreement. Even if a full DPA is not required, briefly state that each party will comply with UK data protection law when handling personal data shared under the agreement. For regulated or sensitive data, get specific advice.

Simple steps to get your agreement ready

1. Start with a professionally drafted template that covers these core clauses. StartupDocs’ template packs include a service agreement you can customise.
2. For each client, write a clear, jargon-free scope of work. Bullet points keep everyone honest.
3. Fill in the blanks (names, dates, fees) and send to the client as a PDF or via your document hub so there is a clear audit trail.
4. Agree changes using tracked suggestions, and make sure the final version is signed by both parties. A digital signature service or a simple email confirmation can work if both sides are comfortable, but a dated, signed PDF is cleaner.
5. Store the signed agreement and any amendments in one place. You will need them if a payment dispute or scope argument later arises.

When to get legal help

This guide describes what a typical service agreement includes, but it is not legal advice. Every business has different risks. If your project involves high-value IP, regulated sectors, cross-border delivery, or unusual liability exposure, ask a solicitor to review your template before you rely on it. A few hundred pounds spent on a targeted review can avoid a misunderstanding that costs far more later.

Keeping the client relationship on track

A service agreement is not meant to be adversarial; it is the foundation of a professional relationship. When both sides know what they are expected to deliver and pay, you spend less time chasing and more time doing good work. For a startup with a small team and no dedicated legal function, a clear, plain-English agreement is one of the most useful documents you can create.