Deal Structure & Partnership Model

The real deal template and the equity-for-engine partnership model behind every vertical.

CURRENT — working framework

Every business has the same problems: get found, convert, follow up, keep the brand coherent while doing it. The Brand Builder Engine solves those as owned, reusable infrastructure. That is why the engine is worth equity in any venture built on top of it: I perfect the engine and stay the engine, partners bring vertical expertise, distribution, and operating capacity, together we spin up profitable brands fast, I take cash plus equity for bringing 80% of the product to the table on day one, and the engine compounds with every deal instead of being rebuilt for each one.

This is the venture-studio move. The engine is the studio. Partners are the operators.

Why this works now

AI collapsed the build constraint. Proven solo: the entire Bex platform (85 pages, 4 days), the Follow-Up engine live on real data, Brand With AI in public beta with a money rail, the Theme /system live, full Cloudflare infrastructure. The old “I design, someone else devs” split is dead. What remains scarce, and what partners must bring, is everything AI can’t generate: clients, capital, domain knowledge, and someone to carry the pager.

What BBE brings to any deal

Piece	What it does in a partner venture	Proof
Brand Brain	The venture’s brand knows itself, one source of truth	DH-Brand-Record, 15 layers
Identity system	Skin any surface from one pack, swap in minutes	9 packs live, verified rebrand cascade
The Theme	Any Identity renders clean on any property	/system live on share.designhacker.com
The Platform	Notion in, full marketing site out, days not months	bexandcosalon.com, 85 pages, 4 days
The Follow-Up	List in, money-making activities out, consent-first	Live on real Bex data
Brand With AI	The public factory that manufactures Identities	brandwithai.com, live beta
The playbook	Templatized spin-up: interview to staging in a day	Ship plan §7, extraction post-DH-launch

A partner venture skips 6-12 months and six figures of build. That’s the equity argument, stated plainly, backed by live URLs.

The five rules (non-negotiable, learned the hard way)

Equity plus cash, every time

Setup fee + monthly retainer covers cost and keeps the engine funded. Equity is the upside kicker, never the whole payment. Comp: Valley Home at $15k build + $2,500/mo. A partner who won’t pay anything today usually can’t sell anything tomorrow.

One deal template, many instances

The structure gets written once. Every new vertical is fill-in-the-blanks, never a fresh negotiation. Locked schema plus locked deal shape is the defense against the Landon failure mode (working system, rebuilt 3x, founder-locked).

The engine stays ONE codebase

Verticals get packs, config, and content models. They never get forks. The moment a partner convinces us to fork core, leverage divides instead of multiplies.

Background IP is licensed in, never assigned

If the venture dies, the IP comes home. If the venture wins, they still don’t own the engine. Their vertical-specific layer (their pack, their content, their domain assets) is theirs.

Cap active verticals

Andrew is the sole integrator, the named thin spot. Hard test for every partner: can they RUN the vertical without me? If no, the equity comes with a job attached, and the answer is no.

The partner test (three boxes, all required)

Domain expertise. They know the vertical’s customers, economics, and language cold.
Distribution. They bring the pipeline: clients, audience, network, or capital.
Operator capacity. They can run the business day to day. Andrew stays the engine.

Anyone who checks one box is a client and pays full freight in cash. Two boxes, maybe, with a bigger cash component. Three boxes, that’s a vertical partner and the equity conversation opens.

Scorecard on people in the current orbit:

Bex — domain, distribution (30+ salons, franchise pipeline), operator, all checked. The template case. Already a paying client, the right order of operations.
Rene — distribution (investor network + client pipeline), operator (always-on infra, the pager). Domain depends on the vertical. Best fit: deal partner + heavy-infrastructure partner across ventures, plus the blogging vertical where his stack IS the domain.
Ed / Valley Home — domain and operator checked, local distribution. Cash-first client with the relationship upside. Correct as structured.
FranDevCo — near-clone of the Bex playbook. Prospect, sell outcomes now, build after DH is live.
so bexy — the vertical waiting on this model. Needs its operator identified before it reactivates.

What partners get, and what they never get

They get

A licensed instance of the engine wearing their brand, the spin-up playbook run for them, the Follow-Up desk on their data, ongoing engine improvements flowing downstream, and Andrew as design/brand/system authority on their venture.

They never get

The engine source as their property, a fork, exclusivity over the engine in their vertical (a priced, time-boxed exception if ever granted), or the right to resell the engine itself.

The legal concepts, in plain language

Background IP vs Foreground IP. Background IP is what each party owned BEFORE the deal (the engine, a partner’s tooling, a partner’s brand). Foreground IP is what gets created DURING the deal (the client’s site, the vertical’s content model). Every agreement names both explicitly. The engine is always Background IP.

