Negotiation·October 5, 2026·5 min read

How to Negotiate When the Other Side Has More Leverage

Low leverage doesn't mean no ask. Start with the smallest version of what you want, lead with their problem, and treat a first "no" as a data point.

When the other side has more leverage, you negotiate by shrinking the ask, not by skipping it. Ask for the smallest version of what you want first, lead with what's useful to them, and keep your constraints to yourself.

Most people with weak leverage do the opposite. They don't ask at all.

Why low-leverage people skip the ask

The logic feels sound: "They hold all the cards. Asking will just annoy them. I'll take what I'm given."

But that logic treats the ask as a demand. A demand needs power behind it. A request doesn't. A request costs the other side almost nothing to hear, and that's the opening you work with.

Here's what skipping the ask actually costs you:

  • You lock in their opening offer as the final one.
  • You teach them you don't push, so the next offer starts lower.
  • You get zero information about what was actually flexible.

You can't walk away, so your goal is different. You're not trying to win. You're trying to move the number, the date or the scope by a notch, without making the person across from you feel threatened.

The tactic: ask for the smallest version first

Break your real want into its smallest piece. Ask for that piece, not the whole thing.

Say your manager hands you a project with a deadline you can't hit. You can't refuse. You have no leverage. The big ask is "move the deadline two weeks." That sounds like you're pushing back on the work itself.

The small ask is: "Can I send you a first section on Thursday so you can see direction before I finish?"

That's easy to say yes to. And a yes changes the situation. You've created a checkpoint, you've shown you're engaged, and the full deadline is now easier to discuss because you've already delivered something. We cover the full version of this in how to negotiate a deadline without looking incapable.

The same move works elsewhere:

  • Salary: Not "I want 15% more." Try "Can we agree to revisit this at six months, with specific targets?"
  • A vendor contract: Not "drop your price." Try "Can you match the price on the first quarter so we can start?"
  • A landlord: Not "waive the increase." Try "Can we phase it in over two payments?"

Small asks work for three reasons. They're hard to refuse without sounding unreasonable. They get you inside the conversation. And once someone says yes to a small thing, they're more likely to say yes to the next one. People like to stay consistent with what they just agreed to.

What to lead with

Open with their problem, not yours.

You have no power to make them care about your constraints. You do have the ability to show how your request helps them. So start there.

Instead of: "I can't take on this much, I'm already overloaded."

Say: "I want this done right, and I think a Thursday draft gets you something to react to early."

Same request. Different frame. The first sounds like a complaint. The second sounds like a plan that serves their goal.

Keep it short. Low-leverage people over-explain because they're nervous, and every extra reason gives the other side something to argue with. One reason, stated plainly, is stronger than five. If you tend to ramble when you're under pressure, being direct without sounding blunt covers how to trim without sounding cold.

What to withhold

Three things stay in your pocket:

  • Your walk-away point. If you say "I really need this job," you've told them you'll accept almost anything.
  • Your deadline pressure. "My lease ends Friday" hands them your clock. Their patience becomes your weakness.
  • Your full wish list. Reveal one ask at a time. If you list everything up front, they can say no to the whole bundle in one go.

Withholding is not lying. You're just not volunteering information that only helps them. If they ask directly, don't invent a story. Redirect: "I'd rather focus on what works for both of us. What's the flexibility on your side?"

That last question is also your best source of information. Ask it and then stay quiet. People fill silence, and what they fill it with is often exactly what you needed to know.

Why "no" isn't always final

A first "no" from a stronger party usually means one of four things: "not now," "not that version," "I don't have the authority" or "I haven't thought about it yet." Only the fourth word, "never," is truly final, and you hear it far less often than you'd expect.

So treat the no as information. Ask:

  • "What would need to be true for this to work?"
  • "Is it the timing, the amount or the principle?"
  • "If not this, what could you do?"

Your manager says "We can't move the date." You say: "Understood. What part of the scope is least critical if the date holds?" You've accepted the no and opened a second door in one sentence.

When you hear the no, don't argue and don't collapse. Stay curious. Arguing tells them you're pushing. Collapsing tells them pushing works the other way. Curiosity keeps the conversation open without costing you anything. If criticism or pushback makes you defensive in the moment, listening without getting defensive is a skill worth building first.

Run it before it counts

The hard part isn't knowing the tactic. It's saying the small ask out loud when your pulse is up and the other person has all the power.

That's a repetition problem. Practice in ConvoForge lets you run the conversation against an AI that pushes back, says no, and tests whether you stay calm and ask the follow-up. Ten rounds in ten minutes, and the real conversation feels like a repeat, not a first attempt.

Before your next high-stakes ask, write down the smallest version of what you want. Then say that one first.

Published October 5, 2026 · More articles →