How to answer a LinkedIn request for a discount code
Answer a LinkedIn prospect asking for a discount code without cutting your price or losing the deal. Scripts and trades that you can copy today.
Get startedShort answer
Ask what they're trying to fix before you talk about money. If a discount makes sense, trade it for something you need, like annual payment or a testimonial. If your price is firm, say so once and ask whether the number is the real blocker.
Work out what the request actually means
A message that says "do you have a discount code" tells you almost nothing on its own. It could come from someone who read your pricing page and decided the number is close, or from someone collecting codes from every tool on their list. Your reply depends on which one you're talking to.
Read the message before it. If they described a problem first, the code is a last hurdle. If the code is the first thing they mention, price is doing all the work and the product hasn't landed yet. Ask about the problem before you talk about money.
One more thing to check: who is asking. A founder or a team lead can usually settle a rate in one call. Someone evaluating for a manager is often collecting prices to compare later, and a code you hand over gets forwarded to a person you never speak to.
Someone shopping for a code
- Opens with the code request and nothing else
- Can't name the thing they're trying to fix
- Goes quiet when you suggest a call, then asks the same question a month later
Someone close to buying
- Mentions a deadline, a team rollout or a tool they're replacing
- Asks what the discount requires before asking how big it is
- Has already used the trial or sat through a demo
- Names the person who signs off on the budget
Ask what they're fixing before you talk about money
A yes in the first message turns your price into a starting bid. A no ends the conversation. Neither gets you anywhere. Reply with the thing you don't know yet, which is what they're trying to do and who else has a say in it.
One question is enough. Two questions in one message reads like a form, and the short reply typed on a phone is the one you'll get an answer to.
Notice what the last line in the exchange below does. It doesn't promise a code. It promises a decision after ten minutes, which gives the buyer a reason to spend the time even if they never get a discount.
Example
- Prospect
Hey, is there a discount code for the Pro plan? Looking at it for my team.
- You
There's no public code, but I can usually get something approved when the fit is right. What are you trying to fix with it?
- Prospect
Our SDRs have no good way to find the right people on LinkedIn, so someone rebuilds the list by hand every week.
- You
That's the case most teams bring us. Ten minutes on a call and I'll know whether a discount makes sense, and whether the plan fits a team your size.
- Prospect
Can't you just send me the code?
- You
I can't, because the rate depends on seat count and how you'd roll it out. If we're not a fit after ten minutes I'll tell you straight, and you've lost nothing.
Trade the discount for something you need
A discount with no condition is a price cut with extra steps. It teaches the buyer that your list price is a starting point and that waiting long enough gets them a better one. Tie every reduction to something that costs them a little and helps you.
Pick the trade that fits the deal. A small team with no reference calls yet can give you a written testimonial after a month. A larger team on a budget cycle can pay for the year up front. A team still evaluating can run the trial on their own data before the lower rate applies. Put the condition on the quote so nobody has to remember it at renewal.
The condition matters more than the size of the cut. A small reduction with a real commitment holds better than a large one given away to end an awkward call.
Watch renewal. If the discount was a one-off the buyer didn't earn, they'll ask for it again in twelve months and you'll have less room to move. A condition that runs for the length of the contract avoids that conversation.
Proof
- Trade
- A written testimonial after a month of real use
- The buyer gives
- A reference you can quote to the next prospect
Commitment
- Trade
- Pays for a full year up front
- The buyer gives
- Predictable revenue and a customer who stays past month one
Rollout
- Trade
- Brings a second team or a named colleague into the call
- The buyer gives
- A bigger account and a shorter cycle
Effort
- Trade
- Runs the trial on their own data before the rate applies
- The buyer gives
- A buyer who has watched the product work
When the number can't move
Some products don't discount. Maybe every customer pays the published rate, or the support cost is already in the number. Say that once, plainly, and stop there. Repeated apologies read as a hint that one more push will work.
Keep the answer short. Long explanations sound like a negotiation you're losing, and a buyer who hears three reasons starts arguing with all three.
- 1
Answer the question that was asked
Say whether a discount exists before you explain anything else. "No, we don't discount" is a complete answer. Then give the reason in one sentence.
- 2
Give the reason once
Describe what the price pays for in the buyer's terms: onboarding, a named person on support, whatever is actually true. Don't repeat it in the next message.
- 3
Ask whether it's a real blocker
Use a closed question: "Is the number the reason you'd hold off, or is it the timing?" The answer tells you whether to keep going or park the deal until next quarter.
- 4
Offer the smaller version
If budget truly decides it, offer fewer seats, the lower plan, or a start date after their next budget cycle. A smaller deal at full rate beats a discount that resets your price for the life of the account.
If you cut the rate to close today, that rate is the rate you renew at. Charge what you'll be happy to see on the invoice next year.
Replies you can copy
Keep every one of these to a single message someone could answer from a phone without scrolling. Change the wording to match how you talk, but keep the shape: one fact, one reason, one question.
Paste this job
When you don't know the fit yet: "No public code, but I can usually get something approved when it's a good fit. What are you trying to fix with it?" When you can trade: "If you're happy to pay for the year, I can give you two months free. Same product and same support, just committed for twelve months." When the price is firm: "We don't discount. The rate covers onboarding and support, and every customer pays it. If the number is the blocker, the smaller plan covers most of what you'd need. Want the comparison?" When they ask a second time: "I'd be doing you a disservice to promise a rate I can't hold at renewal. If the tool solves the list problem, the plan pays for itself. If it doesn't, a discount won't fix that either."
When they keep pushing after the no
Some people ask again, and then again with a different reason. Answer the second request once with the same sentence you used the first time. Repeating yourself is fine. Inventing a new excuse each round is what makes you sound uncertain.
If the third message is still about the code, stop replying to the price and reply to the problem. Send one line about what your product does for a team like theirs and leave the decision with them. You've said your piece, and the deal can sit until they have a real reason to move.
Doing this with Kinlead
Discount requests usually arrive after the first reply, which is where a campaign's reply setting matters. Kinlead campaigns can hand the conversation to you at the first reply, so pricing stays with a person. Or let the AI reply until someone shows real interest, then take over.
Put your pricing rules in the campaign's sales playbook, which is your own script, so early messages never promise a code you can't give. Replies from every campaign land in one inbox with interested ones first, and you get an email when someone writes back. To change a message before it goes, edit it on the Actions page, and pause any campaign while you decide on a rate. The reply handoff workflow covers both settings.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to answer a LinkedIn request for a discount code.md