AI-Native Shift

The Four-Week Cohort

Four weeks. Five to eight people. A working AI-native stack at the end.

The AI-Native Shift cohort is the flagship engagement of the program. Two sessions per week, ninety minutes each, structured to move your organization from the question of whether AI-native is worth the shift to the answer of running it in production.

Talk to us about the cohort See how the cohort runs

What this is

A four-week intensive built around real implementation.

The cohort isn't a course. It isn't a workshop. It's a structured engagement where five to eight people from your organization spend four weeks building the AI-native architecture for your business — with us, with each other, and with the AI agents that will eventually be running parts of it for you.

The format is two ninety-minute sessions per week. Eight total live sessions. The first session each week is conceptual; the second is hands-on application to your actual organization. Between sessions, the team puts the work into rotation in their actual roles. By the end of Week 4, the system you've built is operating against real business data.

Sessions per week 2
Session length 90 minutes
Total sessions 8
Total live hours 12
Weekly rhythm Session 1 (framework) + Session 2 (application)

The four weeks

Each week, in detail.

Week 1

Mindset

Eye-opening. The week before architecture. The week where you stop trying to fit AI into how the business already runs.

Session 1 — The Training Data Problem + the AI-Native Philosophy

Why AI trained on industrial-age data gives you industrial-age answers. What changes when you stop asking "how do we add AI to this process" and start asking "what does this process look like if we design it for AI-native operations from the start." An introduction to the Value-First Framework as the lens we'll use for the rest of the work.

Session 2 — Trap Assessment + Cost-of-Current-State

A working session against your organization. Which of the Twelve Complexity Traps are present? Where is complexity hiding? What is current state actually costing — in time, in margin, in team capacity? The session ends with a shared diagnostic the team agrees on.

What you leave with

A Trap Assessment specific to your organization, a quantified picture of what current state is costing, and shared language across the team for the work of the next three weeks.

Week 2

Architecture

Conceptual, then collaborative. The week where the target state stops being abstract.

Session 1 — The Four Unified Views + the Organizational Frame

A deep dive on the operating model. What "Unified Customer View" actually means in production. What "Unified Revenue View" requires. Why most organizations stop at View 1 and never get to Views 2, 3, and 4. The organizational frame — three functional orientations around customer relationships, operations, and financial health — and how it replaces the twelve-department default.

Session 2 — Value Path Stage Mapping + Target State Architecture

A collaborative architecture session. We map your actual customers against the eight-stage Value Path. We design what HubSpot looks like configured as a Customer Value Platform for your business. The team draws the architecture. We facilitate.

What you leave with

A custom Five-Layer Architecture document. The blueprint that Weeks 3 and 4 will deploy against.

Week 3

Activate

Hands-on. The week where the system stops being a document and starts being a deployed stack.

Session 1 — HubSpot CVP Configuration + AI Orchestration Setup

Configuring your HubSpot as a Customer Value Platform. Setting up the AI agents that will work alongside the team. Connecting real business data. This is the technical session — varying levels of technical confidence is expected, and the team works together.

Session 2 — Enforcement Mechanisms + Integration

The enforcement layer — the operating skills that keep the system aligned with the architecture under day-to-day pressure. End-to-end testing with real scenarios. Iteration on what doesn't work yet.

Between sessions

Activation week surfaces specific problems with specific data — the cohort works through those between sessions, with what they built in Session 1 as the substrate. Anything that stays stuck gets unblocked at the start of Session 2.

What you leave with

A working AI-native stack — not a mockup, not a sandbox. AI agents running against real business data. Named people activated on real problems they own.

Week 4

Scale

Operational. The week where individual activation becomes organizational capability.

Session 1 — Production Readiness + Team Enablement

Production readiness — the operating substrate that lets the system run sustainably. Team enablement — the training rhythm that lets new people coming into the organization inherit the architecture rather than having to rebuild it.

Session 2 — Measurement Framework + Transformation Presentation

The measurement framework — how you know the system is working without dashboard theater. The capstone presentation — the cohort presents the transformation to itself, and the documentation becomes yours.

What you leave with

A team running the system independently. A measurable transformation (people activated, agents in production, integrations running). A transformation presentation that's yours to use however you want — internal leadership, board, recruiting, whatever serves you.

The cohort composition

Five to eight people from one organization. Not mixed individuals.

The cohort is built around shared accountability. When the team building the system is in the room together, there's no telephone game between sessions. When the executive sponsor is in the same conversation as the people who will operate the system, the architecture doesn't get reshaped by someone who wasn't there. This is why we don't run mixed-individual cohorts — the work depends on the people who will live with the system being the people building it.

Executive Sponsor

Authority to implement changes that the cohort produces. Without this, Week 4 ends with a beautiful system and no path to running it.

