Four Models

Each one filled in with Mike's real numbers, so you're looking at the thing and not a description of it.

Goal on the call [1:23:12] — two clients a month at $2,500. Everything below is built backward from that.

A

The Sandler Cookbook

David Sandler · 1967 · Sandler Systems · still the standard sales-manager artifact
The numbers spine

Start at the income number and divide backward until you hit a count a man can do before lunch. Then — and this is the part that makes it work — you measure him only on the behaviours, never on the outcome, because behaviour is the only thing he controls. Mike would recognise this on sight. It's a Canon-era tool. You'd be handing him back his own profession.

Mike's cookbook, filled in
$5,000
Monthly revenue goal — his number, his words
÷ $2,500 per client
2
Clients per month
÷ 25% close rate on a real sales conversation
8
Sales conversations
÷ 80% show rate
10
Calls booked
÷ 20% of real conversations become a booked call
50
Real conversations
÷ 20% of outreaches become a conversation
250
Outreaches
What he actually does — the only thing he gets measured on
12
outreaches / day
60
outreaches / week
12
conversations / week
2–3
calls booked / week
Your language it proves — [1:32:18] “reverse engineer what daily activities create the outcomes you're looking for and then just holding yourself to that standard.”
Source — sandler.com · The Cookbook for Success
B

The Hoshin X-Matrix

Bridgestone Tire · 1965 · adopted by Toyota · Deming Prize lineage
The page

One sheet, four quadrants rotating around a centre, with a correlation grid showing which activity drives which number. Nothing is allowed on the page unless it connects to something on the opposite side. And its rule called catchball — the target is negotiated with the person who has to hit it, never assigned — is DARN CAT at company scale.

Mike's X-Matrix

North — The Breakthrough (6 months)

  • 12 paying clients
  • $30,000 collected
  • An acquisition system that runs without hope in it

West — Targets to Improve

  • Close rate — currently unknown
  • Reply rate — currently unknown
  • Days with zero outreach → 0
  • Revenue per hour worked
Two clients
a month
at $2,500

East — Objectives

  • Prove the price (Aug)
  • Build the avatar from 30 conversations (Sept)
  • Turn on cold flow (Oct)
  • Survive delivery (Nov)

South — Improvement Priorities

  • 250 outreaches / month
  • 30 research conversations
  • Weekly scorecard, no exceptions
  • One repeated answer recorded per week
Risk — it reads as manufacturing. A man from copier sales may find it foreign.
Source — lean.org · Hoshin Kanri
C

The 12 Week Year

Brian Moran · 2013 · Wiley
The cadence

Compress the year into twelve weeks, because annualised thinking is what lets a man coast until December and then panic. Split what he controls from what he doesn't. Then score only the controllables — one percentage, every Friday. 85% is the line. Hit 85% of planned activity and the results arrive whether you believe in them or not.

Weeks 1–12 · August 5 – October 27
IndicatorTypeWeekly target
Outreaches sentLead — he controls it60
Conversations heldLead12
Research calls heldLead5
Follow-ups on no-replyLead25
Offers made at $2,500Lead1
Calls bookedLag — he does not control it2–3
Clients closedLag0.5
85%
The execution score. Planned activities completed ÷ planned activities. Not results. Not effort. Not how the week felt. One number, every Friday. Below 85% two weeks running is the conversation.
Your language it proves — [1:45:53] “one thing, black and white. Gray is not allowed. It is either you did it or you didn't do it.”
Source — 12weekyear.com
D

Operation Crush

Intel · December 1979 · Andy Grove, Bill Davidow, Don Buckhout
The story, not a template

Not something to fill in. The thing you say to him when he doesn't answer the math question — which is exactly what happened at [1:32:18].

Nov 1979

Motorola's 68000 was beating the Intel 8086 on merit. Better chip, losing sockets weekly. A field engineer sent an eight-page telex saying we are losing and nobody is acting.

Dec 1979

Grove pulled a task force. Four days. They didn't change the product. They set one objective and cascaded it to the field as weekly quotas — seminars run, design wins logged.

1980

Target was 2,000 design wins in a year. They booked 2,500. One of them was IBM, and that socket became the personal computer.

Why it lands on Mike — he's a career field-sales man with fifteen President's Clubs. This is the proof, with a date and a number, that reverse-engineered weekly activity beats a better product. He's lived the mechanism from the inside; he just hasn't pointed it at himself.
Source — whatmatters.com · Operation Crush · Grove, High Output Management

They aren't competing. They do different jobs.

A gives the numbers — and it's the only one that converts his own goal into something he can do before lunch. C gives the rhythm — the weekly score that makes a missed week visible on Friday instead of in February. B gives the picture — one page, six months, everything connected. D is what you say out loud when he goes quiet on the arithmetic, like he did.

You already answered the time unit: six months, weekly targets inside. That's A's math, on C's cadence, laid out on B's page.

Pick 1A only. Fastest. A cookbook and six dates. Least visual.
Pick 2A + C. Numbers and the weekly score. No single picture.
Pick 3A + C + B. The full page. D stays in your mouth for Tuesday.