This is a guided route from the operating know-how Adam carries in his head to a value-creation engine that works without him. It is the work to do first, before recruiting operators, buying more companies, or scaling a platform.
How to use this
Move one step at a time. Turn on Edit to shape the words in your own language. Turn on Facilitator to run the conversation with prompts.
The proof ladder
This is the whole route in one picture. The $15M outcome sits at the top, but we can't jump to it. Each rung only holds if the one beneath it is true, so the work runs bottom to top. Tap a rung to see why it matters.
Rung 0{{ ladderSelNum }} · {{ ladderSelName }}
{{ ladderSelWhy }}
02 · The big question
How do we create a path for Eric and Lil to produce $15 million of liquidity for their family over the next 10 years?
That is the right destination. It is not yet the strategy.
North star
$15M family liquidity over 10 years.
Crux
The pivotal solvable challenge that makes the north star plausible.
Don't chase the number. Solve the bottleneck that could make the number real.
03 · North star vs crux
A crux is the one specific, solvable challenge that unlocks everything above it.
A spreadsheet is not proof.
A platform name is not a strategy.
The same situation, framed three ways
Each reframe is more precise and more solvable than the last. The goal is to move from the frame that sounds strategic to the one we can actually start on.
{{ reframeKicker }}
{{ reframeText }}
{{ reframeWhy }}
Do we affirm this?
Codify before recruit. Make Adam's operating system portable before recruiting, launching, or scaling.
What we affirm or flag here is compiled on the Commit page.
04 · The hidden object
The operating knowledge Adam uses on instinct: training, quality control, job-site judgment, referral-partner trust, customer handoffs, compensation logic, operator coaching, and field-level standards.
"I have it because I am it."
It lives inside Adam. Powerful, but not scalable. While it stays tacit, every new operator depends on Adam's calendar.
The source code · eight modules
Each module is a piece of judgment Adam runs on instinct. The work is the same in every one: turn what he does on instinct into an artifact someone else can use. Here is the whole system, laid open.
Rank them together: move the hardest to codify to the top. Your order is compiled on the Commit page.
{{ m.tacit }}
05 · Tacit to explicit
Codification is a process, not a document. We pull the judgment out of Adam's head, pressure-test it, and package it into forms a stranger can follow.
Two layers, not one
What Adam knows is mostly trade-general: how to train a crew, hold quality, price work, earn referral trust. That becomes a core playbook any home-services operator can start from. We then extract the operator's own field knowledge and fold it in, so a plumbing or insulation business gets a version shaped to its work.
Layer 1 · Core Adam playbook
Trade-general operating system.
The judgment that holds across any trade: training, QC, pricing logic, referral trust, handoffs, financial rhythm.
Layer 2 · Operator adaptation
Trade-specific version.
We extract the operator's own tacit knowledge and fold it into the core, so the result is a plumbing, insulation, or drywall playbook that fits the work.
A piece of judgment becomes a form
The conversion pipeline
Stage {{ pipeSelNum }} · {{ pipeSelLabel }}
{{ pipeSelEx }}
Tap a stage to see what it produces. The output is a core playbook a new operator can start from, then adapt.
A playbook is proven when a stranger can run it, not when it impresses the people who wrote it.
06 · Our seats
Adam framed this around Lil and Eric, and we appreciate that. But the real opportunity is a set of complementary seats: Adam holds the know-how, Eric turns it into a system, and Lil tests that system against the market. Two of those seats are ours.
Eric · the inside seat
Codifier and portfolio integrator.
Turns AdamOS into playbooks, scorecards, scripts, and financial cadence. Owns reporting, back-office systems, accountability, and execution rhythm.
The architect of the system first. That could grow into a COO role later, once the system exists to run.
Lil · the outside seat
Operator discovery and referral-market lead.
Finds and qualifies operating-partner candidates, tests the language that attracts builders not job-seekers, and feeds market signal back into the playbook.
Not a helper, not generic sales. She turns "the right who" into a testable profile and a real pipeline.
Adam knows the system. Eric codifies the system. Lil finds and qualifies the first user of the system.
The role map
Adam
Tacit know-how, vision, capital, culture, opportunity judgment.
Eric
Codifier, integrator, cadence architect.
Lil
Operator discovery and referral-market lead.
Operator
First user of the codified system.
Lil scouts while we codify, but does not sell or close before the role, wedge, script, and first playbook modules are clear. Any role scope or compensation is conceptual and needs the right advisors.
Do we affirm this?
These are our seats: Eric codifies the system, Lil runs operator discovery, Adam supplies the know-how.
What you affirm or flag here is compiled on the Commit page.
07 · Codify before recruit
Path A · Recruit first
Operator apprentices to Adam.
Adam stays the bottleneck.
Success depends on personality fit.
Hard to repeat across brands.
Path B · Codify first
Operator receives a playbook.
Hiring criteria become clearer.
Training becomes testable.
The system improves over time.
What would you rather test first?
{{ choiceReveal }}
08 · First proof wedge
A good wedge is narrow enough to test, meaningful enough to matter, and clear enough to reveal whether the system works.
Drywall looks like a candidate wedge, based on our prior discussion. A hypothesis to test, not a decision.
Proof-wedge scorecard
{{ wedgeTally }}
Score each criterion together. Nothing is pre-decided. Leave a row unsure if we honestly don't know yet.
A scorecard is a conversation, not a verdict. A real wedge decision needs Adam in the room.
09 · The evidence frame
Our plan ties our economics to revenue and EBITDA milestones, not to time or the number of entities. The upside is earned by value created, not effort spent.
The value-creation ladder · tap a rung
Rung {{ valSelNum }} · {{ valSelLabel }}
{{ valSelWhy }}
Metrics that should move
First-pass financial cases
Companies
{{ caseCompanies }}
Yr 10 revenue
{{ caseRevenue }}
Yr 10 EBITDA
{{ caseEbitda }}
Eric vested
{{ caseVested }}
Family net liquidity
{{ caseLiquidity }}
Strategic implication
{{ caseImplication }}
Revenue and EBITDA are illustrative first-pass assumptions for discussion, not forecasts. Liquidity and company counts are drawn from Adam's plan and the crux analyses.
Conceptual only. Requires partner, CPA, tax, accounting, securities, employment, and legal review before implementation.
10 · True-equity wealth conversion
The plan's preferred structure is a profits interest: non-voting equity that pays out only on value created above a set threshold. Adam keeps control, capital authority, and first claim on returns. The family shares in the upside beyond that line.
Eric and Lil are building toward one number together: $15M in liquid wealth for the family. How each person's contribution is papered is a detail for the advisors, not a line that divides the goal.
The waterfall
Conceptual only. Requires partner, CPA, tax, accounting, securities, employment, and legal review before implementation.
11 · Platform scale comes last
Don't start by building the platform. Start with proof. Each step up in company count has to be earned, not assumed. The conditions live on the ladder below.
Each jump is a gate, not a step. The conditions to its right must be true before it is earned.
{{ s.label }}
{{ s.gate }}
Operating-partner pods can support 3–4 companies each if the model works, with Eric becoming head of the operating system rather than the sole executor. A future scaling mechanism, not a current commitment.
12 · Anti-frames
Tap a card to see what it misses and the better reframe.
Which one are we most likely to slip into?
Naming it is how we guard against it. Your pick is compiled on the Commit page.
13 · The next solvable move
Eric extracts the system from Adam's head while Lil tests the operator market against it. The two tracks run together and meet at a single decision gate in week 12.
Eric's track · AdamOS extraction
{{ ph.weeks }}
{{ ph.title }}
{{ it }}
Lil's track · operator discovery
{{ ph.weeks }}
{{ ph.title }}
{{ it }}
The guardrail: Lil can scout before AdamOS v1 is complete, but does not sell or close before the role, wedge, script, and first playbook modules are clear. Momentum, without letting momentum become noise.
Any role scope, project fee, success pay, or longer-term stake is conceptual only and needs the right legal, tax, and employment advisors.
14 · Commit
One page that compiles the route: what we took from the conversation, how we'd frame the work, where it goes, and the first 90 days. A working draft, in the same posture as everything here. React to it, edit it, and read it back before the conversation with Adam.
End-of-conversation memo · working draft
Adam, Eric, Lil
What we heard
$15M of family liquidity over 10 years is the right north star, and the question is sincere: how do we get Eric and Lil there.
Adam is service-oriented and focused on Lil and Eric. The posture is generous, and the goal is something we build together.
The pull is toward action: find the operator, launch the platform, buy companies. That pull is the risk.
Lil has real urgency and real market instinct. Her seat needs to be named and scoped, not absorbed.
The crux we framed
Codify before recruit. The first solvable move is making Adam's operating system portable, not finding the operator or building the platform.
The vision, if the system proves portable
AdamOS becomes a portable playbook. A non-Adam operator uses it. EBITDA improves. That value converts into liquidity for the family. Only then does the platform earn its scale, on the ladder's terms, not before.
The plan, in one breath
A 90-day proof sprint, two tracks. Eric extracts and codifies AdamOS. Lil tests the operator market against it, inside the guardrail. Both meet at a single decision gate in week 12.
What we are not committing to yet
Launching Uncommon, hiring an operator, naming a final wedge, or making any equity or compensation commitment. Those decisions wait for evidence the sprint is built to produce.
The decision in front of us
Run the 90-day proof sprint, or not. Everything else is downstream of that one yes.
What we marked together
Nothing marked yet. As you affirm, flag, rank, and pick across the route, your decisions compile here.
Affirmed
✓{{ a.label }}
Flagged to revisit
!{{ a.label }}
Where we lean
{{ s.label }}: {{ s.value }}
TALK TRACK
"I think the $15M question is the right north star. My biggest reaction is that the first move may not be building the full Uncommon platform yet. The real first crux is extracting your operating system, the training, QC, referral-partner model, compensation logic, customer handoffs, and decision rules, so it can live outside your head. If we turn that into a playbook someone else can execute, then recruiting operators, launching brands, and building a portfolio become far more credible. If we skip that step, I worry we're just scaling Adam-dependence."
The next step is a draft sprint charter for the first 90 days.
A working draft you can react to and edit, in the same posture as this route. It scopes the work, prices it, and names the decision. Print-clean.
A first-pass conversation tool distilled from Adam's plan, the P7 crux analysis, the prior crux analysis, and the reference-frame learning route. Not a decision, a forecast, or legal, tax, accounting, securities, employment, or investment advice. Treat every number and structure as a hypothesis to pressure-test.