IP Ownership When You Hire A Fractional CTO

Hiring a fractional CTO can be a brilliant move when your startup is growing quickly, but you're not quite ready for a full-time technical leader.

They might shape your product roadmap, choose your stack, manage developers, review code, design architecture, speak to investors and even build parts of the platform themselves. That makes the role incredibly valuable - and also legally sensitive.

The key question is simple: does your startup actually own the code, architecture and strategy materials your fractional CTO creates? A properly drafted fractional CTO agreement in the UK can make that answer clear from day one.

What Is A Fractional CTO Agreement?

A fractional CTO agreement is a contract between your startup and a part-time or external Chief Technology Officer that sets out their role, payment, confidentiality, IP ownership and exit rules.

Unlike a standard service agreement or consultancy agreement, this contract needs to deal with the fact that your CTO is likely to be close to the core of your business. They may have access to:

• Your product roadmap and technical strategy
• Source code, repositories and development environments
• Customer data, analytics and user behaviour insights
• Investor materials and fundraising plans
• Security information, API keys and cloud infrastructure
• Your team, supplier agreements and future hiring plans

Because of that, a generic contractor template often won't go far enough. It might cover fees and a basic confidentiality clause, but miss the things that matter most for a startup preparing to scale, raise funds or sell later.

A good consultant CTO agreement should answer practical questions like:

• What exactly is the CTO being hired to do?
• Who owns the code, architecture, documentation and technical strategy they create?
• Can they reuse tools, libraries or methods from other projects?
• What happens if you promise equity but the relationship ends early?
• Who controls access to GitHub, AWS, Google Cloud, Notion, Jira or similar systems?
• What happens when the engagement ends?

If you get these points clear early, you're not just avoiding legal headaches. You're making the business easier to fund, grow and eventually exit.

Who Owns The IP A Fractional CTO Creates?

Usually, your startup won't automatically own IP created by a fractional CTO unless there's a written assignment or the facts clearly support another arrangement.

This catches a lot of startups out. In the UK, the default position is different for employees and contractors.

For employees, copyright created in the course of employment usually belongs to the employer under the Copyright, Designs and Patents Act 1988, unless there's an agreement saying otherwise.

For contractors and consultants, the starting point is different. If your fractional CTO is engaged as an external consultant, they usually own the copyright in the materials they create unless they assign it to you in writing. A copyright assignment generally needs to be in writing and signed by the person assigning the rights.

That matters because your fractional CTO may create or contribute to:

• Source code and scripts
• Software architecture diagrams
• Technical specifications
• Database structures and schema designs
• AI prompts, models, training materials or system instructions
• Product roadmaps and feature prioritisation documents
• Security processes and deployment procedures

Say Priya runs a SaaS startup. She hires Theo as a fractional CTO for two days a week over 12 weeks. Theo designs the architecture, writes several key backend modules and prepares a technical roadmap for investors. Priya pays every invoice on time, totalling £16,800 plus VAT.

If their contract only says Theo will provide CTO services, but doesn't assign IP to the company, Priya may not fully own the materials Theo created. She may have an implied copyright licence to use them, but that can be much weaker than ownership. If an investor asks for proof that the company owns its core technology, Priya could be stuck trying to fix the paperwork under pressure.

The cleaner approach is to include a technology consultant IP assignment from the start, covering both work created during the engagement and any relevant work already created specifically for your startup.

What IP Should Your Startup Capture In The Agreement?

Your agreement should capture all IP and work product your fractional CTO creates for your business, not just finished code.

Founders often focus on source code, which makes sense. But a CTO's value is usually much broader than writing code. They may create the technical thinking that makes your product valuable, fundable or scalable.

Your agreement should clearly cover:

• Code: source code, object code, scripts, plugins, integrations and configuration files.
• Architecture: system designs, diagrams, infrastructure plans and data flows.
• Product Materials: technical roadmaps, feature specifications, backlog structures and user stories.
• Documentation: deployment notes, security procedures, API documentation and onboarding guides for developers.
• Data And Databases: database structures, data models and materials that may attract database rights.
• AI And Automation Materials: prompts, workflows, model instructions, evaluation frameworks and internal AI tooling created for your business.
• Confidential Know-How: non-public technical methods, commercial strategy and product decisions.

You should also deal with what isn't being assigned. A fractional CTO may bring their own pre-existing tools, libraries, snippets, templates or frameworks. That isn't always a problem, but your contract should say what those materials are and what rights your startup has to use them.

For example, your contract might say the CTO keeps ownership of their pre-existing toolkit, but gives your company a broad licence to use any parts embedded in your product. The licence should be wide enough for your business to operate, modify, commercialise, sublicense to customers where needed, and transfer the product if you sell the company.

If open-source software is involved, your agreement should also require the CTO to follow an approved open-source policy. Some licences can affect how your product is distributed or disclosed, so you don't want open-source choices being made casually inside your core platform.

How Do You Deal With Equity Promises And Contractor Status?

You should deal with equity promises in writing before work starts, because informal promises can create confusion about ownership, payment and expectations.

This is especially common with fractional CTOs. You might agree a lower cash fee because they will receive shares later. Or you might discuss a CTO becoming a technical co-founder if things go well.

The risk isn't that equity is always a bad idea. It can be a smart way to align incentives. The risk is leaving it vague.

Equity Promises Need Clear Terms

If you're offering shares or options, your documents should cover:

