In partnership with
You did everything right.
You built rapport. You explained the value. You handled the objection.
Then you asked. And something went wrong.
Most people spend hours preparing what to say before the ask. Almost nobody practices the ask itself. The result is a conversation that builds well and collapses at the moment it matters most. Not because the offer was wrong. Because the way the question was framed created friction where there should have been none.
This is the part of influence nobody talks about. Not the pitch. The ask.
There are three ways people ask for a yes. Two of them reliably produce hesitation. One of them does not.
Last week Viktor wrote a brief, built a landing page, and opened a pull request.
Last week, Viktor wrote a campaign brief, built a landing page, opened a pull request, generated a board-ready PDF from live Stripe data, and sent a follow-up email to a churned customer. All from Slack. Same colleague that also pulls your reports and monitors your dashboards. 5,700+ teams. 3,000+ integrations.
The justification ask.
"I really think this would work for you because X, Y, and Z, so I wanted to see if you would be interested."
This sounds confident. It is not. Justification before an ask signals insecurity. The brain of the person you are talking to registers the explanation as evidence you expect a no. When you expect a no, so do they.
The justification ask also gives the other person something to argue with. You have handed them three reasons. They only need to disagree with one.
The permission ask.
"Would it be okay if we moved forward?"
This sounds polite. It is not strategic. Asking permission makes the other person's comfort the priority instead of the decision. It also invites a softer no. "I need to think about it" is the natural answer to a permission ask. The conversation ends without ending.
The assumption ask.
"What would you need to see to get started this week?"
This is different in structure from the first two. It does not justify. It does not ask permission. It assumes the decision is moving forward and asks only about the conditions. The other person either answers the question, which moves the conversation forward, or they surface the real objection, which is the information you actually needed.
The assumption ask does not pressure anyone. It creates clarity. Most conversations stall not because someone wants to say no but because nobody has named what a yes actually requires.
This is not a typo: they build your store free
The hardest part of e-commerce isn't selling. It's everything before your store goes live.
Live Store Build skips all of it — live, on the call, right now. Adrian Morrison's team builds your Shopify store in 30 minutes. Custom theme. Real products. Ready to sell when you log off.
Click in. Your store goes live today.
Chris Voss calls this calibrated questions. Questions that cannot be answered with yes or no, that require the other person to think and respond with information. "What would you need to see" is a calibrated question. "Are you interested" is not.
The structural difference matters because of how the brain processes the two formats. A yes or no question produces a binary response. A what or how question produces a thinking response. Thinking responses reveal information. Binary responses reveal nothing except the current emotional state of the person you are asking.
This week's articles have been building toward this point. Monday was about what happens before the conversation. Tuesday was about what to do when it breaks down. Wednesday was the one sentence that reopens a closed door. Thursday is the moment the door is open and you have to walk through it.
The ask is the walk.
Most people hesitate at this point not because they do not know what to say but because they are afraid of making the other person uncomfortable. That fear produces justification asks and permission asks. Both of which create the discomfort they were designed to avoid.
The assumption ask feels more direct. It is. And directness, delivered without pressure, is the thing people consistently respond to better than they expect.
Speak the email. Send the email.
Talk through your reply and get polished, professional text ready to paste. Wispr Flow strips filler, fixes grammar, and formats everything. 89% sent with zero edits. Works everywhere.
This week's micro-action:
Write out your current ask. The actual words you use when you are ready for a yes.
Then identify which type it is. Justification, permission, or assumption.
If it is not an assumption ask, rewrite it as one. "What would you need to see to get started this week?" is the template. Adapt it to your context.
Use it once before Sunday. Once. Real conversation, not practice.
Pro members get full access to all Tuesday and Thursday deep-dives and FREE products from our product list.
Subscribe to PRO Member to read the rest.
Become a paying subscriber of PRO Member to get access to the transformational content on this post and other subscriber-only content.
UpgradeA subscription gets you:
- 🔒 Premium-only guides on mindset, emotional control, conflict, and influence
- 🎁 Downloads & tactical playbooks (for real-world use, not fluff)