License vs assignment. An assignment transfers ownership, gone forever. A license grants permission to use while ownership stays home. The engine is only ever LICENSED into ventures: non-exclusive, non-transferable, scoped to the venture, terminating if the venture dissolves or breaches. Delivered client work (their site, their pack) can be theirs outright; the engine underneath never is.

Derivative works and the fork rule. Improvements to core flow back to the engine (that’s the compounding); vertical-specific packs and content models belong to the vertical. Write it down, this is the #1 future-fight generator in IP deals.

Exclusivity. Default answer: no. If granted, it is PRICED and TIME-BOXED with performance minimums (keep exclusivity only while hitting revenue targets). Free, open-ended exclusivity is how the engine gets parked in a dead vertical.

Work-for-hire trap. Any contract calling Andrew’s contribution “work made for hire” assigns it away by default. Strike that language on sight wherever the engine is involved.

Equity mechanics to ask counsel about: sweat-equity grants get taxed as income at grant unless structured properly (83(b) timing on restricted stock, or profits interests in an LLC, the usual clean answer for this model). Vesting on BOTH sides protects everyone.

The standard deal template (fill in the blanks)

Parties + venture. Who, and the named vertical scope. Scope matters: the license covers THIS vertical, nothing wider.
Engine contribution (Background IP, licensed). Enumerate: Brand Brain pattern, Identity system, Theme /system, Platform engine, Follow-Up engine, playbooks. Attach as an exhibit so “the engine” is never vague.
Partner contribution. Domain expertise, named pipeline/distribution commitments, operating role. Make the distribution commitment CONCRETE (intros, first N clients, capital) so equity is earned by delivery, not by conversation.
Cash. Setup fee ($X, comp family: $15k) + monthly retainer ($X/mo, comp: $2,500). Payable regardless of equity.
Equity. Range 10-25% depending on how complete the engine’s head start is for that vertical, as profits interests or restricted units, vesting over 2-3 years, with anti-dilution basics per counsel.
IP terms. License grant + fork rule + improvements-flow-back + IP-comes-home-on-dissolution + no right to resell the engine.
Roles. Andrew is design/brand/system authority. Partner is the operator. Neither runs the other’s layer.
Exit. What happens on venture death (license ends, IP home), on sale (license survives or converts per counsel), on partner exit (vesting stops).

Paper weight by deal size: handshake for nothing, one-page MOU when work starts, counsel-drafted agreement the moment equity or an investor enters the room.

The pitch (how this sells)

The frame: the partner’s venture is the hero. BBE is the system underneath that removes 6-12 months and six figures of build risk on day one. Speed and execution language, never transformation promises.

Demo-first, always. The proof stack does the selling: bexandcosalon.com (85 pages, 4 days), the live Follow-Up desk on real data, brandwithai.com, and once shipped, designhacker.com itself. Screen share beats slide deck.

The pitch skeleton (60 seconds):

“Every business fights the same four problems: get found, convert, follow up, stay on-brand while scaling. I’ve built the engine that solves all four, and it’s live… here’s a franchise running on it, built in four days. When we launch your venture on it, you skip the year of tech build and start at the revenue conversation. You bring the vertical and the customers, I bring the engine and the brand system, we split cash and equity, and you own the business. I stay the engine.”

Objection: Can't we just own the tech?

“You own everything specific to your venture: brand, content, customers, the business itself. The engine stays mine and keeps improving under you for free. Owning a frozen copy would actually be worth less.”

Objection: Why cash AND equity?

“Cash keeps the engine funded and proves the venture is real. Equity aligns us long-term. Ventures that can’t fund a setup fee can’t fund customer acquisition either.”

Objection: Exclusive for our vertical?

“Exclusivity is available, priced, time-boxed, and tied to performance minimums. Keep it by hitting numbers.”

Investor-facing angle

If a partner’s network brings investment conversations, the structure that protects the engine: investors invest in the VERTICAL entity (so bexy Inc., the editorial venture, etc.), which holds a license to the engine. They never invest in, or take a security interest over, the engine itself. If someone insists on engine ownership as a condition, that’s a different (much bigger) conversation with counsel in the room from minute one. Keeping the cap tables of ventures separate from the engine is the whole ballgame for optionality later, including any future SaaS raise on BBE itself.

Sequence (do not reorder)

DH.com live. The ship plan’s four blocks. A live DH.com is the sales asset, so partner conversations become demos, never pitches.
Extract the starter + site-spinup skill from the proven instance.
Valley Home staging proves the templatized spin-up on a real deal.
Then open the vertical-partner conversations (Rene deal shape, so bexy operator hunt, FranDevCo) with three live proofs on screen.

Before the first signature, in order

Attorney reviews the deal template once (one-time cost, reused forever).
Decide the engine’s holding entity question (does BBE IP sit in a dedicated LLC that grants the licenses? Counsel call, likely yes eventually).
Run the IP organization cleanup so the Background IP exhibit is a clean, dated inventory instead of an archaeology project.
Then, and only then, partner conversations move from talk to paper.