1. Do a time audit on the last three deals you won: hours spent in each of the four jobs. Sourcing will come out near empty — not because it wasn't needed, but because it was being dodged.
2. Make the most painful cut first: almost every first split goes between sourcing and closing, the two whose tempos clash hardest. Watch for a month: did the closer's meeting count rise? If not, the bottleneck was never sourcing.
3. Put the handoff on one page: three required items plus a line saying "send it back if these are missing". Rejectability is the point — a handoff nobody can return just gets silently redone downstream.
What a handoff sounds like: "This one's yours. His words were 'reconciliation eats two days at every month end.' Budget never came up. The finance director decides. Confirm those three before you book the meeting."
Mechanism: specialisation pays twice — fluency from repetition, and not having to switch mental gear between unlike tasks. It costs once, at every seam: handoff friction and lost information. So finer is not better. The net depends on your deal volume, and at low volume the friction outweighs the fluency.
Honest boundary: those experiments run in milliseconds, and converting them into "switching costs a salesperson X% of the day" is extrapolation, not a research finding — they support "switching has a cost", not any number. Also, splitting narrows what each person sees: whoever does sourcing stops hearing real closing conversations and their judgement drifts. Sitting them in on a live meeting periodically isn't a perk, it's calibration.
Sent in advance: a one-page description of your real product, plus public information on a real customer (site, job ads, news).
Task one (15 min, live): "I'm head of operations at that company. You have ten minutes. Go." You play an ordinary difficult buyer: busy, mildly sceptical, volunteering nothing. Watch for: how many questions he asks; whether they're about his pitch or my situation; whether he follows up when I go vague or just keeps talking.
Task two (15 min): "What went badly there, and what would you change on a second run?" Watch for: whether he can review himself concretely. A person who can is one a process can amplify; a person who blames the customer isn't.
Task three (15 min): hand him a real objection ("we're already using someone else") and have him write three lines back. Watch for: does he acknowledge before he answers, or collide head-on.
Scoring sheet (1–5 each, identical for everyone): question quality / listens before speaking / self-review / handles vagueness / clarity. Score independently before anyone speaks — discussing first lets the first voice contaminate the room.
Mechanism: the accuracy of any selection depends on how much of the signal is genuinely job-related. A free chat hands the criterion over to momentary warmth and similarity, which pours noise into the judgement. Fixed questions on a fixed scale put candidates on one baseline. A work sample is more direct still — behaviour predicting behaviour, with one less layer of translation.
Boundaries and one red line: structured doesn't mean stiff — probe and follow up freely; what's fixed is the question list and the scoring dimensions, not the conversation. A work sample only works if the task really resembles the job, so no brain-teasers. And the hard line: a sample task must never become free labour — beyond an hour or two, or if you intend to actually use the output, pay for it.
1. What's the laziest way to game this metric? On revenue → give discounts. On new logos → ignore renewals. On activity → pad the logs. Once you know, either change the metric or block the route directly. The most useful block: charge discounts against his commission base, so giving margin away costs him his money.
2. Who owns the things you can't count? Handoff quality, telling the truth, helping a colleague — none of it ever fits in a commission. Only three fixes work: lower the intensity of the single metric (don't run pure commission), tie part of the payout to the team or to renewals, and delay vesting. Adding one more commission line to cover the gap mostly just creates a new surface to game.
3. Accelerators or not? They do drive a sprint, and the price is the shape above. If you use them, lengthen the period and set the threshold within reach; anyone far below it will write off the quarter and hide deals until the next one.
4. How do you set the rate? There's no universal number, only a derivation: take gross margin per deal, decide what share of that margin selling can consume (your unit economics decide this, not your competitors'), multiply by expected deals, and that's the ceiling on one person's total package — then split it into base and commission. Common industry practice is a roughly even split (a checkable convention, not a research finding); the simpler and more individual the deal, the more can sit in commission.
Mechanism: when one person must do several things and only some of them can be measured accurately, strong incentives on the measurable part pull effort away from the rest. That isn't an attitude problem — it's a rational response to the price list you handed him.
Boundary: commission addresses willingness, never capability — a low conversion rate is usually a skill and process problem, and adding commission there just disappoints your best people into leaving first. Same for individuals: reward yourself only on countable metrics (posts published, people met) and the uncountable things that actually compound get crowded out by your own scheme.
1. Four fields required, everything else optional. Each extra mandatory field costs you a slice of data quality; compute the reporting fields yourself from those four instead of levying them on the front line.
2. "Next step" must be an action plus a date, never a status. "Keep following up" and "waiting on the customer" don't count. "Turn the reconciliation piece into a 20-minute demo and send it to Zhang by 6 November" does.
3. Never make CRM activity counts a performance metric. The moment calls logged becomes something people are judged on, you've imported the crowding-out problem from the last move straight into your system, and the data turns beautiful and useless. A CRM should be the seller's own workbench: it remembers what he has to do, rather than watching what he did.
What to say in the weekly meeting: "The next-step dates on these three have passed. Those are the only three we're discussing — are they stuck, or should they be closed out?"
Mechanism: intentions become actions not through resolve but by being hung on a specific time and situation, so that nothing has to be decided again in the moment. Meanwhile, writing down a tacit process that exists only inside one head is what lets a team stop depending on that person — but externalising has no magic of its own. What works is people genuinely changing behaviour because of it.
Boundary: with two or three people the benefit is mostly not forgetting things, and a shared spreadsheet is plenty. Only two signals really call for a system — handoffs starting to happen and forecasting starting to matter. Adopt too early and you'll spend months configuring a system with no data in it. Also, a checklist governs "don't drop things", not "should we work this deal at all" — that's qualifying, and no field will decide it for you.
Ninety minutes with the team you have — even if that's just you.