Handling common sales objections in LinkedIn messages

Learn how to answer price, timing, and competitor objections in LinkedIn DMs with short, low-friction templates that move conversations toward meetings.

Get started

Short answer

Handling objections in LinkedIn messages takes shorter, less formal replies than a call or an email. Accept the objection in one line, ask one question that shows you understood it, and offer a small next step. The aim is to keep the thread open until there is a reason to talk.

What an objection in a LinkedIn DM actually means

A prospect who types 'this is too expensive' into a LinkedIn chat is not asking for a pricing breakdown. They are deciding whether you are worth another thirty seconds. A long reply reads as pressure, and pressure ends the thread.

LinkedIn is a chat window. Email habits don't transfer: no greeting, no signature, no five-paragraph justification of your value. Two or three sentences and one question is the whole format, and it works because it looks like something a person would type.

The reply has one job, which is to keep the thread open until there is a reason to get on a call. Winning the argument in the DM gets you a well-argued dead thread.

The worst replies answer a question nobody asked. A prospect says the price is high and gets a feature list. A prospect says they're busy and gets a lecture about time management. Read the objection as written and answer that one thing.

Most objections fall into four buckets: price, timing, a competitor, or an in-house build. Each needs a different question, and none of them need a defence.

The defensive reply

  • I understand you feel it's expensive, but if you look at our feature list we offer more value than anyone else in the market, and several case studies prove the return.
  • I'm sorry you're busy, but this only takes 15 minutes and it will save you hours every week, so it's actually a time saver for you.

The curious reply

  • Fair. Is the cost of the problem on a spreadsheet anywhere, or is it still invisible?
  • Makes sense. Is the busyness the problem itself, or the thing stopping you from fixing it?

One line to accept the objection, one question to understand it, one small next step. Keep the whole reply under three sentences.

Answering price and budget objections

A price objection on LinkedIn usually means the value isn't visible yet. Drop your number in the first reply and you have told the prospect the original figure was invented.

Move the conversation to the cost of the problem instead. If the problem is expensive enough, budget appears. If it isn't, you found out early, which saves you a month of follow-ups.

Treat 'no budget' and 'too expensive' as different objections. No budget means the money is committed elsewhere this year. Too expensive means the number doesn't match the value they see. One needs a date, the other needs a conversation about what the problem costs.

The question that does the work is what they're comparing your price to. A competitor's quote, a hire they didn't make, or nothing at all. Each answer sends you somewhere different.

If they name a real number, ask what it would take to make that number work. Sometimes the answer is a smaller starting scope, sometimes it's a different month. Both are better than a discount you volunteered.

Example

  1. Prospect

    This looks expensive for what we need.

  2. You

    Fair. What are you comparing it against, another tool or the cost of leaving things as they are?

  3. Prospect

    Honestly, we don't have budget this year.

  4. You

    Understood. Does the problem sit still until next year, or does it get worse each quarter?

  5. Prospect

    It gets worse. It's costing us time every week.

  6. You

    Then it may be worth 15 minutes to see if there's a way to start small this year. Thursday or Friday?

When they say the timing is bad

'Let's revisit in six months' is the most common way to end a LinkedIn thread without being rude. Take it as a real answer and a soft no at the same time.

You have two moves. Accept the date and stay useful until then, or test whether the delay is safe. Testing means asking what happens if the problem is still there in six months. If they can't answer, the timing was a brush-off.

A brush-off usually means the message didn't give them a reason to keep talking. The next one might.

Whichever you pick, put the date in your calendar and follow up on it. Missing a date the prospect gave you is worse than never asking for one.

Let's revisit in six months

What they said
A polite no, or a real budget cycle
What it usually means
Ask what changes in six months, then book the follow-up for that week

I'm slammed right now

What they said
The problem isn't urgent enough yet
What it usually means
Ask whether the busyness is caused by the problem you solve

Send me some information

What they said
They want to close the chat politely
What it usually means
Send one page and ask a question about it so the thread stays open

We're locked in until March

What they said
A real constraint with a real date
What it usually means
Book the conversation for the month before renewal

Paste this job

No problem, I'll come back to you in October. One question before I do: if the problem is still costing you time in six months, what will have changed? If the answer is nothing, I'll leave it there.

When they mention a competitor or an in-house build

Don't run down the other company. The prospect picked it, and insulting it insults them. Ask what it doesn't do and let them tell you where the gap is.

In-house builds need a different angle. Someone on their team built it and is proud of it. Praise the build, then ask about upkeep, because maintenance is where internal tools quietly eat a team's week.

The question that lands hardest is what happens when the person who built it changes team or leaves. Most teams have never written that down.

Running down the other tool

  • Acme is outdated, most of their customers are moving to us because the reporting doesn't work.
  • Building it in-house was a mistake, you'll spend more on maintenance than on a proper tool.

Asking about the gap

  • Acme is a solid tool. What made you look at anything else?
  • That's a real build. Who maintains it now, and what happens when they change team?

Example

  1. Prospect

    We already use Acme for this.

  2. You

    Acme is a solid tool. What made you look at anything else?

  3. Prospect

    The reporting is manual. We export everything into a spreadsheet.

  4. You

    Manual exports are the usual reason people end up talking to us. How long does the export take each month?

Turning the objection into a booked call

An objection reply that ends with no next step leaves the thread to die. Every answer should end with something small the prospect can say yes to.

  1. 1

    Accept it in one line

    Fair. Makes sense. That's a real constraint. Don't apologise and don't explain your pricing model.

  2. 2

    Ask one question that sorts a real block from a brush-off

    Ask about cost, timing, or what happens if nothing changes. One question, not three.

  3. 3

    Offer a next step that costs them almost nothing

    15 minutes on Thursday, a one-page summary, a follow-up in the month they named. Vague offers like 'a quick chat sometime' get ignored.

  4. 4

    Send it and stop typing

    One follow-up after a few days, one more if they gave you a reason. Then leave it alone.

If a prospect gives you a date, follow up on that date. Nothing kills a warm thread faster than missing the deadline they set for you.

Building a shared objection playbook

If two people on the same team answer the same objection differently, you can't tell which reply works. Write the answers down, keep them short, and review them with the people who send the most messages.

One page per objection is enough: what they said, what it usually means, two replies, and the question that follows. Anything longer gets ignored in a busy week.

  • Copy the exact wording the prospect used. 'Too expensive' and 'no budget' need different replies.
  • Write two versions of each reply, one that accepts the objection and one that tests it.
  • Add the question that comes after, because the question is what keeps the thread alive.
  • Delete replies nobody has sent in a month. A playbook full of dead scripts stops getting opened.
  • Review it monthly with whoever sends the most messages. They hear the objections first.

Doing this with Kinlead

Kinlead writes messages and follow-ups from a campaign's goal, tone and an optional sales playbook, which is your own script. Paste your objection replies into that playbook and the drafts start from your wording.

Each campaign chooses how replies are handled: hand the conversation to you at the first reply, let the AI reply until there is real interest, or let the AI reply until a meeting is booked using your scheduling link. Hand-off mode makes sense while you are still learning which replies work. Replies from every campaign land in one inbox, classified by intent, with interested replies first, and you get an email when someone replies. More on AI LinkedIn outreach.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? Handling common sales objections in LinkedIn messages.md