Pick the Bets That Matter

The plan is not to do more.

The plan is to make the next two quarters impossible to misunderstand.

Offsite Flow

flowchart TD
    Inputs[Customer and revenue inputs] --> Bets[Candidate bets]
    Bets --> Rule{Passes decision rule?}
    Rule -- yes --> Owner[Name owner]
    Rule -- no --> Kill[Move to no list]
    Owner --> Proof[Define six-week proof]
    Proof --> Rhythm[Add to operating rhythm]

The room should move ideas into one of two places: owner-ready or killed.

Portfolio Split

pie title Q3 strategic capacity
  "Activation" : 40
  "Partner channel" : 30
  "Enterprise readiness" : 20
  "Run the business" : 10

The split is a constraint, not a wish list.

Six Week Plan

gantt
  title First proof schedule
  dateFormat  YYYY-MM-DD
  axisFormat  %b %d
  section Activation
  Trial funnel instrumentation :active, a1, 2026-06-08, 10d
  Qualified trial review      :a2, after a1, 7d
  section Partner
  Launch partner shortlist    :p1, 2026-06-10, 8d
  Integration memo            :p2, after p1, 10d
  section Enterprise
  Security packet v1          :e1, 2026-06-12, 12d

Every bet gets a proof date before it gets a budget.

The Room Has One Job

By the end of the offsite, every team should know:

• what we are betting on
• what we are deliberately not doing
• who owns the first visible proof

No vague pillars. No orphaned initiatives.

Operating Principles

Fewer bets
Clearer proof
Named owners

Milestones

The first proof must be small enough to ship in six weeks and strong enough to change behavior.

Candidate Bets

Bet	Why now	First proof
self-serve activation	sales pipeline is saturated	20 qualified trials
partner channel	integrations are driving pull	3 signed launch partners
enterprise readiness	expansion deals are blocked	security packet v1

Decision Rule

Choose bets that pass all three tests:

1. customers can feel the change
2. a single owner can move it
3. the first proof arrives within six weeks

Anything else is a project, not a strategy.

Bet Shape

• Self-serve activation
  • first proof: 20 qualified trials
  • owner: Growth
  • customer behavior: fewer demo-only prospects
• Partner channel
  • first proof: 3 signed launch partners
  • owner: Alliances
  • customer behavior: integration-led pull
• Enterprise readiness
  1. security packet v1
  2. procurement blocker map
  3. expansion account pilot

Nested ownership beats vague pillars.

What We Kill

• projects with no named owner
• launches that only create internal motion
• metrics no customer behavior can validate

---

Strategy gets sharper when the no list is visible.

Operating Rhythm

Cadence	Question
Monday	What proof moved?
Wednesday	What is blocked?
Friday	What did customers tell us?

Final Readout

Use the same format for every bet:

1. The customer behavior we expect to change.
2. The first visible proof.
3. The named owner.
4. The reason we are not doing the nearest alternative.

No section gets more than one owner.

Close

Leave with fewer priorities than we arrived with.

That is the point.