Contracts, intellectual property and compliance basics

Video lecture

Contracts, intellectual property and compliance basics

11 chapters · about 8 min · full transcript

Coming soon

Chapter 1 of 11

Contracts, IP and compliance

Founders' agreements
Who owns the IP?
Customer and supplier contracts
Data protection
AI: ownership, data, policy

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Transcript of the narration, chapter by chapter.

0:00 Contracts, IP and compliance

Imagine you've built a successful product. An investor is ready to sign. Then, during due diligence, their lawyer asks a simple question: who owns the code? And you realise the first version was written by a freelancer who never signed anything. The deal stalls. In this lecture, you'll learn how to protect the business you're building: founders' agreements, intellectual property, customer and supplier contracts, data protection, and the new questions AI raises about who owns what, and what data you can put into which tools.

0:37 Why it matters

Why does this matter? Because legal gaps are cheap to fix early and expensive to fix late. A founders' agreement written in week one is a friendly conversation. The same agreement written after a falling out is a war. An IP assignment signed when a contractor starts costs nothing. Chasing a former contractor for one two years later can cost a deal. Here's the key idea. Paperwork doesn't slow a startup down. Missing paperwork does, usually at the worst possible moment. This lesson is general information, so always involve a qualified lawyer.

1:17 The house analogy

Here's an analogy. Think of your business as a house. The founders' agreement is the deed that says who owns which rooms and what happens if someone moves out. IP assignments are the receipts proving you actually bought the bricks. Customer and supplier contracts are the rules for guests and tradespeople. And data protection is the lock on the filing cabinet where you keep other people's personal details. You can live in a house without these for a while. But the moment you try to sell it, rent it or insure it, someone will ask to see every one.

2:00 Founders and IP

Let's take them in turn. A founders' agreement covers roles, the equity split, vesting, decision rights and what happens if someone leaves. Vesting is crucial. A common pattern is four years with a one-year cliff, meaning a founder who leaves in the first year keeps nothing, and after that earns their shares gradually. Next, IP. In many countries, a freelancer or contractor owns what they create unless there's a written assignment, and even employees' work can be unclear without proper terms. So every founder, employee and contractor should sign an IP assignment to the company. Then trademarks: search and register your name in your key markets before you invest in the brand.

2:49 Contracts and data

Now contracts with customers and suppliers. For services, a common structure is a master services agreement for the legal terms, plus a statement of work for each project's scope, deliverables, timeline and fees. Key clauses: payment terms, IP, confidentiality, limitation of liability, termination and dispute resolution. And data protection: if you collect personal data, you need a lawful basis, a clear privacy notice, security appropriate to the risk, and agreements with processors who handle data for you. Relevant laws include the UK GDPR, the EU GDPR for EU residents, the UAE's federal data protection law and Saudi Arabia's Personal Data Protection Law.

3:33 Worked example 1: no vesting (illustrative)

A simple worked example, illustrative. Two friends in Leicester start a small app business with an informal fifty-fifty split. Six months in, one takes a full-time job and stops contributing, but still owns half the company. Without vesting, there's no fair way to rebalance, and the remaining founder has to negotiate from a weak position. Now rewind. With a founders' agreement and four-year vesting with a one-year cliff, the departing founder would have left with nothing in the first year, or a fair proportion later. The conversation would have been awkward, but short and friendly.

4:14 AI questions

Now AI. Three new questions. First, who owns AI-assisted work? Copyright rules are unsettled and differ by country. The US Copyright Office has maintained that copyright protects human authorship, so purely AI-generated material may not be protected, while human selection, arrangement and editing can be. The UK has a provision for computer-generated works that's been under government review. So record meaningful human contribution to your key assets. Second, what data can go into which tools? Check each tool's terms on training, data location and retention. And third, what do your contracts say about AI use? Clients increasingly ask, and you should decide your answer before they do.

5:01 Worked example 2: an agency's AI policy (illustrative)

Now a realistic scenario, illustrative. Kareem runs a content agency in Abu Dhabi. A large client asks: do you use AI, and who owns the output? He has no policy and no answer. So he fixes it. He writes a one-page AI policy: approved tools on business plans that don't train on inputs, no client confidential data in unapproved tools, human review of everything, and disclosure on request. He adds an AI-use clause to his contracts, and adjusts his IP warranties to what he can honestly give. He keeps a register of tools and their terms. The client signs, and two competitors who couldn't answer lose the pitch.

