Contract basics for service businesses

0:00 Contract basics for service businesses

A big client sends you their contract. Twenty-five pages of dense legal language, with a note: please sign by Friday. Many freelancers and small agencies simply sign, because asking for changes feels risky, or they don't know what to look for. That's how people end up with unlimited liability, ninety-day payment terms and no rights to their own tools. In this lecture, you'll learn the common contract structures for service businesses, the clauses that matter most, how to negotiate them constructively, including a new AI-use clause, and how to keep contracts practical. This is general information, not legal advice.

0:43 Why it matters

Why does this matter? Because contracts protect relationships as much as they protect you. Clear terms prevent misunderstandings, and fair terms mean nobody feels trapped. And most clients expect some negotiation. Large organisations often send one-sided templates as a starting point, and procurement teams are used to reasonable redlines. Here's the key idea. You don't need to be a lawyer to spot the handful of clauses that matter most, and asking for fair changes, politely, is normal professional behaviour.

1:17 The tenancy analogy

Here's an analogy. Think of a tenancy agreement for a flat. Most of it is standard. But a few clauses really matter: the rent and when it's due, the deposit and how it's returned, who fixes the boiler, how much notice either side must give, and what happens if something's damaged. You don't need to understand every word to check those. Service contracts are similar. A handful of clauses carry most of the risk and value: payment, IP, liability, indemnities, termination, acceptance, confidentiality, data and AI use, and governing law.

1:56 Structure and key clauses

First, structure. Many service businesses use a master services agreement, an MSA, for the legal terms that apply to the whole relationship, plus a statement of work for each project, with scope, deliverables, timeline and fees. Small projects can use signed proposals with attached terms of business. Now the key clauses. Payment terms. Intellectual property. Limitation of liability, which caps your exposure, often at the fees paid. Indemnities, meaning who pays if a third party sues. Termination and what's owed for work done. Acceptance. Confidentiality and data protection. AI use. Non-solicitation. And governing law and dispute resolution.

2:38 IP positions

Let's look at IP, a frequent point of negotiation. Clients often want to own everything, immediately. A fair position that many service businesses use: the client owns the final deliverables once they've paid in full. You keep your pre-existing tools, templates, code libraries and know-how, and license them for use in the deliverables. Third-party assets are licensed on their own terms. And for AI-assisted work, be careful what you warrant. Copyright protection for purely AI-generated material is uncertain in some jurisdictions, so give warranties you can honestly support, and record meaningful human contribution.

3:18 Liability and indemnities

Now limitation of liability, which many small businesses overlook. Without a cap, a mistake on a small project could expose you to claims far larger than your fee. A common, fair approach is to cap liability at the fees paid under the agreement, or over the last twelve months, and to exclude indirect losses like lost profits, with the usual exceptions the law requires, such as fraud. Be cautious with indemnities too. An open-ended promise to cover all the client's losses from any claim is very different from a mutual, limited indemnity, for example for your own infringement of someone else's IP.

4:02 Worked example 1: Ella in Brighton (illustrative)

A simple worked example, illustrative. Ella, a freelance developer in Brighton, receives a contract from a large retailer. She uses the priority list from the lesson. She finds unlimited liability, IP transferring on signature, and ninety-day payment terms. She sends a polite redline email proposing liability capped at fees paid, IP transferring on full payment with her tools retained, and thirty-day terms with milestone invoices. The retailer's legal team accepts the liability cap and IP change, and agrees forty-five days. Ella accepts that compromise, because monthly milestones keep the amounts small. The whole exchange takes three days.

4:44 Negotiating constructively

Now negotiating contracts constructively. Start by saying what's fine: it's mostly fine for us. Limit your changes to the ones that matter. Explain each briefly, and describe it as standard, which for most of these it is. Offer to discuss on a call. Prioritise: know which changes you must have, like a liability cap, and which are nice to have. And don't sign something you can't live with because of time pressure. Finally, the AI-use clause. Clients increasingly include one, or you should propose one: permitted uses, no client confidential data in tools that train on inputs, human review of deliverables, and disclosure on request.

5:30 Worked example 2: Lahore ↔ Saudi (illustrative)

Now the realistic scenario, illustrative. Bilal's software studio in Lahore is signing an MSA with a Saudi logistics group. The contract is bilingual, governed by Saudi law, with disputes resolved in Riyadh. It includes a broad indemnity, a five-year non-solicitation clause, and no mention of AI. Bilal prioritises. Must-haves: a liability cap, a narrower, mutual indemnity, and the English version prevailing for interpretation, or at least a certified translation he can rely on. Nice-to-haves: a shorter non-solicitation period and an AI-use clause. He engages a lawyer familiar with Saudi commercial contracts. The client agrees the cap, a narrower indemnity and the AI clause, and keeps Saudi law and Arabic as the prevailing language, with an official translation provided.

6:21 Watch me: reviewing a template

Watch me review a client's template with the priority list. I open the contract and search for each key clause. Payment: ninety days, no deposit. I'll propose thirty days with milestones. IP: transfers on creation. I'll propose on full payment, keeping my tools. Liability: no cap. Must-have: capped at fees paid. Indemnity: I indemnify them for all losses from any claim. I'll propose mutual and limited to IP infringement and breach of confidentiality. Termination: they can terminate anytime with no payment for work in progress. I'll add payment for work done. AI use: nothing. I'll add our standard clause. Then I write the redline email.

7:07 Common mistakes

Let's list the common mistakes. Signing without reading the key clauses. Accepting unlimited liability. Transferring IP before payment. Agreeing to open-ended indemnities. Missing termination payment terms. Ignoring governing law in international deals. Asking for dozens of trivial changes, which annoys legal teams. Staying silent on AI use. And not getting a lawyer for significant or cross-border contracts. Keep contracts practical too: a clear MSA and short SOWs you actually use beat a perfect document nobody reads.

7:40 Recap and try this now

Let's recap. Use an MSA for the relationship and SOWs for projects. Focus on the clauses that carry most of the risk: payment, IP, liability, indemnities, termination, acceptance, confidentiality and data, AI use, non-solicitation and governing law. Negotiate constructively: say what's fine, prioritise a few important changes, explain briefly and offer a call. Add or accept a sensible AI-use clause. Get legal advice for significant contracts. Your try this now: review your current contract or a client's template with the priority list, draft a redline email with no more than five changes, and book a lawyer's review of your template. Next module: managing expectations and difficult clients.