The Sales Team Parity Argument
Ask for exactly the accountability sales gets: budget, experiments, and outcomes — not named deals on named dates.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
A rhetorical and operational framework for winning the right to work without fixed delivery dates. Bastow points out that product is the only function required to name what will be delivered and when. Sales is not: they commit to a pipeline process and an aggregate number, not to which specific customer will sign. You should ask for the same terms — investment in, experiments run, numbers moved.
Origin
Janna Bastow's argument, developed for defending Now-Next-Later to sceptical leadership.
Core principles
- 01Product is uniquely and unfairly asked to predict specific outcomes in advance.
- 02Sales calls are experiments — they know some will convert and some will not, they just cannot say which.
- 03The credible commitment is process plus aggregate outcome, not itemised prediction.
- 04You should be accountable for the experiments you ran and the money you spent, not for knowing what would work before you knew it.
How to run it
- 1
Name the asymmetry out loud
Point out that a VP Sales does not walk into a board meeting and say they will close the Acme deal at the end of October for a million pounds. They cannot know that.
- 2
Describe what sales DOES commit to
A process to fill a pipeline, a budget to spend on account executives, and near-certainty on an aggregate number by quarter-end — grounded in the fact that someone bought last quarter and the quarter before.
- 3
Translate the structure to product
Ask for the same shape: give me a budget, I will spend it on a team running experiments — an interface change, a pricing tweak, a positioning change. Some will fail, some will succeed, and by quarter-end enough will succeed to move the right numbers.
Pro tip If they could tell you in advance which calls would convert, sales would only make those calls. Same logic applies to your experiments.
- 4
Offer the accountability you CAN carry
Commit to reporting how many experiments you ran last quarter and which numbers moved in the right direction. Explicitly refuse accountability for predicting which experiments would win.
Pro tip Build the track record first — the sales argument only works if you can actually point at last quarter's experiment count and moved metrics.
Watch out This is not a request for less accountability. If you use it to escape measurement entirely, leadership will correctly reject it.
In the wild
A VP Sales asks for a quarter of a million dollars of investment into the team. They spend it on account executives who pick up the phone and run calls. Some calls work, some fail; nobody knows in advance which. What they commit to is the process, the spend, and the aggregate number by quarter-end.
→ The board accepts it as a legitimate commitment. Bastow's point: you are asking for no more leeway than that, so the same commitment shape should be acceptable for product.
Common mistakes
Playing the timeline magic eight ball
Continuing to supply confident delivery dates you cannot know teaches leadership to keep demanding them and guarantees you will be judged against fiction.
Asking for freedom without offering the substitute metric
Dropping dates without producing an experiment count and moved-numbers report reads as evasion. The substitute accountability has to arrive at the same time as the removed one.
Is it for you?
Best for
Product managers and heads of product who need to persuade a CEO, board, or sales-led leadership team to accept an outcome-based commitment instead of a dated feature list.
Not ideal for
Agency or client-services contexts where the customer is literally paying for a specified deliverable on a specified date.
From the transcript
“product people are the only ones who seem to be pinned down to be required to give concrete dates as to when things are going…”
“you should be accountable for your experiments and how you're spending the money and what you're doing but you shouldn't be accountable for saying what…”
From the episode
Building better product roadmaps
Janna Bastow (Mind the Product, ProdPad)