5:48 Watch me: the legal checklist

Watch me work through the founder legal checklist from the lesson. Founders' agreement, with vesting: tick. IP assignments from every founder, employee and contractor: I find one contractor missing, so I send the assignment today. Contractor agreements with an AI-use clause: I add the clause to the template. Customer terms and privacy notice: tick. Data processing agreements, including with my AI and model providers: I check each provider's business terms and data settings. AI tools register: I list each tool, its plan, what data is allowed and who owns it. Trademark search: booked. Insurance: I review professional indemnity and cyber cover. Twenty minutes, and two real gaps closed.

6:35 Common mistakes

Let's list the common mistakes. No founders' agreement or no vesting. Contractors who never signed an IP assignment. Copying another company's terms that don't fit your business or jurisdiction. Collecting personal data without a lawful basis or privacy notice. Pasting customer data into AI tools that train on inputs. Promising clients IP warranties on AI output that you can't back up. And skipping trademark checks until after a rebrand is expensive. For tax and bookkeeping, keep records from day one, and check registration thresholds for VAT or sales tax where you operate.

7:15 Recap and try this now

Let's recap. Put the foundations in early: a founders' agreement with vesting, IP assignments from everyone who creates for you, clear customer and supplier contracts, and data protection that fits the laws where your customers are. For AI, record human contribution, check tool terms, write a one-page AI policy and state your position on AI use in contracts. Your try this now: complete the founder legal checklist, send any missing IP assignments today, and draft your one-page AI policy. And take the example clause to a qualified lawyer before you use it. Next, we'll look at building the company itself.

Protecting the business you are building

Early-stage founders often postpone legal basics until a problem appears. A few foundations, set up early, prevent expensive disputes and protect value. Again, this is general information, not legal advice.

Founders' agreement

Co-founder disputes are a common cause of startup failure. A founders' (or shareholders') agreement should cover:

Ownership percentages and how they were decided.
Vesting: founders earn their shares over time (commonly four years with a one-year "cliff" in startup practice), so a founder who leaves early does not keep a large stake.
Roles, decision-making and deadlock resolution.
What happens if a founder leaves, dies or becomes incapacitated.
Intellectual property assignment to the company.
Non-compete and confidentiality obligations (enforceability varies by jurisdiction).

Intellectual property (IP)

Type	Protects	Notes
Trademarks	Brand names, logos	Register in each country where you trade; check availability first
Copyright	Software code, content, designs	Arises automatically in many countries; ownership must be clear
Patents	New inventions	Expensive; strict novelty rules; public disclosure before filing can destroy rights
Trade secrets	Confidential know-how	Protected through confidentiality and access controls

Critical point: make sure the company owns the IP created by founders, employees and contractors. Use written assignments in employment and contractor agreements. Without them, a freelancer may own code your business depends on.

Customer and supplier contracts

Key clauses in customer contracts or terms of service:

Scope of service and service levels.
Payment terms and late payment.
Limitation of liability.
Data protection and confidentiality.
Intellectual property and licences.
Term, renewal and termination.
Governing law and dispute resolution.

Use templates from reputable sources as a starting point, but have a lawyer review your core contracts.

Data protection and privacy

If you collect personal data (customers, users, employees), privacy laws likely apply. Examples include the EU and UK GDPR, the UAE Federal Personal Data Protection Law, Saudi Arabia's Personal Data Protection Law (PDPL), sector rules and state laws in the US (such as California's), and Pakistan's applicable rules and developing data protection framework. Core practices:

Collect only what you need.
Tell people what you collect and why (privacy notice).
Get consent where required, especially for marketing.
Secure data; limit access.
Have a process for data requests and breaches.
Check rules on transferring data across borders.

Tax and bookkeeping basics

Register for relevant taxes (corporate income tax, VAT/sales tax, payroll taxes) when required.
Keep business and personal finances separate.
Maintain accurate books from day one; use accounting software.
Understand filing deadlines; penalties for late filing can be significant.
Budget for tax payments in your cash forecast.

Employment basics

When hiring, follow local employment law: written contracts, minimum wage and working hours rules, social security or pension contributions where applicable, visa and work permit requirements (particularly relevant in the UAE and KSA), and end-of-service or severance obligations.

Worked example

