[PROSPECT NAME]'s Frameworks. Our Infrastructure. One Asset We Build and Own Together.
[LLM: Personalized opening explaining the JV. Reference their specific frameworks, audience size, existing systems. This is NOT a template—it's a venture proposal. Show them what co-ownership looks like WITH their brand, their audience, their methodology.]
[LLM: Address their current ceiling. If they've tried off-the-shelf tools before, acknowledge it. If they have existing AI work, reference it. Make this feel like a progression, not a cold pitch.]
🎯 1+1+1=4 ECONOMICS FOCUSLead with the WIN-WIN-WIN, not the tool: Their audience gets [frameworks] via AI (better/faster/cheaper). They scale impact WITHOUT more time (leverage). We build a repeatable, exit-ready venture. Make CRYSTAL CLEAR: this multiplies revenue per hour, frees bandwidth, and naturally positions them as the authority for adjacent products. REFERENCE SPECIFICS: their current $X pricing, how this stacks, what gets replaced, why their audience will pay for scalable access. THIS is NOT about features. It's about economics and leverage.
01
The Model
This Isn't Software You Buy. It's a Venture We Build Together.
[LLM: Explain the core value. 3-layer IP split. No upfront cost. Why this structure works specifically for their situation.]
Their Domain IP
[Their Methodology Name]
[LLM: Describe their frameworks/expertise. Their frameworks, methodology, voice. The transformation they've proven works. How it stays theirs.]
Our Structural IP
The Architecture
[LLM: Business structure, JV framing, growth planning, exit strategy thinking. How we structure ventures for long-term value.]
Our Technology
The Infrastructure
[LLM: AI extraction, heuristic scoring, thinking-pattern replication. Why this beats GPT-based tools. Model-agnostic future-proofing.]
[LLM: Credibility callout]
[LLM: Why their existing audience is the leverage. How this model works because they've already built trust.]
💡 THE 1+1+1=4 MODEL (This is the core)THEM: Domain IP + Audience + Distribution (they keep all IP, we don't touch their coaching/events) US: AI extraction + Business structure (exit-ready ventures, not just tools) AUDIENCE: Scalable access to their frameworks (they get better outcomes, faster, cheaper than 1-on-1) CROSS-SELL: Adjacent products become natural recommendations to an engaged audience
KEY MESSAGING: "This isn't a tool. It's a venture where everyone wins because we're solving THEIR audience's ceiling (access + time) while freeing YOUR time and multiplying revenue per hour."
What It Actually Looks Like
Not a Chatbot. A System That Thinks Like [PROSPECT].
[LLM: Explain the difference between off-the-shelf and custom heuristic scoring. Make the technical part understandable.]
[%]
[Metric 1]
[#]
[Metric 2]
[#]
[Metric 3]
0
Generic Answers Allowed
Sample Interaction
[LLM: Scenario title from their domain]
[PROSPECT NAME] Clone — [TIME]
U
[LLM: Realistic user question in their domain. Deep, specific, not surface-level.]
AI
[LLM: Show the internal scoring pass. "Scored generic answer 12/100. Routing to Socratic depth..."]
[LLM: AI response that demonstrates THEIR thinking pattern. Socratic, not prescriptive. First-principles reasoning. Their voice, not a placeholder.]
Why this isn't another chatbot answer
[LLM: Explain the scoring rubric. Why generic answers get rejected. What makes this response sound like THEM.]
02
Current Pipeline
[#]ventures in active build
Domains We're Currently Building In
[LLM: Where [PROSPECT] fits. What other domains we're active in. How adjacent frameworks create cross-sell opportunities.]
Proposed
[PROSPECT NAME]
[Domain]
[Venture Name]
[Domain]
[Venture Name]
[Domain]
[Venture Name]
[Domain]
[Venture Name]
[LLM: Cross-sell callout]
[LLM: Why this venture fits the stack. How [PROSPECT]'s audience discovers adjacent expertise. Mutual benefit.]
Founding partnership spots: [X of Y remaining]
🎯 PIPELINE CONTEXTShow momentum: What ventures are live? Beta? Planning? This demonstrates scale without being overwhelming. Scarcity dots should be realistic (not 7/7 remaining). The dashed "Proposed" card makes theirs feel imminent.
03
What's Expected
Not Heavy Lifting. But It Requires Showing Up.
[LLM: Calibrate expectations. Their business stays untouched. This is a new asset. What they MUST do vs what's optional.]
What They Bring
[Specific to their context]
[Specific thing] — [LLM: What exactly. Not generic. Refer to their actual content/systems]
[Specific thing] — [LLM: Framework walkthroughs, decision logic, how they think]
[Specific person/role] — [LLM: Who validates AI responses. Their integrator role]
[Their audience] — [LLM: How they distribute. Traffic they drive]
[What they've built] — [LLM: Past AI attempts. What worked. Where it hit ceiling]
Direct feedback — [LLM: What matters for iteration]
What We Bring
Structure + Technology
Venture framing — [LLM: Long-term value structure, not just monthly revenue]
Promo page — [LLM: Immediate asset for waitlist building]
[LLM: Honesty callout]
[LLM: "We don't have all answers" / "This model works when both sides are invested" / etc. Anti-sales stance.]
💡 EXPECTATION SETTINGBe specific and honest. "4-6 hours Week 1, then responsive turnaround" beats "very collaborative." "Direct feedback on AI voice" is better than "ongoing optimization." Remove uncertainty.
04
Partnership Arc
Start Simple. Formalize as It Earns.
[LLM: Why this phased approach. How it protects both sides. When formalization happens.]
Where We Start
[LLM: Phase name/timeline]
[LLM: Initial terms. Revenue share specifics. What "courting period" means for them.]
[LLM: Timeline/KPI targets.]
[LLM: Legal structure summary or next step]
As Revenue Hits Milestones
[LLM: Formalization trigger]
[LLM: What changes when you hit $X revenue or Y users. Governance structure. Terms evolution.]
[LLM: Or we part ways cleanly — no lock-in]
Long-Term
Exit-Ready Asset
[LLM: Their IP control. Veto power. Right of first refusal. How this is built for their optionality.]
Built to compound, not just transact
05
Launch Strategy
[PROSPECT]'s Audience Gets Introduced in Three Waves.
[LLM: Why this phased approach protects their brand. How each wave is validated before the next.]
Wave 1 — Inner Circle
[#] Hand-Picked People
[LLM: Who they are. Why this validates fast. "Is this you?" framing.]
[Timeline: 1-2 weeks]
Wave 2 — Early Access
[#] From Their Community
[LLM: Their mastermind members, core audience. How you frame early access as innovation, not beta test.]
[Timeline: 2-4 weeks]
Wave 3 — Full Launch
[LLM: Why the confidence at this point. Real usage validation. Launch positioning.]
Ongoing
🚀 LAUNCH POSITIONINGThis removes risk perception. Three waves = proven with real users before full market. "I built something new" beats "here's a startup." Each wave is a confidence building exercise.
06
The Process
What Actually Happens After They Apply
1
Apply
Quick Application
[LLM: What you evaluate. Quick overview of criteria.]
[PROSPECT] · [TIME]
2
Conversation
Alignment, Not a Pitch
[LLM: What you talk about. Methodology, business model, fit assessment.]
Both · [DURATION]
3
Agreement
Sign Revenue Share
[LLM: What the initial agreement covers. Rev share terms, targets, KPIs.]
Both parties
4
Week 1
Share IP + Onboarding
[LLM: What they provide. Podcasts, recordings, frameworks. Onboarding form specifics for their business.]
[PROSPECT] · [HOURS] total
5
Weeks 1-3
We Extract and Build
[LLM: What you're doing. Framework extraction, voice calibration. When they get early promo page.]
Us · they get promo page early
6
Week 3-4
Test and Refine Together
[LLM: What they validate. AI voice accuracy. GTM finalization. Pricing, offer structure.]
Both · [HOURS]
7
Week 4+
Launch
[LJM: Three-wave rollout. Revenue starts at full launch.]
Both
⏱️ TIMELINE SPECIFICITYDon't say "we'll figure it out." Give realistic days/weeks. "Week 1-3" + "4-6 hours" removes uncertainty. Journey steps should have owner labels (You / Us / Both).
07
Who Fits
We're Selective. This Has to Be Mutual.
[LLM: Why you turn down partnerships. Not about exclusivity. About fit. What doesn't work.]
→
[Criterion 1] — [LLM: Specific metric or signal relevant to their situation]
→
[Criterion 2] — [LLM: Why this matters]
→
[Criterion 3] — [LLM: Named methodology, existing framework, clear system]
→
[Criterion 4] — [LLM: Content depth. Specific number of source files or hours of recordings]
→
[Criterion 5] — [LLM: Who validates. Can be them or team member]
→
[Criterion 6] — [LLM: Responsiveness expectation. Not hours of time, but timely turnaround]
[LLM: Honesty about fit]
[LJM: "This works best when both sides are invested." Anti-sales language. Better to be honest and stay friends.]
🎯 ELIGIBILITY CRITERIAMake it scannable. 6 criteria with specific numbers/signals (not vague). This filters leads automatically and disqualifies tire-kickers early. It shows you have standards.
08
Straight Answers
Questions You Should Ask
[LLM: Specific, honest answer. Include numbers if relevant. Show you've thought this through.]
[LLM: Thoughtful response. Don't dodge. Show three-wave rollout prevents this.]
[LLM: Specific answer. Explain how this complements, not replaces, their 1-on-1 work.]
[LLM: Clear: nothing changes. Their coaching stays theirs. This is a new asset alongside.]
[LLM: Model-agnostic, moatable factors (thinking + relationships + taste), how you evolve with tech.]
[LLM: How your approach differs. Why heuristic scoring beats platform dependency. Concrete example.]
[LLM: Their IP stays theirs. Clear exit terms. No upfront cost = limited risk. No lock-in.]
[LLM: Is there a coaching community, workshop, or other entry point? Onramp to full partnership.]
❓ FAQ SPECIFICITYExtract from transcripts or anticipate from their objections. Each answer should be 2-3 sentences: specific claim + proof + next step. Avoid "we do X and it's great" — instead show HOW and WHY.
If This Makes Sense, Apply and Let's Build.
[LLM: Final momentum statement. They've seen the model. If it resonates, next step is application. Make it feel inevitable, not pushy.]
📋 TEMPLATE METADATAThis is the ACTUAL 8-section JV partnership template structure (as reverse-engineered from Brian/Cheri pages). Use this prescriptive version to show LLM where content should go. Sections: Hero + Model + Pipeline + What's Expected + Partnership Arc + Launch Strategy + Process + Who Fits + FAQ + CTA. Personalization depth is MAXIMUM — every LLM instruction should reference their specific context.