OLD SCRIPT DETECTED
“One more feature and then it'll sell itself”
Try this response:
“The two years are spent either way. The only live question is where the next quarter goes.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“One more feature and then it'll sell itself”
YOUR RECORDED RESPONSE
“The two years are spent either way. The only live question is where the next quarter goes.”
ONE PRIVATE MOVE
In your next sales conversation, when someone mentions a missing feature, ask: "If we built that, would you buy?" Write their exact answer in a private note and close the document without deciding anything.
The Feature That Never Closes the Sale
- 01 / The Moment After the Demo Falls Flat
You're in the call with a prospect who said yes to the meeting. You walk through the product—the core flow, the integrations, the polish you've sweated. Silence. Then: "It looks nice, but we'd need [blank]." Not criticism. Not hostility. Just a gap between what exists and what they'd pay for. You nod, take the note, and the call ends with "let's stay in touch." Two hours later, you're in Slack naming that gap as a feature card. Not investigating why it matters to them. Not asking what would make them move now. Just: we're building that next.
- 02 / Why Adding It Feels Like Progress
Each feature you ship is a small proof that the direction is right, that iteration is the answer. The roadmap grows longer, more detailed, more defensible. You show it to yourself: six months of work mapped out. Meanwhile, the core metric—signups, activation, retention—hasn't moved in months. But the feature work is visible. You're doing something. And each new card is a reason to delay the sales conversation you're afraid of: the one where you learn that the problem isn't the product, it's the fit, the price, the timing, or the person you're selling to. One more feature means you don't have to know that yet.
- 03 / The Moment You Can Choose Otherwise
Next time someone on a call says they need something you don't have, pause before adding it to the roadmap. Instead, ask: "If we built that, would you buy?" Don't prompt them to say yes. Listen to the answer—and the hesitation around it. If the answer is soft or conditional, the feature isn't the problem. The feature is the thing you build so you don't have to sit with that softness. You can write down what you heard. Close the doc. Walk away. The clarity you get from that one unflinching question is cheaper than three months of engineering work, and it actually moves the needle.
TRACE · 01/04
How this script runs you
- You call it iterating; the metrics call it the same flat line for six months.
- The roadmap grows a new feature every time a sales conversation gets scary.
- There are dashboards you've stopped showing to yourself, let alone the board.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Sunk-Cost Cockpit
Two years in means two years owed—turning now would make it all a waste. But the two years are already spent. The only live question is where the next quarter goes. If the product could sell itself, it already would have. The next feature is a hiding place; the next unflinching call is the test.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The two years are spent either way. The only live question is where the next quarter goes.
- If the product could sell itself, it already would have. The next feature is a hiding place; the next call is the test.
- A pivot doesn't erase what I learned—it's the only way to cash it in.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“One more feature and then it'll sell itself”
I say
“The two years are spent either way. The only live question is where the next quarter goes.”
Then I do one thing
In your next sales conversation, when someone mentions a missing feature, ask: "If we built that, would you buy?" Write their exact answer in a private note and close the document without deciding anything.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "One more feature and then it'll sell itself". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
Doesn't asking 'would you buy' sound pushy or desperate?
It sounds direct. Most people respect directness. It also stops you from guessing what they mean. If they say 'maybe someday' or 'possibly,' that's data—and it's different from 'yes, that would close it for us.' You're not demanding they commit; you're asking them to be honest so you can stop building on assumptions.
What if they say yes to the feature but still don't buy after I build it?
That's the risk you're testing. Building first and asking after is the expensive version of that same risk. Asking first just makes the risk visible before you've spent the time. If they say yes and don't buy later, you've learned that the feature wasn't the real blocker—and you can investigate what was before you've added five more cards to the roadmap.
How is asking one question different from just launching the feature and seeing if it moves the needle?
One question gives you signal in minutes. A feature launch takes months and still doesn't tell you why someone bought—or why three others didn't. You're not choosing between perfect information and none; you're choosing between a ten-minute conversation and three months of work that might be addressing the wrong problem entirely.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Cleaning Up the Big Muddy: A Meta-Analytic Review of the Determinants of Escalation of Commitment — Sleesman, Conlon, McNamara & Miles, Academy of Management Journal, 2012
- The Pivot: How Founders Respond to Feedback through Idea and Identity Work — Grimes, Academy of Management Journal, 2018
- The Recovery Experience Questionnaire — Sonnentag & Fritz, Journal of Occupational Health Psychology, 2007