Partnership
For organizations going deeper than the cohort scope allows.
Partnership is the rung above the four-week cohort. It's for organizations that have already done the cohort and want ongoing co-evolution as the work compounds — or for organizations whose first engagement is large enough that the four-week structure isn't the right shape for the work in front of them.
The partnership isn't a retainer. It's a structured engagement built around specific capability development, with a clear cadence, clear scope, and the same capability-transfer outcome the cohort commits to.
The shape of the engagement
Ongoing co-evolution, not ongoing dependency.
Most partnership relationships in this market are retainers — a monthly fee in exchange for a defined level of ongoing access. The partnership tier is structured differently. The fee is monthly. The minimum is three months. But the engagement is shaped around capability transfer, not around perpetual access. Three months in, six months in, a year in — the relationship is producing measurable internal capability inside your organization, not producing measurable internal dependency on us.
If after three months your team is operating the system on its own and the partnership has run its course, that's the partnership working as designed. If after three months we're agreeing to continue because there's a next layer of work and your team wants us partnered through it, that's also the partnership working as designed. Either way, you can give thirty-day notice at any time. The cancellation policy is unconditional.
The fit
Two organizational situations make partnership the right shape.
Post-cohort organizations going deeper
You've completed the four-week cohort. The Foundation for the Unified Customer View is in place. Your team is operating the system. Now you're going after the next layer — Unified Revenue View, Unified Business Context, Unified Team Enablement — and you want a partnership that walks alongside that work rather than another four-week intensive.
Organizations whose first engagement is larger than the cohort scope
The four-week cohort is built for a specific scope — five to eight people from one organization, building a working AI-native stack. Some organizations come to the work with scope that exceeds that — multiple business units, multi-portal HubSpot architecture, regulated environments with specific compliance overlays, or implementation timelines tied to commercial milestones that don't fit the four-week shape. Partnership is the right shape for that work.
What you get
What partnership includes.
- Weekly strategy sessions — 60 minutes, structured around the capability you're building this month, not a generic "check-in."
- Direct working access between sessions — the partnership is collaborative, not transactional.
- Continued evolution of your AI-native stack — new agents, new enforcement skills, new architecture moves as your operating model matures.
- Access to the practitioner community of the Value-First Collective.
- All updates to the operating playbook as the methodology evolves.
For clarity
What partnership isn't.
- Not a managed-services relationship. We don't run the system for you. Your team operates it. We partner on its evolution.
- Not unlimited access. The cadence is real — weekly sessions, structured working windows between them. Asynchronous availability is intentional and reasonable, not always-on.
- Not a path that requires the cohort first. Most partnerships do follow the cohort, because that's the most natural progression. But partnership is the right shape on its own merits for some organizations, with or without a prior cohort.
- Not bundled-up consulting hours. The investment isn't tied to a billable-hour count. The relationship is structured around capability outcomes, not hour accounting.
Investment
$9,995
Monthly. Three-month minimum.
Partnership is $9,995 per month, with a three-month minimum commitment. After the initial three months, the relationship continues month-to-month with thirty-day notice on either side. The cancellation policy is always available and unconditional.
The minimum exists because the work compounds. The first month is orientation. The second month is when the architecture decisions start producing visible capability change. The third month is when the team can credibly assess whether the partnership has run its course or whether the next layer of work warrants continuing.
How partnerships start
Two doorways. Same engagement shape.
Through the four-week cohort
Most partnerships start as a cohort. The cohort produces the working stack and the team capability. Partnership picks up where the cohort leaves off, with the natural continuity of having been in the work together for four weeks already. The partnership conversation often emerges in Week 4 of the cohort itself, when the next layer of work becomes visible to both sides.
Through a direct partnership conversation
If your scope exceeds the cohort shape — or if the cohort isn't the right entry point for your organization for other reasons — we'll structure an initial three-month partnership directly. The first session of that engagement is shaped around the architecture work that would otherwise have happened in cohort Week 2. The structure adapts to the scope.
The capability transfer outcome
The point of the partnership isn't to make the partnership permanent. The point is that your team is operating an AI-native organization on its own, and we are available as thought partners and as a community of practice — but the operational work is yours.
Most partnerships run between three and twelve months. Some run longer because the scope of the work is larger. Some end at three months because the work transferred faster than expected. There is no commercial pressure to extend a partnership beyond its useful life. The thirty-day notice policy is real. The capability-transfer commitment is real. We'd rather have an organization that graduated cleanly and refers another organization than one that stayed past the point where staying served them.
Daily Brief
Stay close to the work.
Each morning, the Daily Brief delivers one note from the day’s episode — the practical move a leader can put into rotation.
Same audience as the cohort. Same operating language. Free.
Unsubscribe at any time. Your address stays with us — never shared, never sold.