A Business Model That Requires Optionality
I run a specialized consulting practice serving insurance carriers, insurtechs, and adjacent companies. My focus areas include non-standard auto insurance, performance marketing, and AI implementation. The value proposition depends on working across the ecosystem: learning from multiple carriers, seeing patterns others miss, and bringing insights from one engagement to the next.
At any given time, I have four to six concurrent clients generating meaningful monthly revenue. Each engagement comes with a contract, and every contract carries risk.
The specific risks for a multi-client practice:
- IP assignment clauses that claim ownership of methodologies developed during the engagement
- Non-compete provisions that prevent working with other carriers
- Exclusivity language that sounds reasonable but boxes you into a single relationship
- Termination clauses that give the client all the flexibility and leave you exposed
I needed a way to review every contract carefully, identify every problematic clause, and respond with specific counter-language. And I needed to do it without spending $500-600 per hour on outside counsel for routine reviews.
Building a Contract Review Protocol with AI
The approach is straightforward. I created a dedicated Claude project for contract review, seeded with several examples of existing agreements - some of which outside legal counsel had reviewed - along with a guidelines document containing my personal standards: deal-breaker thresholds, preferred language for key provisions, common consulting agreement pitfalls, and acceptable risk tolerances.
When a new contract arrives, I load it into the project. The AI identifies issues against my documented standards, categorizes them by severity (deal-breaker, significant, minor), and drafts specific counter-language for each problematic clause.
What the Guidelines Document Contains
- IP ownership standards: what I assign to clients versus what I retain
- Non-compete and exclusivity boundaries: what I will and won't agree to
- Termination requirements: mutual rights, reasonable notice periods
- Liability caps: appropriate risk allocation for advisory work
- Confidentiality parameters: protecting client information without restricting my practice
- Template counter-language for common issues
The Review Process
The key is specificity. Clients respond better to "here's the exact language I'd propose" than to "this clause is problematic." The AI helps generate that specific language quickly, drawing on patterns from prior negotiations stored in the project context.
Four Negotiations, Three Lessons
| Deal | Outcome | Timeline | Scale |
|---|---|---|---|
| Regional carrier, D2C strategy | Signed | 1 week, single counter | $$$ |
| Venture-backed AI company, advisor role | Signed | 72 hours | $ |
| Top 10 carrier, strategic engagement | Signed | Standard process | $$ |
| Insurtech partnership | Never signed | 12 months total | $ + equity |
The Regional Carrier: 17 Issues, One Week
The initial agreement included a two-year non-compete that would have prevented me from working with any carrier in my core market. It also contained an IP assignment clause claiming ownership of all materials created "during the performance" of the agreement, which would have included every methodology, framework, and tool I refined while serving them.
I loaded the contract into the AI project, got back a categorized issue log, and sent a comprehensive counter-proposal with specific alternative language for each problematic clause. Seventeen issues total, three deal-breakers.
Their Associate General Counsel's response to the IP ownership counter-proposal: "We accepted your changes."
One week from receiving the draft to signed agreement. One round of counter-proposals. The specific language I proposed became the final language in the contract.
The Venture-Backed Advisor Role: 72 Hours
A different challenge: the original contract had a zero-day termination clause (either party could terminate immediately, without notice), a competitive activities restriction that contradicted the CEO's written confirmation that they had "no exclusivity expectations," and an IP assignment scope broad enough to capture pre-existing methodologies.
Same process: load contract, generate issue analysis, and draft counter-language. I flagged the contradiction between the CEO's email and the contract language, proposed specific modifications, and provided exact alternative clauses.
72 hours from concern identification to executed contract with all modifications accepted.
The Top 10 Carrier: The Door That Stayed Open
This engagement came through a staffing platform, so the contract terms were largely standard. What matters is that it happened at all.
The engagement put me in front of C-suite executives at a major carrier exploring strategic expansion. The kind of relationship that compounds over time.
It would not have been possible if I had signed a category exclusivity clause with the insurtech partner whose deal stalled. Their proposed language would have prevented this engagement entirely. This door would have been closed before I knew it existed.
The insurtech partnership looked promising. Equity upside. Genuine alignment on market approach. I invested three months of free advisory work building the relationship. Then five months of contract negotiation. We were 98% agreed.
The sticking point: they wanted category exclusivity. I proposed narrower language - direct competitive overlap only, not the entire market segment. They took the ball to legal for "final review."
Four months of silence followed. Terms 98% agreed. Never signed.
Twelve months total. Far longer than the other three deals combined.
How a Contract Clause Enabled a Business Decision
Several months after signing the regional carrier agreement, I faced a strategic decision. I had been developing expertise in an emerging field known as Answer Engine Optimization - optimizing content to be surfaced by AI assistants. The methodology crystallized unexpectedly: I used Perplexity to troubleshoot my espresso machine, and it not only diagnosed the problem but recommended a local repair provider. The implications for customer acquisition were immediate.
The question became: should I offer this as a consulting service, or build it into owned properties?
The service model means trading expertise for fees. The asset model means building properties I own, proving the methodology works, then approaching carriers with demonstrated volume rather than theoretical capability.
The answer depended on a legal question: who owns the methodology?
I went back to the carrier contract I had negotiated. The IP ownership clause I had proposed - and they had accepted - explicitly stated that I retain ownership of:
- Pre-existing methodologies, frameworks, and tools
- General consulting knowledge and expertise
- Materials that can be used across multiple clients without revealing confidential information
- Templates and approaches refined during but not specific to their engagement
Work product specific to their business belongs to them. Methodology in my head belongs to me. Properties I build independently are clean.
Without that negotiated language, the answer would have been ambiguous at best. With it, I have optionality. I can pursue the asset model, the service model, or both.
Avoiding any expectation of exclusivity is essential to maintain the options that not only provide revenue, but also the field in which seeds of new ideas are planted, watered, and harvested.
What Transfers to Other Operators
Create a guidelines document with your deal-breakers, acceptable terms, and preferred language. The AI review is only as good as the standards you give it.
"We accepted your changes" only happens when you propose exact alternative language. Conceptual pushback creates negotiation cycles. Specific counter-proposals close deals.
Standard "work made for hire" clauses are overbroad. Propose carve-outs for pre-existing frameworks, general expertise, and materials usable across clients. Include a license-back provision so clients can use your methods in their deliverables without owning them outright.
Category exclusivity sounds reasonable in negotiation. It becomes a constraint when the next opportunity arrives. Narrow the scope: specific competitive overlap, not entire market segments.
Twelve months and 98% agreement means nothing if the contract never signs. Stalled negotiations have opportunity costs. Sometimes the lesson is that the deal was never going to close.
A multi-client consulting practice with protected methodology ownership, preserved optionality across market segments, and the freedom to pursue emerging opportunities - including building proprietary approaches that would have been legally ambiguous under standard contract terms.