• How much equity is being offered
• Whether it's shares, options or a future right to receive shares
• What the CTO needs to do to earn it under an advisor equity arrangement
• Whether equity vests over time or milestones
• What happens if the CTO leaves early
• Whether the company can buy back unvested or leaver shares
• What approvals and filings are needed

If you issue shares in a UK company, you'll usually need to update your register of members and file a return of allotment, Form SH01, with Companies House within one month of the allotment. Depending on the size of the shareholding, your PSC register may also need updating. You may also need board and shareholder approvals under your articles of association and shareholders agreement.

If you're considering EMI options or another share option arrangement, get tax and accounting advice as well as legal advice. HMRC rules can be technical, and the tax position can change depending on the company's circumstances and the CTO's status.

Contractor Status Still Matters

Your contract should also reflect whether your fractional CTO is genuinely a contractor, a worker or an employee in practice. The label in the agreement helps, but it isn't the whole answer.

In the UK, employment status can affect rights under the Employment Rights Act 1996 and related laws. HMRC status and off-payroll working rules can also be relevant, especially where the CTO works through a personal service company. This is an area where tailored advice is worth getting if the arrangement is close to full-time, exclusive or highly controlled.

From a practical perspective, make sure the contract matches how you actually work together. If you say the CTO controls their own hours but you require them online 9 to 5 every weekday and manage them like staff, that inconsistency can cause problems later.

What Should A Fractional CTO Contract Include?

A fractional CTO contract should include the usual commercial terms plus specific clauses for IP, confidentiality, systems access, equity and exit arrangements.

Here is a practical outline you can use when thinking through the document. This isn't a finished contract, and it should be tailored by a lawyer before you use it, but it will help you spot the key moving parts.

1. Parties: State your company name, company number and the CTO's legal name or company details.
2. Role And Scope: Describe the CTO services, such as architecture, code review, hiring support, roadmap planning or investor technical support.
3. Time Commitment: Set out expected days, hours, availability and any response times for urgent issues.
4. Fees And Expenses: Explain the day rate, monthly retainer, invoicing cycle, VAT position and approved expenses.
5. Deliverables: List any concrete outputs, such as architecture diagrams, audit reports, sprint plans, repository setup or technical due diligence materials.
6. IP Assignment: Assign all IP in work created for your business to your company, ideally as soon as it is created.
7. Pre-Existing Materials: Identify any tools, code or frameworks the CTO already owns and set out the licence your company receives.
8. Open-Source Rules: Require approval before using open-source components that could affect your product or customer obligations.
9. Confidentiality: Protect your code, product plans, customer data, security information, financials and investor materials.
10. Data Protection: Deal with UK GDPR and the Data Protection Act 2018, especially if the CTO can access personal data or production systems.
11. Security And Access: Cover MFA, password managers, device security, admin rights, key rotation and return or deletion of materials.
12. Equity Or Options: State whether any equity is being offered and link to the right shareholder, option or vesting documents.
13. Conflicts: Restrict work for direct competitors or projects that create a conflict with your startup.
14. Termination: Set notice periods, immediate termination triggers and what happens to unfinished work.
15. Exit Handover: Require documentation, credential transfer, repository handover and reasonable support during transition.

The IP clause is usually the centrepiece, but the surrounding clauses matter too. For example, an assignment won't help much if the CTO is the only person with access to your cloud account, or if they used a third-party contractor without a clear subcontractor agreement or IP assignment.

What If You Have Already Started Without An Agreement?

If you've already started without a signed agreement, deal with it now rather than waiting for a funding round, dispute or handover problem.

This is more common than you might think. Early-stage startups move quickly, and it can feel awkward to raise legal paperwork after someone has already been helping for weeks or months. Still, it's usually easier to fix while the relationship is friendly.

Start with these steps:

1. Map The Work: List what the CTO has created or contributed to, including code, architecture, documents, roadmaps and account setups.
2. Check Existing Messages: Review emails, Slack messages, proposals and invoices to see what was agreed about ownership, payment and equity.
3. Identify Third-Party Materials: Ask whether any code, templates, open-source components, subcontractors or pre-existing tools were used.
4. Prepare A Deed Or Assignment: Put a written IP assignment in place covering past and future work, signed by the right person or company.
5. Fix Access Control: Make sure your company owns the main repositories, cloud accounts, domains and admin credentials.
6. Document Equity Separately: If equity was discussed, record exactly what has and hasn't been agreed before issuing shares or options.

Try to avoid presenting this as a lack of trust. You can frame it as investor-readiness and good governance. Most experienced fractional CTOs will understand that a startup needs clean IP ownership to raise money, bring in customers and protect the team.

If there's already tension, be careful with how you approach it. Keep a clear record of what has been created, what has been paid for and what access the CTO holds. If you're worried they may restrict access to systems or repositories, get advice before making sudden changes.

Key Takeaways

• A fractional CTO can create valuable IP beyond code, including architecture, roadmaps, documentation and technical strategy.
• In the UK, contractors usually keep ownership of copyright unless there's a written assignment transferring it to your company.
• Your agreement should deal with pre-existing tools, open-source software, confidentiality, data protection and systems access.
• Equity promises should be documented clearly, especially if shares or options vest over time or depend on milestones.
• If work has already started, you can often clean things up with a written IP assignment and proper handover process.
• Documents work best when they match how your CTO relationship actually operates in practice.

If you'd like help with your fractional CTO contract, IP ownership clauses, equity arrangements or technology consultant handover process, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.