ASSAY

One rep. One sale. Every call.

A sales system,
running.

One deal, worked properly, from the first ring to the reason it was booked. The company is invented. Nothing else is.

Take a call. Push back on it the way a real one pushes back. The queue re-sorts itself, the account fills in from what was said, and the coach waits for enough calls before it opens its mouth.

Every number in it is sourced. 5 of 24 claims this industry teaches from failed the audit, three of them mine. The working is published.

The call tree, live

Deal inspection

Queue, call, account.

Under ten reps there is nothing to inspect. Past eight hundred they build it themselves.

The champion and the economic buyer are usually the same person, which makes it fast, and hides the risk. RevOps can veto it on integration grounds in week three, security can stall the paper over call recording, and the reps decide at rollout whether it lives past renewal. The people who can kill it are rarely the people you are talking to.

Forty seconds, no clicking. It drives the real tree. An objection that stops the call, three implication questions, the close. Touch anything to take over.

Pick someone from the queue.

Nothing here is a script you read. Every line has what comes back underneath it, and the call goes where you take it.

Every line in the tree is defensible and the evidence behind the rails is published. The research.

What it found

Numbers I did not write.

All of these are computed from the 14 calls in the worked example by the same functions the Coach and Manager tabs run on your own book. Load it and check every one.

  1. 2.8 against 0.5

    Implication questions on the calls that booked, against the ones that did not

    Rackham found this gap across 35,000 calls and it is the strongest predictor on the research page. Fourteen calls proves nothing on its own. What it shows is the mechanism running on a rep's own record instead of being quoted at them.

    Check it: Coach, first panel

  2. 100% against 0%

    Trust and risk objections against timing ones

    3 and 3 occurrences. A book that logs "objection handled" produces one blurred number and the instruction "get better at objections". This says rehearse timing, which is a thing a person can actually do on Monday.

    Check it: Manager, worklist

  3. 0%

    Advance rate on reflex brush-offs, from 3 of them

    A brush-off fires before any information has reached the prospect, so there is nothing yet for them to be uninterested in. Handling it as a real objection confirms you are what they thought you were, and the record here says so out loud.

    Check it: Coach, what to change

  4. 3 held, 3 missed

    Of 7 meetings agreed across the book

    Booked and held are different numbers and most pipelines carry only the first. Splitting them is the difference between a meeting count and a forecast, and it is why an agreed meeting that no-shows does not count as an advance anywhere in this system.

    Check it: Manager, top row

  5. 16

    Objections worked rather than logged

    Each one stopped the call until it was handled, then recorded how it went in the prospect's words. That record is what every number above is made of. Without it a call log is a list of dispositions.

    Check it: Desk, run a call

  6. Check it.

    Book tab, load the worked example, then Coach.

    Anything with fewer than three occurrences behind it is suppressed rather than shown, here and everywhere else in the system. A page complaining that sales numbers get quoted without their samples does not get to quote one without its sample.

Why this exists

I went looking for how to do this well.

What I found was an industry quoting itself.

Every post said the same eight things. Every one of those things had a number under it, and every number had a company under that, selling the thing the number recommends. Nobody linked a study. The ones I could chase turned out to be older than the phone in my pocket, or a survey of what people said they did, or a training firm discovering that training works.

So I stopped reading and started checking. Twenty-four claims, each one back to its source, with the publisher’s stake in it written down beside the verdict. Five of them failed. Three of the five were ones I had already believed.

This is what was left standing, built into something that runs. Not a summary of the research. The research, wired up, where you can argue with it.

Where to look

  • Say no on the call and watch it refuse to move on
  • Say it a second time and watch what the card says then
  • Log the call, then open Qualify without typing anything
  • Book a meeting and see where Manager puts it
  • Run four calls and watch Coach refuse to advise you

Tell me where it is wrong

A verdict you disagree with, a question the tree should ask and does not, an objection I handled badly. The critical answers are the ones that get published here beside what they changed.

Say so here

Eight questions, one click each. It lands in one inbox and nothing is stored.

Assay. Built by Kendal Miller.