The Partnership OS Install:
Every Agreement the Partnership Has Been Running Without
The full custom build of the operating system your partnership runs on. Eight agreements, built specific to your business, your decisions, your capacity, and your team. Not a document set you receive. Agreements you've drafted, tested against real decisions, and are already running by the time the build is called done.
Most partnerships don't need more conversations. They need better infrastructure.
You've probably felt some version of this already. Decisions that used to take minutes now loop for weeks. One topic stays carefully avoided so neither of you has to be the one who raises it again. Under real pressure you each default to your own style rather than a shared method. Meetings expand to compensate for agreements that were never actually made. Small frustrations accumulate instead of closing.
None of that is a communication problem. It's the absence of infrastructure that better conversations can't substitute for.
Sunny Sabbini is a partnership advisor in the San Francisco Bay Area working with
business partners and cofounders whose partnership has outgrown how it was set up.
The Standard Version, and Yours
The Partnership Design Lab drafts standard versions of some of these agreements, live, in a half day, alongside other partnerships doing the same work. For some partnerships those hold. Others get far enough in to find that the standard version doesn't fit what their business actually needs, and where it stops fitting is real information.
This is the custom version. Same artifact family, built for your specific decisions, your actual roles, and the team you actually have, rather than the generic case a standard version has to cover.
The standard version is the one that works for most partnerships. This one is the one that works for yours.
Built for Now, or Built for What’s Next?
The Partnership Capacity Check looks at ten situations growing businesses bring to their partners, and asks one thing of each: can the way you work together now carry it?
What Gets Built
Eight agreements. Two that set direction. Three that make direction executable. Two that account for what the two of you can actually carry. One that keeps all of it current as the business changes.
The balance is deliberate. An operating system built only from decision rules produces a business that runs cleanly toward a direction the two of you haven't actually agreed on. Built only from direction and relationship, it produces alignment nobody can execute. The eight cover all three dimensions because in a partnership they were never separate for long.
Three at full depth
Shared Direction Map
What it answers. Where is each of you actually trying to take this, and are those two pictures still the same picture? What has changed about what each of you wants that hasn't been said out loud? Is the business you're running still the right vehicle for what each of you is building toward?
Why it matters. Partners change. Ambitions change. What a partnership is building toward frequently doesn't get updated to match, and neither partner notices, because nobody re-asks a question that was settled in year two. What follows is that every resource decision quietly becomes a proxy for a conversation you haven't had. You argue about a hire. The hire isn't the disagreement.
What you walk away with. One documented picture of where this partnership is going, built by surfacing each partner's version separately first and then reconciling them, so what you end up with is something both of you recognize rather than something one of you conceded to.
Decision Rights Framework
What it answers.Which decisions require both of you and which don't? Who owns what in practice rather than on paper? What makes a decision final? How does disagreement escalate without becoming gridlock? How do you stop relitigating decisions you already made?
Why it matters. Decision drag is the most expensive cost a partnership carries and the least visible on any report. When authority isn't explicit, every decision becomes a negotiation before it can become a decision. When closure isn't defined, decisions reopen. And when ownership has quietly drifted from what was agreed, both partners end up touching everything, which is why nothing moves cleanly and why your team has learned which of you to ask.
Why it's more than a chart.Assigning decisions is the systems layer. Underneath it is a direction question, because you can't assign a decision without knowing what you're deciding toward. And underneath that is a capacity question: whether either of you can say the real objection in the room where the decision gets made. Build the chart and leave those two alone, and the chart gets quietly ignored inside a quarter. That's why this artifact takes as long as it does.
What you walk away with. A decision rights matrix mapping the categories of decisions your partnership actually makes to clear ownership, escalation triggers, and a defined standard for what counts as closed. Specific enough that someone on your team could read it and know exactly who to bring what to, without asking either of you first.
Capacity and Constraints Agreement
What it answers. What can each of you genuinely sustain at the level you're actually operating? What are the real limits, including the ones that have nothing to do with the business? What happens when one partner's capacity changes, for any reason?
Why it matters. Most partnerships run on an unexamined assumption that both partners have roughly equivalent capacity and that this will stay true. It's rarely true at the start and it doesn't stay true. One partner absorbs more, it starts to grate, and it doesn't get said, because saying it feels like an accusation rather than a fact about the design. What accumulates from that is more corrosive than the workload itself.
What you walk away with. An explicit account of what each of you can carry, with the limits treated as real constraints the structure has to accommodate rather than things to work around quietly. Including a defined process for what happens when one partner's capacity changes, agreed while nobody's capacity is currently in question.
The other five
Growth and Risk Posture Agreement
How much risk each of you is willing to carry, how fast you want to grow, and what you're each unwilling to trade for growth. Partners who agree on direction routinely disagree on pace and exposure without knowing it, and discover it during the decision that can't wait. You leave with an explicit posture you've both signed onto, and a way to test a specific opportunity against it.
Operating Rhythm
What meetings you actually need, at what cadence, and what each one is for. Without a deliberate rhythm, partnerships default to constant ad hoc check-ins that exhaust both of you, or long gaps with no real contact until something surprises you. You leave with a documented rhythm, so communication becomes predictable rather than reactive.
Repair and Escalation Protocol
How you know when something between you needs to be addressed rather than absorbed, who raises it, how, and how you know it's actually closed rather than dropped. This also covers the practical terms every partnership runs on without writing down: response times, what checking in means as distinct from deciding together, how the work is actually divided. You leave with a repeatable process both of you know how to use when something goes sideways.
Culture and Practice Charter
What this partnership is for beyond the financial outcome, what's non-negotiable for each of you, and how the two of you intend to treat each other when it's hard. Most partnerships assume alignment here and find the gaps when the stakes are high and nobody is at their best. You leave with a documented reference point, available when a hard call needs one.
Partnership Review and Renewal Cadence
When and how the other seven get re-examined, and what triggers a re-examination early. A structure built for a nine-person firm doesn't fit an eighteen-person firm, and the version of the two of you that built it isn't automatically the version that runs it under the next conditions. You leave with a defined cadence, so the system stays current rather than becoming the thing you've outgrown three years from now.
How the Eight Work Together
They aren't eight independent documents. Several depend on others being built first, and building them out of order is one reason previous attempts didn't hold.
Direction comes first, because decision rights built before direction is agreed will faithfully execute a disagreement. Capacity comes early, because a decision rights framework that assigns authority neither partner can actually sustain is a document rather than a system. Rhythm and repair come after authority is clear, because a repair protocol without defined ownership has nothing to escalate to. Renewal comes last and then applies to everything above it.
Which of the eight your partnership needs most, and in what order, isn't a fixed sequence. It's what the Read determines.
Built, Not Delivered
This isn't a document set you receive and file. Each artifact gets run live, against a real decision, at least once before the build is called done. You leave with agreements you've already tested, not ones that sounded right in a room.
What's Included
A partnership retreat, where the direction and capacity work happens with enough continuous time to actually finish it.
Bookended individual sessions with each partner, before the build begins and after it completes. The pre-build sessions are where each of you says the thing plainly, once, without managing the other person's reaction while you're saying it. The closing sessions are where each of you names what you're now responsible for holding.
The full build of all eight agreements, each one run live before completion.
Travel and accommodations for the retreat aren't included.
What Changes
Decisions accelerate. What used to loop for weeks resolves in days, because authority is clear and closure is defined.
Roles feel clean. Not just described. Experienced as clear, by both of you and by the people who work for you.
Repair happens quickly and leaves little residue, instead of sitting for weeks doing quiet damage.
Your team notices before either of you says anything about what changed.
Most partnerships operate in a low-grade state of vigilance. Watching for the next friction point. Managing around things that were never quite agreed. Compensating for gaps neither of you has named. When the structure is actually built, that vigilance eases, and you get to spend your attention on the business instead of on managing the partnership around it.
The partnership stops being a constraint on the business and becomes an asset to it.
Beyond the Core Eight
The eight are the core. Some partnerships need more, and what they need depends on what's coming.
A Transition and Continuity Protocol, for partnerships with a succession, a sale, or a partner stepping back somewhere in view. A Coherent Leadership Signal standard, for partnerships whose team has learned to route around them. Others exist and get built when the situation calls for them.
These are scoped as part of the build rather than sold separately.
After the Build
Some partnerships want the working relationship to continue once the eight are built and running.
Conditions keep changing, so a structure that fits this year fits less well next year. What continues isn't a new set of sessions. It's access and judgment as the business keeps changing, and a cadence for keeping the eight current rather than letting them become the thing you've outgrown.
It isn't something you start on its own, and it isn't part of the build itself. It's how a build tends to keep going, for partnerships who find they want it once they're actually running on what they built.
Who This Is For
Partnerships who've had the Read, know specifically what needs building, and have both partners willing to do the work.
Both partners participate throughout. This isn't work one partner can commission on behalf of the other.
Some partnerships build alongside one or two others. Some build privately. Which shape fits depends on what you're building and how sensitive the material is, and that gets decided in scoping rather than before it.
Investment
Scoped to what your partnership needs.
Two partnerships rarely need the same build, and pricing a bespoke engagement with a single fixed number would mean charging some partnerships for work they don't need and underpricing the ones who need more.
The Read and Roadmap is priced as its own piece of work and so is the Partnership OS Install, because each of them is a different job rather than a stage of one.
Where to Start
Every build starts with the Partnership Evolution Read.
Not because the build is a lesser step, but because a bespoke build scoped without a read is a build aimed at whatever presented. The Read is where you find out which of the eight your partnership actually needs built custom, in what order, and why that order matters for your situation.
Partnerships who complete the Read move directly into scoping.
A partnership built for what's next.
San Francisco Bay Area · Remote sessions nationwide
As Seen In
See full articles from Press & Media page