Illustrative. A startup in London built its app with a freelance developer without a written contract. When it raised investment, the investors' due diligence found that the company could not show it owned the code. The founders had to negotiate an IP assignment with the freelancer, who demanded payment, delaying the round by two months. A one-page assignment clause at the start would have prevented this.

Legal checklist for early-stage founders

[ ] Company registered with appropriate structure and licences
[ ] Founders' agreement with vesting and IP assignment
[ ] Employment and contractor agreements with IP and confidentiality clauses
[ ] Trademark search and registration in key markets
[ ] Customer terms / contracts reviewed by a lawyer
[ ] Privacy notice and data protection processes
[ ] Tax registrations and bookkeeping system
[ ] Insurance reviewed (e.g., professional liability, property, cyber)

2026 update: AI, IP and data

Ownership of AI-assisted work. Copyright rules for AI-generated material are unsettled and differ by country. For example, the US Copyright Office has maintained that copyright protects human authorship, so purely AI-generated material may not be protected, while human selection, arrangement and modification can be. The UK has a specific provision for "computer-generated works" that has been under government review. Practical steps:

Keep a record of meaningful human contribution to important assets (brand, code, content).
Check the terms of the AI tools you use: who owns outputs, whether inputs are used for training, and whether the provider offers any IP indemnity on business plans.
In client and contractor contracts, be explicit about AI use: whether it is allowed, disclosure, review responsibilities and IP warranties you can realistically give.

Data protection when using AI. Before sending personal data to an AI provider, check your lawful basis, the provider's data processing terms, where data is processed, and retention. Relevant laws include the UK GDPR and Data Protection Act 2018, the EU GDPR for EU residents' data, the UAE's federal personal data protection law and Saudi Arabia's Personal Data Protection Law (plus sector and free-zone regimes such as DIFC and ADGM). Pakistan has had draft personal data protection legislation for several years; check its current status and any sector rules. When in doubt, minimise and anonymise.

Company AI policy. Even a five-person business benefits from a one-page policy: approved tools, what data may never be pasted into them, when outputs need human review, disclosure to clients, and who to ask.

Hands-on: founder legal checklist (with AI items)

[ ] Founders' agreement: roles, equity split, vesting (e.g. 4 years with 1-year cliff), decision rights, exit
[ ] IP assignment: every founder, employee and contractor assigns work IP to the company
[ ] Contractor agreements: scope, payment, confidentiality, IP, AI-use clause
[ ] Customer terms / MSA + SOW; privacy notice; cookie approach where required
[ ] Data processing agreements with processors (including AI/model providers)
[ ] AI tools register: tool, plan, data allowed, training opt-out, owner
[ ] AI use policy (one page) shared with team
[ ] Trademark search and registration in key markets
[ ] Record-keeping for tax; VAT/GST registration thresholds checked
[ ] Insurance reviewed (professional indemnity, cyber)

Hands-on: AI-use clause (example wording to discuss with your lawyer)

AI-assisted work. The Supplier may use AI tools to assist in producing the
Deliverables, provided that (a) the Supplier does not input the Client's
Confidential Information or personal data into any tool that uses inputs for model
training or that has not been approved in writing by the Client; (b) all
Deliverables are reviewed by a qualified person before delivery; and (c) the
Supplier discloses, on request, which Deliverables were materially AI-generated.
The Supplier's IP warranties apply to the Deliverables as delivered, to the extent
permitted by the AI tool terms disclosed to the Client.

This is illustrative wording only, not legal advice; have a qualified lawyer adapt it to your jurisdiction and situation.

Common mistakes

No founders' agreement.
Contractors retaining IP ownership.
Launching a brand without checking trademarks.
Copying another company's privacy policy without matching your practices.
Mixing personal and business finances.

Quick self-check

Go through the checklist. Which three items are missing for your business, and when will you address them?

Founders' agreements with vesting and IP assignment prevent common disputes.
Ensure the company owns IP from founders, employees and contractors through written assignments.
Core contracts, privacy practices, tax registrations and employment compliance should be in place early.
Use templates as a starting point but take qualified legal and tax advice.
For AI-assisted work, record human contribution, check tool terms on ownership and training, and state your AI-use position in contracts.

Complete the legal checklist for your business or idea and create a dated plan for the missing items, including which adviser you will consult.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.

Contracts, intellectual property and compliance basics