Case study · AI consultancy
Bigger contracts, without losing the IP underneath them.
A growing AI and technology consultancy was moving from founder-led, relationship-based contracting to a scalable operating model — and enterprise customers were arriving with their own paper. Legal support became part of the growth infrastructure rather than a one-off documentation exercise.
- Enterprise MSAs
- Negotiated without giving away core IP
- Reusable IP
- Methodologies kept commercially reusable
- Flexible talent
- CTO, advisor and introducer structures
- Capped risk
- Liability sized to the value of the work
The risk
Winning the deal, losing the method.
Enterprise contracts routinely ask for ownership of everything created, broad licences over what already existed, uncapped liability and obligations passed down from a prime contractor. Signed as presented, they can transfer the very methodologies that make an AI consultancy valuable.
Terms that feel survivable at small contract values become material risks as revenue and customer dependency grow.
Before
Where the business stood
Customer contracting
- Founder-led, relationship-based agreements
- Enterprise buyers arriving with their own MSAs and flow-down terms
IP
- Proprietary methodologies, frameworks and readiness tools built informally
- No clear line between deliverables and reusable company assets
Partners and advisors
- Technical leadership and introducers engaged loosely
- Service delivery blurred with wider partnership expectations
Risk
- Uncapped liability and broad indemnities accepted to win work
- Obligations inherited from upstream contracting chains
After
Where the work landed
Customer contracting
- Scalable negotiating positions across enterprise agreements
- Flow-down and downstream obligations assessed before signature
IP
- Pre-existing, third-party, new, derivative and joint assets separated
- Usage rights sufficient to deliver, without transferring the methodology
Partners and advisors
- CTO services and collaboration frameworks reusable for future engagements
- Commission and introducer entitlements clearly defined
Risk
- Liability proportionate to fees; indemnities narrowed
- Termination and survival terms treated as risk controls
The result
Scale pursued, downside controlled.
The company could chase larger enterprise opportunities without customer contracts undermining its core IP. External advisors and technical specialists supported growth inside defined boundaries, and proprietary methodologies stayed reusable across the wider customer base.
The contracting infrastructure became suitable for a business preparing for greater scale, strategic investment or an eventual transaction.
How it was structured
Contracts, IP, partners, risk
As customers grew larger, contracts arrived as detailed master services agreements with project documentation, procurement standards and obligations flowing down from prime contractors. Each one increased revenue potential and downside exposure at the same time.
Work covered reviewing and negotiating customer MSAs, assessing downstream and flow-down obligations, and developing more scalable contractual positions — so the same issues did not have to be argued from scratch on every deal.
The business was developing proprietary AI methodologies, assessment frameworks, readiness tools, adapted products, customer-specific outputs and assets created with external collaborators. The contracts had to distinguish pre-existing company IP, third-party IP, newly created materials, derivative products, jointly developed assets and customer deliverables.
The commercial point: give customers enough usage rights to complete the project, without quietly transferring the underlying methodologies that create enterprise value. That preserved the ability to reuse core frameworks, commercialise methodologies across multiple customers and build repeatable products — so no single contract could erode the value of the wider business.
Rather than relying on exclusivity, the structure controlled use: defining permitted use of proprietary IP, separating client deliverables from reusable methodologies, limiting unintended rights over derivative products, clarifying ownership where external parties contributed, and keeping partnership discussions distinct from service arrangements. The purpose was to prevent relationship ambiguity, reduce IP and knowledge leakage, preserve freedom to work with other customers, and avoid handing over strategic rights through ordinary operational contracts.
Specialist technical leadership was accessed through external CTO and collaboration arrangements, with service obligations separated from broader partnership concepts — so capability could be brought in without creating unclear ownership or partnership rights.
Advisors and introducers could share in revenue from opportunities they originated, with agreements defining qualifying introductions, relevant projects, commission entitlements and continuing payment rights. Business development capacity grew without a fixed-cost sales organisation.
Larger relationships brought contractual approval processes, reporting requirements, audit provisions, information security obligations, compliance standards, project definitions and allocated responsibilities — often inherited from contracting chains above the customer. The aim was to keep commercial control while operating credibly inside sophisticated procurement environments.
Liability: uncapped exposure, caps disproportionate to project fees, extensive customer indemnities and obligations inherited from upstream contracts.
IP: broad customer licences, ownership language capturing existing methodologies, unclear derivative-work provisions and loss of reusable assets.
Operational: information security, audit obligations, compliance and customer-imposed standards.
Terms tolerable for a small consultancy become material risks once contract value, headcount and customer dependency increase.
Termination provisions were reviewed as part of the enterprise risk work rather than treated as boilerplate: the rights available to customers, the ability to exit a problematic relationship, the consequences of termination, continuing IP or payment obligations, and disproportionate obligations surviving the contract.
Strategic takeaway
What made the difference
Protect the asset
Guard the methodologies and frameworks that create long-term enterprise value, not every clause equally.
Borrow capability
External CTOs, advisors and introducers accelerate growth inside defined commercial boundaries.
Price the complexity
Accept enterprise obligations only where the contractual downside is controlled.
Build once
Repeatable structures put in place before volume makes bespoke contracting inefficient.
Result
Larger enterprise opportunities pursued without customer contracts undermining core IP.
Lasting value
Contracting infrastructure fit for greater scale, strategic investment or an eventual sale.
Details have been generalised to protect confidentiality. This case study is not legal advice.
What does your business need next?
No complicated brief required. Start with the problem.