Operations Champion

Day-to-day ownership of the transformation after the cohort ends. The person who will hold the architecture when no one's watching.

Key Team Members

The people who will actually use the new systems. They need to build them, not inherit them.

Technical Resource (optional)

If custom integration is in scope. Often a contributor or partner you already work with — they don't need to be a full-time employee.

What's in the investment

Everything required to leave with a working system.

  • Eight ninety-minute live sessions across four weeks
  • Five to eight named participants from your organization
  • All program materials, frameworks, and reference documentation
  • HubSpot CVP architecture deployed against your portal
  • AI agents configured and connected to real business data
  • Enforcement skill library, customized to your operating context
  • A custom Five-Layer Architecture document — yours to keep, extend, and share internally
  • The operating playbook for evolving the system after the cohort
  • Cohort alumni community access

Investment

$24,995

For the four weeks.

The cohort is $24,995 for the organization. One price. Five to eight people. All eight sessions. Everything listed above. No per-seat upcharges. No materials fee. No "premium tier" with the actually-useful pieces gated behind it.

After the four weeks

Two optional windows, capped — only if you need them.

The cohort ends after four weeks. Most organizations don't need anything else. The system is running, the team can operate it, and you're free to evolve it without us.

Two optional capability transfer windows are available if a specific capability gap shows up at the end of Week 4. Each window is hard-capped — no scope creep, no open-ended retainers. They're not upgrades. They're not "the real program after the program." They exist because some capability transfers take a little more time, and we'd rather have a structured window for that than pretend the four weeks are enough for every organization.

Both are optional. Both have hard caps. Either window only happens if your team explicitly identifies the capability gap and chooses to do it. The default is that you don't need them.

Activate window

$8,000 cap

A specific Week 3 activation that needs deeper partnership to fully land — typically a complex integration or a particularly involved AI agent configuration.

Scale window

$8,000 cap

A specific Week 4 scale move that needs additional facilitation — typically when a larger team needs structured enablement rounds to operate the system at full breadth.

Both windows are capped. Neither rolls into a retainer. The point of the cohort is that three months from now, you're operating the system on your own. The capability transfer windows exist to make that more likely, not to extend our involvement.

For clarity

What the cohort doesn't pretend to be.

  • It's not a course. There's no LMS to log into and watch on your own time. The cohort is live and synchronous.
  • It's not a strategy engagement. The deliverable isn't a slide deck or a recommendation document — it's a running system.
  • It's not done-for-you. It's done-with-you. Participation is required. People who attend without engaging won't get value, and the team around them won't either.
  • It's not a sales pitch for a longer engagement. The cohort is the engagement. Partnership exists if you want it after, but the cohort is built to leave you self-sufficient.
  • It's not for organizations looking for a one-person training. The cohort requires five to eight people from one company. That requirement is structural, not preferential.

Common questions

FAQ

What if we're early-stage and don't have all five-to-eight people yet?

A two-person founding team can do extraordinary work in the cohort if both people are fully committed. We'll talk through whether your stage is the right fit during the Activation Workshop — for some early-stage organizations, the Activation Workshop itself is the right engagement, and the cohort comes later.

We're already on HubSpot. How is this different from a HubSpot consulting engagement?

A HubSpot consulting engagement configures your HubSpot. This cohort treats HubSpot as the substrate for the operating model you actually run — Customer Value Platform, not CRM. The configuration is downstream of the architecture decisions. Most HubSpot engagements skip the architecture and go straight to configuration; that's the work that produces well-configured systems running broken processes.

How is this different from hiring an AI consultant?

An AI consultant adds AI to your existing operating model. The cohort redesigns the operating model so AI isn't an addition — it's the substrate. Different starting assumption. Different deliverable. Different team capability at the end.

What if Week 3's deployment doesn't fully work?

Iteration is the work, not a sign something is wrong. The system in production at end of Week 3 is the starting point for Week 4 — refinement, hardening, and operationalization. The optional Activate capability transfer window exists for exactly the cases where Week 3's first pass needs more time to fully land.

Can we cancel after we've started?

Yes. Our cancellation policy is 30-day notice — always available, unconditional. If the cohort isn't the right fit once it's underway, you can step out. The investment is non-refundable for sessions already delivered, but no one is held to a program that isn't working for them.

When does the next cohort start?

Cohorts are scheduled when there's a fit between organizations ready to commit and our delivery capacity. Apply or book an Activation Workshop, and we'll talk through timing.

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.

Take the next step

Option 1

Talk to us about the cohort

Thirty-minute fit conversation about the cohort and where you actually are.

Go
Option 2

Listen to today's episode

Daily show, every weekday.

Go
Option 3

Explore the framework

The operating model the cohort draws from.

Go