Confidential · Partner Intelligence
A quick honesty note before the read: you've given me a lot — full 34s, full WG, real-world color commentary, and a defined CEO seat for Jak with Dawson in discovery. That lets me go deep. But these frameworks are dialogue tools, not selection instruments, and a two-year working history between you two will tell you more than anything below. Treat this as a map for conversations, not a verdict.
Let me also pull on the role thread immediately: Jak is named CEO/co-founder. Dawson is not assigned a seat. So the structure here is — evaluate Jak's fit in the CEO chair, then ask what shape Dawson most needs to take given Jak's wiring and the specific build path you've laid out (test kits → peptides → lab → 503B).
---
Jak is a vision-and-invention engine sitting in the CEO seat; Dawson is a galvanize-and-execute engine looking for his. That is one of the cleanest originate-to-activate handoffs the Working Genius model describes — if you consciously build the bridge and hire around the tenacity gap neither of you owns.
The deterministic read already flagged the near-mirror complement (3 of 6 stages) and the mirror-image crush buttons. That's the structural good news. The structural risk is also already on the table: neither of you has Tenacity or Enablement as a genius, and in a business that ends with a 503B pharmacy — which is fundamentally a tenacity-and-compliance grind — that's the single most important gap to name out loud before you incorporate.
---
Patrick Lencioni's model is fundamentally about energy, not capability. People can do work outside their genius; they just get drained doing it. Read this section as "where does the gas tank refill, and where does it leak."
Jak — Invention + Wonder (genius), Discernment + Enablement (competency), Tenacity + Galvanizing (frustration).
Jak is wired at the front end of work. Wonder asks "could this be better / what's possible here?" and Invention answers it with novel solutions. That's a founder-grade combination for the opening of a venture: spotting that test kits → peptides → lab → 503B is a coherent stack other people aren't seeing, and inventing the operational shape to make it work. Discernment in competency means Jak can sanity-check ideas (his own and others') with decent gut instinct, even if it's not where he gains energy. The frustrations matter: Galvanizing in frustration means rallying people repeatedly to action drains him, and Tenacity in frustration means the last-15% grind to ship drains him too. A CEO who is frustrated by both galvanizing and tenacity has to design around that — not pretend it away.
Dawson — Galvanizing + Discernment (genius), Tenacity + Enablement (competency), Invention + Wonder (frustration).
Dawson is wired at the back half of work. Discernment lets him judge which ideas are actually good; Galvanizing lets him rally people to go execute them. Tenacity sitting in competency (not frustration) is meaningful — he can push things across the finish line, he just doesn't gain energy from it the way a pure Tenacity-genius would. And the crush button: Invention and Wonder both in frustration means open-ended "what if we…" sessions exhaust him. He wants the question settled so he can go win.
The handoff. Jak invents and wonders. Dawson discerns whether it's the right move, then galvanizes the team to go. That's the textbook complement Lencioni describes as the most generative pairing — and it's also the one most likely to break down at the transition point. Jak will keep re-opening questions Dawson thought were closed; Dawson will push to execute before Jak feels the vision is fully formed. You will need an explicit "decision is made, we're moving" ritual — otherwise the mirror-image crush buttons become a chronic source of friction rather than a productive tension.
The team-level gap the deterministic read flagged: no one owns Enablement or Tenacity as a genius. Enablement is the "I'm in, how can I help" energy that keeps a team feeling supported. Tenacity is the finisher energy — the person who loves the last mile, the compliance audit, the punch list. In a 503B trajectory, where FDA compliance and cGMP documentation are the entire game, a Tenacity-genius operator is not a "nice to have" — it's the third hire after you two.I have enough to ground the dossier well. Let me write it.
---
The deterministic read flagged three shared top-10 themes: Belief, Strategic, Futuristic. That's a meaningful trio.
Belief is the values-anchor theme. Both of you make decisions through a values filter, not just an opportunity filter. In a venture that touches health, peptides, FDA-regulated pharmacy, that shared Belief is genuinely important — it means neither of you is likely to cut corners on the compliance side because "we're good people doing it right" is core to how you both operate. The risk is that Belief-Belief pairs can lock horns when their specific beliefs diverge. Get the values conversation out of the way explicitly — what do you stand for around quality, patient safety, marketing claims, what you won't sell, what you will? Don't assume alignment because the theme matches.
Strategic + Futuristic shared means you'll both see the chess board and the horizon. People exceptionally talented in the Futuristic theme are inspired by the future and what could be; they energize others with their visions of the future. That's both of you. You will have no trouble agreeing the venture could become something big. The risk is twin-Futuristic founders sometimes spend too much time in 2028 and not enough in next Tuesday — but Dawson's Achiever and Focus (#1 and #6) are the antidote there.
Where they diverge — and this is the gold:
Jak's stack is heavily Strategic Thinking + Influencing, with Belief as the lone executor up top. Belief, Strategic, Ideation, Futuristic, Adaptability, Woo, Individualization in the top 7 paints a picture of a founder-archetype CEO: values-anchored, visionary, idea-generative, networked, and adaptive in the moment. The construction and 503B operations background you described in the color commentary adds something the raw themes don't show — Jak has done the operational grind even though it isn't where his top themes pull him. That's a learned competency he can lean on, but probably not where he gains energy now.
Dawson's stack is dominantly Executing + Influencing-with-edge, with Strategic Thinking themes used in service of getting things done. Achiever #1, Relator #2, Arranger #4, Competition #5, Focus #6, Significance #7 — this is a get-it-done-with-the-right-people-and-win operator. Achiever #1 is meaningful: Achiever is the most common #1 theme globally, and people with it have a constant internal drive and high capacity for hard work, with roughly 1 in 3 people having Achiever in their Top 5. Combined with Arranger (orchestrating moving pieces) and Focus (goal-protection), Dawson is wired for operational throughput. Add Competition and Significance and you have someone who needs the scoreboard to be visible and the work to matter.
Shared blind spots in the bottom of both stacks. Look at where both of you are deep in the bottom-10: Discipline (Jak #31, Dawson #30), Consistency (Jak #34, Dawson #27), Harmony (Jak #32, Dawson #28), Context (Jak #26, Dawson #31). Neither of you is naturally a systematizer who builds repeatable rules and keeps the peace. In a 503B world built on SOPs, batch records, and uniform process — that gap is the same gap Tenacity+Enablement points to from the WG side. The frameworks corroborate.
---
They agree on the big things:
Where CliftonStrengths adds nuance WG misses:
Where WG adds nuance CliftonStrengths misses:
---
The wiring fits the external, visionary, originating CEO archetype well. Belief + Strategic + Ideation + Futuristic + Woo is almost a textbook founder-CEO stack. Look for roles that will let you contribute your ideas about the future — you might excel in entrepreneurial or startup situations. That's Jak.
The stretch for Jak in the CEO seat is the part of CEO that isn't vision — it's the galvanize-the-team-every-Monday, hold-people-accountable-to-the-finish part. Galvanizing in frustration is the watch-item here. Lencioni's framework points out that without good Discernment or Tenacity around them, inventors might leave a trail of half-finished brilliance. Jak's prior 503B/VP-Ops experience is a real asset — but it also means there's a temptation to take back operational ownership when things get messy. Resist that. The CEO seat for someone wired like Jak is best played as Chief Vision/Strategy/External Officer — capital, story, partnerships, the regulatory and facility chess game where his construction-and-503B history is gold — with operational execution genuinely delegated.
The Belief #1 + 503B + peptides combination is also worth saying out loud: peptides are a regulatory gray zone evolving fast. Jak's Belief will demand a clear ethical line. Decide it now, not under pressure later.
Jak owns vision, external, regulatory architecture, and the long-arc strategy. What the team most needs from the second seat is the person who turns that into shipped product, hit revenue, and a team that executes. Three functional shapes worth testing through real work, in rough order of fit:
1. The COO / Head of Operations & Commercial seat — the strongest hypothesis.
Dawson's Achiever-Arranger-Focus-Competition-Strategic-Belief-Deliberative top-10 is unusually well-matched to a COO profile in a multi-vertical, logistics-heavy build. His 3PL background, his actual experience in in-home test kits and peptides, and his Galvanizing+Discernment WG genius all point the same direction. The wiring points toward someone who can stand up the test-kit fulfillment engine, own the P&L on the first vertical, build the team, and hold the scoreboard. Discernment-as-genius means he can also serve as Jak's idea-filter — the "is this the right move?" voice Jak needs before committing capital. Worth noting: in one documented two-person team map, one founder immediately recognized that her partner's Discernment was exactly what frustrated her but it was also exactly what she needed for their business to be successful — she needed him to analyze her ideas and look for potential pitfalls before they both leaned into action. That's the dynamic available to you two if you build the ritual.
2. The President / Co-CEO of the first vertical — a variant worth considering.
If you want clearer ownership and Dawson has the appetite for full P&L, give him the test-kits vertical outright as President, with Jak as group CEO over the holding entity that includes the future lab and 503B. This plays harder to his Competition (#5) and Significance (#7) — he gets his own scoreboard and his own win. The risk is fragmenting decision-making too early; the upside is that it lets each of you operate in your zone with less collision.
3. Head of Revenue / Commercial — the narrower shape, only if #1 and #2 don't fit.
If operational ownership turns out to be the wrong fit given your real working history, Dawson's Galvanizing-Discernment-Relator-Competition-Achiever stack would also play well as the person who owns growth — building the commercial engine, partnerships, account relationships, sales team. This is a narrower seat than COO and probably under-uses his Arranger and 3PL background, but it's a viable fallback.
Hypothesis-framed, not verdict. All three are starting points to test against your real two-person working history. Run the first 90 days with the COO framing and see if the energy matches the theory.
Compliance documentation systems, SOP authorship, the cGMP-readiness paperwork engine for the 503B. Both your stacks say "find someone whose Tenacity-Enablement genius is real, whose Discipline and Consistency are top-10, and whose ego is fine being the third name on the cap table." This is your most important early hire — probably before you raise, certainly before you order lab equipment.
---
The pace/closure collision. Jak's Adaptability + Ideation will keep options open longer than Dawson's Focus + Deliberative wants. Dawson will feel like decisions keep re-opening. Jak will feel like Dawson is locking in prematurely. "What if…" — that's the Futurist painting a bold picture of what's possible and energizing the team with vision; but these big dreams can also be draining when you just need someone to execute a simple task on time, rather than imagining myriad alternatives. Build a "decision is closed" ritual — once you both agree a call is made, neither reopens it without a stated trigger.
The Significance / Competition / Belief triangle. Dawson's Competition #5 + Significance #7 needs visible wins. Jak's Belief #1 needs the work to matter morally. These can align beautifully (winning at meaningful work) or collide (Dawson wants to push aggressive growth, Jak says "not at the cost of values"). Talk about this before the first peptide marketing decision lands on the table.
The "we both think we know operations" trap. Jak ran 503B ops for two years. Dawson ran 3PL logistics and verticals. You will both have strong opinions on operational questions, and you don't have a tiebreaker. Decide ownership explicitly: who has the final call on facilities, vendors, fulfillment, QA, hiring? Don't leave it implicit.
The Tenacity/Enablement gap. Already said, saying it again because it's the most important structural finding. Finishers with the Tenacity genius have the energy, talent, and drive to get things across the goal line — all six types of working geniuses are required for getting work done successfully. Hire this person early.
The compliance-systematization gap (CliftonStrengths-side). Low Discipline + low Consistency in both stacks means neither of you will naturally build the rigorous, repeatable, fair-rules culture a 503B requires. This is the same gap as Tenacity/Enablement viewed from the other framework. One excellent hire can close both.
---
1. Have the Belief conversation. One sitting, two hours, no laptops. What are the values lines you both hold? What will you not sell? What's the brand promise on quality and safety across test kits, peptides, and eventually compounded products? Write it down. This becomes your decision filter when the first hard call comes.
2. Map the verticals to ownership now, even if rough. Test kits = ? Peptides commercial = ? Lab buildout = ? 503B = ? Don't leave it as "we'll figure it out." Use the wiring: Jak's construction + 503B history naturally pulls him toward facility, regulatory architecture, and the future-state lab/503B planning. Dawson's 3PL + test-kit + peptide experience pulls him toward standing up commercial operations on verticals one and two. Sketch it on paper.
3. Build the decision-rights doc. Three buckets: Jak decides alone, Dawson decides alone, decided together. Hiring above $X, capex above $Y, anything touching regulatory, anything touching brand. The mirror crush buttons mean you'll naturally encroach on each other's zones — the doc prevents it.
4. Make the Tenacity hire the next hire after you two. Job description: someone who loves the punch list, the SOP, the audit. Probably someone whose CliftonStrengths include Discipline, Responsibility, and Consistency in the top 10, and whose WG includes Tenacity (ideally with Enablement). This person is your operational backbone.
5. Run the Working Genius Team Map together. Both of you. Two hours with a certified facilitator if you can swing it. Use it specifically to talk about the mirror crush buttons — Jak's frustrations are Dawson's geniuses and vice versa — and design the handoff explicitly. This is the highest-leverage conversation you can have in your first 30 days as partners.
---
A final honest note: the structural read here is encouraging — complementary WG, shared values themes, real domain experience on both sides, and a coherent role logic. But the frameworks can't see your actual working chemistry, your equity split, your capital situation, or whether you'll handle the first real disagreement well. Treat everything above as hypotheses to pressure-test through real work, not conclusions. The next 90 days of doing this together will teach you more than any assessment can.
You've named the exact friction this pairing will produce, and you've named it early — which is the win. Let me sharpen what's actually happening underneath, because the fix has to match the mechanism.
What's driving the reopening behavior on Jak's side:
What's driving the closing behavior on Dawson's side:
This is the mirror-image crush-button dynamic the deterministic analysis flagged. It's not a personality clash; it's a predictable energy-flow collision. Good news: it's structurally solvable.
Separate the "open" surface from the "closed" surface. Don't try to make Jak stop ideating — you'll lose the thing that makes him valuable as CEO of a multi-vertical build. Give the ideation a container so it stops leaking into execution.
1. Weekly Invention slot (60–90 min, Jak-led, Dawson optional). This is where Jak's Ideation/Futuristic/Wonder runs free. New verticals, new angles on peptide sourcing, the 503B horizon, the lab build sequencing. Output: an "options parking lot" that's captured, not acted on. Jak's Input #11 will appreciate the artifact.
2. Weekly Operating Review (Dawson-led, 60 min, tight agenda). Status against committed decisions only. The rule: items on the parking lot don't enter this meeting unless they've cleared a gate (below). Dawson's Focus/Arranger/Achiever runs this cleanly.
3. Monthly Re-decision Gate (90 min, both, ritualized). This is the pressure valve. Anything from the parking lot that Jak genuinely believes should reopen a closed decision gets one slot here. Requirement to reopen: new information that wasn't available when the decision was made, not new ideation about it. This honors Jak's Adaptability (real signal from today gets a real hearing) while protecting Dawson from death by reconsideration. Decisions reopened: logged. Decisions reaffirmed: also logged — Dawson's Significance #7 and Achiever #1 want the receipts.
4. A "disagree and commit" protocol with a time stamp. When a decision closes, name how long it's closed for (a quarter, until a milestone, until a specific metric moves). Jak's Belief #1 will hold a commitment when it's framed as a commitment; what destabilizes him is when it feels like an idea he agreed to rather than a value he signed onto. Frame closed decisions as commitments to the venture's purpose, not as bets you made on Tuesday.
5. A shared language for what's happening when it happens. When Jak starts reopening, Dawson gets to say "parking lot?" without it being a fight. When Dawson is shutting something down too fast, Jak gets to say "is this a real close, or are you Galvanizing past a real signal?" The Working Genius vocabulary is genuinely useful here — it depersonalizes the friction.
One thing to watch: with Harmony #32 for Jak and Harmony #28 for Dawson, neither of you will naturally surface the friction in the moment. You'll both let it slide and it'll accumulate. Build the re-decision gate as a scheduled release valve precisely because neither of you will call the meeting spontaneously.
---
The deterministic analysis flagged it: no one on the founding team holds Enablement or Tenacity as a genius. For a venture that's going to traverse in-home kits → peptides → lab → 503B, Tenacity isn't optional. 503B in particular is a finish-the-last-10% world — cGMP, FDA inspections, batch records, CAPA. The work of closing things out to standard is where this venture lives or dies.
Let me check current Table Group framing on Tenacity-gap teams before I prescribe.
Good — the Table Group's published material on a Tenacity gap is clear and direct, and there's good corroborating language about Enablement. Now I can write the hire section with grounded specificity.
Both Working Genius gaps matter, but they hurt differently.
Tenacity is the genius of completion — people with this genius push through the final stretch when the energy of early stages has faded and the finish line is still not in sight. They care about results more than process, will not declare something done until it is actually done, and without Tenacity on a team, projects get 90 percent complete and stay there.
For 503B, "90% complete" is not a regulatory category. A batch record is done or it isn't. A SOP is signed or it isn't. An inspection finding is closed or it isn't.
Enablement matters too but reads differently in your build.
Enablement is the genius of responsive support — people with this genius read what others need and provide it, not because they are told to but because they naturally notice the gap and fill it. They are the teammates who make other people better. They are strategically attentive, not passive. The challenge is that Enablement often goes unrecognized precisely because it works — things move smoothly and no one asks why.
In an early-stage venture pivoting across verticals, the absence of Enablement shows up as Jak and Dawson both burning cycles on coordination work that someone else should be absorbing.
I'd actually frame this as two hires phased across the build, not one — because the role you need at the kit-fulfillment stage is different from the role you need at 503B. But the first hire should be designed so it grows into the second if the person scales.
Hire #1 — Director of Operations & Compliance (bring on at vertical #1, in-home kits).
Working Genius target:
these are responsive, dependable doers who derive energy from completing tasks and responding to the needs of others, equally value responsiveness and reliability, and are low-maintenance contributors who hold themselves accountable for delivering on their promises.
That's exactly the energetic profile that fills both your gaps in one person.
CliftonStrengths target: You want the Executing domain stack that's buried in both founders' profiles. Specifically:
People exceptionally talented in the Deliberative theme are best described by the serious care they take in making decisions or choices. They anticipate obstacles.
People exceptionally talented in the Discipline theme enjoy routine and structure. Their world is best described by the order they create.
This is the Gallup-published wiring for the compliance-and-completion seat.
Background you're hunting for:
Hire #2 — QA / Regulatory leader (bring on when peptide sales scale or lab work begins, whichever comes first). Different person, narrower technical depth. By the time you're compounding, you need a head of QA who has owned an FDA inspection. Don't try to grow Hire #1 into this seat unless they specifically came from regulated pharma — most ops/compliance people can't make that jump.
Earlier than feels comfortable. Here's why:
1. You're already a Tenacity-gapped team and you know it. Every week you run without that genius on the team, something is quietly getting dropped or half-done, and neither of you will see it because you don't have the wiring to notice. Jak's Restorative #8 will catch some of it after the fact (fix-what's-broken), but reactive Restorative is more expensive than proactive Tenacity.
2. In-home test kits are a regulated-enough vertical to need this role from day one. FDA labeling, CLIA considerations if results are interpreted, state-by-state shipping rules, HIPAA on the data side. You don't want to be retrofitting compliance into a kit business after launch.
3. *Hiring this person before the peptide pivot means they help design the peptide ops, not inherit them.* That's a 10x quality difference.
Concretely: I'd target this hire to be in seat within 60-90 days of company formation, before the first kit ships. Yes, that's expensive equity/
Good question, and the right one to be asking before the first vertical ships. Let me build this from the ground up rather than handing you stock EOS — because stock EOS will fight some of what's actually true about your founding team and your build sequence.
EOS is built for a relatively stable single-business with a Visionary/Integrator split, a clear accountability chart, and quarterly Rocks. The bones are sound. But three things about your situation push against the default:
1. You're not one business, you're a sequenced portfolio. Kits → peptides → lab → 503B is four businesses with different regulatory regimes, different unit economics, different customer motions. A single L10 meeting and a single scorecard will blur them.
2. Your Visionary/Integrator split is unusual. Jak is a Visionary on paper (Ideation/Futuristic/Invention/Wonder) but has actually run VP of Ops at a 503B — meaning he has Integrator pattern recognition the typical Visionary lacks. Dawson is a natural Integrator (Focus/Arranger/Achiever/Discernment/Galvanizing) but is also bringing the 3PL vertical-building experience that means he'll originate operating models, not just execute them. You have role-blur in a productive direction, but EOS as written doesn't have a slot for it.
3. Your Tenacity gap is structural. EOS assumes the Integrator drives accountability. Dawson can do that for a while, but his Tenacity is Competency, not Genius. The OS has to compensate for that until Hire #1 is in seat, and then redistribute when they arrive.
So: keep the EOS skeleton (Vision, People, Data, Issues, Process, Traction — the Six Key Components). Rebuild the muscle around your actual wiring and your actual build sequence.
---
Call it whatever you want internally, but the conceptual frame I'd pitch is:
One company, one purpose, one scoreboard at the top — and a stage-gated portfolio of verticals underneath, each with its own operating cadence sized to its maturity.
This frame does three jobs:
---
This is what EOS calls the V/TO (Vision/Traction Organizer), but I'd build it heavier on purpose and lighter on tactical 1-year plan, because your 1-year plan will get reshaped by what the kit vertical teaches you.
Components:
Reviewed annually, refined quarterly, not touched weekly.
---
This is the load-bearing innovation versus stock EOS. Every vertical lives at one of five stages, and moving stages requires clearing a written gate. This is what stops Jak's Ideation from prematurely activating the lab build while kits are still finding product-market fit.
The five stages:
1. Parking Lot — captured idea, no resource commitment. Jak's weekly Invention slot feeds this.
2. Exploration — small time-boxed research budget, named owner, defined question to answer, deadline. Output: a written go/no-go memo.
3. Build — capital and headcount committed, milestones defined, scorecard live.
4. Operate — shipping to customers, KPIs in the weekly review, P&L visible.
5. Scale or Sunset — clear thresholds for either path.
Gate criteria are written before the gate is approached, not after. This matters enormously for your pairing. If the criteria for moving peptides from Exploration to Build are written down in month 2, then in month 8 when Jak wants to accelerate and Dawson wants to wait, the argument is against the written criteria, not against each other. Belief #1 on both sides will respect a prior written commitment more than a verbal one.
Only one vertical at a time can be in Build stage. This is the rule that protects you from the most predictable failure mode of a portfolio venture: spreading thin. You can have Kits in Operate, Peptides in Build, Lab in Exploration, and 503B in Parking Lot — but you cannot have two verticals in Build simultaneously until you have a COO-level operator under each, which you don't and won't for a while.
---
EOS prescribes a weekly L10. I'd run four meetings on staggered cadences, each with a specific job. The discipline is that each
Picking up where I cut off — Layer 3 in full, then the rest.
EOS prescribes a weekly L10. I'd run four meetings on staggered cadences, each with a specific job. The discipline is that each meeting has a different cognitive mode — and you stop mixing modes. Mixing modes is the #1 cause of the reopening problem from the last turn.
Mode: Execution. Closed decisions only.
Dawson's Focus #6 + Arranger #4 + Discernment Genius runs this in his sleep. Jak attends but doesn't drive. Rule: no new vertical ideation in this meeting. New ideas get parked, not discussed.
Mode: Generative. No decisions made.
Jak's Ideation #3 + Futuristic #4 + Strategic #2 + Invention Genius runs free here. Dawson optional. If Dawson attends, his job is to listen and capture, not to discern. Discerning in this room kills the generative mode and burns Jak's energy without producing better decisions — it just produces fewer decisions.
Mode: Judgment. This is where decisions can change.
This is where the founders argue productively, on a schedule, with a structure. Both Belief themes will hold the outcome because it was decided in the right room at the right time.
Mode: Constitutional. The Layer 1 document gets touched here, nowhere else.
Annual offsite is 2 days and adds 3-Year Picture refresh.
One non-obvious rule: when Hire #1 (Director of Ops & Compliance) is in seat, they attend the Weekly Operating Review and the Monthly Gate, not the Invention Slot. Their Tenacity genius should not be exposed to weekly ideation noise; they need to be pointed at finishing things, not arbitrating new ones.
---
EOS says 5-15 weekly numbers. For a portfolio venture I'd structure it as three tiers, because you have to see the company AND each vertical without conflating them.
Tier A — Company health (5 numbers, reviewed weekly):
Tier B — Live vertical scorecard (5-8 numbers per vertical in Operate stage):
Tier C — Build-stage milestones (binary, reviewed monthly at the Gate):
The "no percent-complete" rule is specifically for your Tenacity gap. Until Hire #1 is in seat, percent-complete numbers will drift optimistic because nobody on the founding team has the Tenacity wiring to push past 90%. Binary milestones force honesty.
---
EOS insists: seats first, then names. Hold that rule. Here's how I'd draft it for your venture, sequenced to the build.
At founding (Day 1):
Picking up at Layer 5 mid-sentence and going through to the end.
At founding (Day 1):
At ~Day 60-90 (Hire #1 lands):
At ~Month 9-12 (Kits in Operate, Peptides in Build):
At ~Month 12-18 (Lab in Exploration → Build):
At ~503B horizon:
The rule for the chart: every seat has one accountable name. No "Jak and Dawson together own X." Co-ownership is how Tenacity gaps stay invisible. If a seat is genuinely shared today, write down who owns it primarily and put a review date on it.
---
Standard EOS says: document your "core processes" — the handful of major workflows that run the business — at a high level, get everyone following them, this is "the Process Component."
For a portfolio that ends in 503B, that's not enough. You need a two-tier process system:
Tier 1 — Company core processes (EOS-style, lightweight):
Documented in plain language, fits on a page each, founders and early team follow them. This is the EOS "followed by all" discipline.
Tier 2 — Regulated SOPs (cGMP-style, heavyweight, vertical-specific):
Why two tiers matters for your team: Jak's Discipline #31 and Consistency #34 are bottom-of-stack. Dawson's Discipline #30 and Consistency #27 are also low. Neither founder will naturally generate or maintain Tier 2 documentation. If you don't structurally assign Tier 2 to the Compliance hire from day one, it won't exist when an FDA pre-approval inspection shows up, and at that point it's too late to retrofit.
---
EOS has an Issues List — the running log of things that need solving, worked through IDS in the L10. Keep it. Add one thing:
The Vault. A separate, dated log of decisions made and the reasoning at the time. Three columns: decision, date closed, reopening criteria.
This is the structural fix for the reopening problem, made permanent. When Jak surfaces a re-decision request at the Monthly Gate, the Vault is what gets consulted first. "We closed this on March 12. Reopening criteria were: customer complaint rate above X, or supplier lead time above Y, or new regulatory guidance. None have triggered. Park or proceed?"
The Vault honors both founders' Belief — decisions become commitments-on-record, not casual agreements. It also gives the Compliance hire something most early-stage ventures can't give them: an actual decision history they can reference when building SOPs.
---
EOS says
Picking up at Layer 8 and running through to the end. I'll tighten the remaining layers so we actually finish.
EOS says 3-7 Rocks per person per quarter, company gets 3-7 Company Rocks. Keep the structure, tune the sizing:
The 90-day cycle:
---
EOS treats finance as a function under the Integrator. For a venture going kits → peptides → lab → 503B, capital sequencing is a load-bearing system, not a function. The 503B horizon implies real capex (lab equipment, cleanroom buildout, QMS, headcount) and Jak's prior 503B experience tells him exactly how much that costs.
Three documents that live alongside the V/TO:
1. Capital Plan — what each vertical costs to reach Operate stage, in cash. Refreshed each quarter. Honest.
2. Funding Path — bootstrap / revenue-funded / debt / equity, sequenced by vertical. Which vertical funds which.
3. Trigger Table — cash thresholds that trigger action. "If runway drops below 9 months, pause Exploration stage on all verticals." "If Kits gross margin holds above X for 2 quarters, release Peptides into Build." This pre-commits both founders to financial discipline before the emotion of the moment.
The Trigger Table is the same pattern as the Stage Gates and the Vault: pre-written rules that depersonalize hard decisions. Both founders have Belief #1 / #9 in their top 10 — pre-written rules with a values rationale will hold. Verbal agreements in the moment will not.
---
Two pieces, both lightweight at founding, heavier as you scale.
A. The People Analyzer (EOS keeps this, it works):
B. The Profile Review (your addition):
For your Compliance Hire specifically, this is how you avoid the most common founder mistake: hiring someone whose profile screams Tenacity and then loading them with Exploration-stage ambiguity because you're still figuring things out. Their profile is the contract about what kind of work you'll send them.
---
Separate from your operating agreement / cap table docs. This is a 1-2 page internal document, signed by both of you, reviewed annually. Contents:
1. Decision rights matrix. Who decides what, alone vs. together. Hiring above $X salary = together. Capital commitment above $Y = together. Vertical stage gates = together. Day-to-day operations = Dawson alone. Vertical exploration spend under $Z = Jak alone. Etc.
2. Communication norms. Response-time expectations, what goes in Slack vs. what requires a meeting, "no big decisions over text."
3. The reopening protocol from the last turn, written down.
4. The disagree-and-commit protocol with the time stamp convention.
5. The conflict escalation path. When founders are stuck — and you will get stuck — what's the path? Outside advisor? Coach? A specific board member once you have one? Decide now, not in the moment.
Picking up at the end of Layer 11 and finishing the build.
6. Founder energy review. Quarterly, 30 minutes, one question each: where are you spending time that's draining you, and where are you under-spending time that energizes you? This catches Jak drifting into Operate-stage Tenacity work (will burn him out fast given Frustration in Tenacity + Galvanizing) and Dawson drifting into solo execution because it's faster than delegating (will cap the company at his personal throughput).
7. Exit and equity protocols. Vesting cliffs, what happens if one founder wants out, what happens if performance becomes an issue. Boring to write, catastrophic to skip. This is a real-lawyer document, not an OS document, but the OS document references it so neither of you pretends it doesn't exist.
The reason this is a layer of the OS and not a one-time legal task: both founders have Harmony in the bottom 5 zone (Jak #32, Dawson #28). Neither of you will spontaneously raise the hard interpersonal stuff. The Founders' Agreement, reviewed on a calendar, forces the conversation to happen on a schedule instead of waiting for a blowup.
---
The OS has to have an owner, a review cycle, and permission to evolve. EOS implementations often fail because the OS gets treated as scripture instead of as a living tool.
---
When you eventually have a team and you're rolling this out, don't call it "our custom EOS variant." Call it something that explains the frame, not the lineage. Two framings that would work:
Option A — "Purpose, Portfolio, Posture."
Option B — "One Company, Four Verticals, One Cadence."
Emphasizes the unified rhythm under a sequenced portfolio. Simpler, more operational, probably better for an ops-heavy team.
Pick one, use it consistently, and resist Jak's natural urge to rename it every quarter. (That's not a dig — Ideation #3 + Invention Genius will want to refactor the language because language is thinking for that profile. Catch it gently.)
---
Don't try to stand all twelve layers up at once. You'll burn yourselves out building the OS instead of the business.
Days 1-30 — The Spine:
1. Constitution v1 (Purpose, Values, 10-year, 3-year, 1-year, Portfolio Map). Half-day session.
2. Accountability Chart v1 with vacant seats drawn.
3. Founders' Operating Agreement v1.
4. Weekly Operating Review + Weekly Invention Slot live, on the calendar.
5. Tier A Scorecard (5 company-health numbers) live.
Days 30-60 — The Gates:
6. Stage Gate criteria written for Kits (Build→Operate) and for whatever's next in line.
7. Vault stood up with first 10-15 decisions logged retroactively.
8. Monthly Re-decision Gate live.
9. Tier 1 Core Processes drafted (one page each).
10. Compliance hire job description posted, written against the target profile from the last turn.
Days 60-90 — The Muscle:
11. First quarterly Rocks set and tracked.
12. Capital Plan + Funding Path + Trigger Table v1.
13. Tier 2 SOP framework chosen (which eQMS, which document control approach) — even if mostly empty, the scaffolding is up before kits ship.
14. Compliance hire in seat or in final-round interviews.
15. First quarterly offsite executed; OS reviewed against reality.
By day 90 you've got a working system, a closing first hire, and a shipping first vertical. Anything more elaborate than this in the first quarter is the OS eating the business.
---
One: A system this designed only works if both founders treat it as binding on themselves first. The Stage Gates don't work if Jak overrides them because he's excited. The Vault doesn't work if Dawson re-litigates without using the Monthly Gate. The whole frame depends on both of you using the system especially when you don't feel like it. Belief #1 / #9 is the asset that makes this realistic for your pairing — both of you can hold to a commitment when it's framed as a values commitment. Lean on that.
Two: None of this substitutes for the things the profiles can't tell you. CliftonStrengths shows wiring under normal conditions; Working Genius shows energy across stages of work. Neither shows derailers under acute stress, neither shows integrity under pressure, neither shows whether a hire will actually execute when