How to handle requests for custom features on LinkedIn
Learn how to reply to prospects asking for custom features without promising roadmap changes. Qualify if a request is a dealbreaker or a nice to have.
Get startedShort answer
When a prospect asks for a custom feature on LinkedIn, don't say yes or no immediately. Use a discovery approach to find the problem they are trying to solve. This helps you determine if the feature is a dealbreaker or just a preference.
Stop the yes or no reflex
The natural reaction to a feature request is to want to close the deal. This often leads to saying yes to a roadmap change that doesn't exist or saying no and killing the conversation. Both responses are mistakes because they stop the discovery process.
If you promise a feature to win a customer, you create a churn risk. The customer buys based on a promise, but they leave when the delivery date slips or the final version doesn't match their mental image. I watched a founder promise a custom reporting view to close a $12k deal. The view shipped four months late and missing two columns. The customer churned in month six and told three other prospects.
If you say no immediately, you miss the chance to find out why they actually need that function. The request is a clue. It's not the whole story. Treat it like a symptom and dig into the cause.
If you need time to think, say so. 'Let me check with the product team and get back to you tomorrow' is better than a guess. It buys you a day and shows you take the request seriously.
The reflex
- Yes, we can definitely add that to our roadmap for you.
- No, we don't have that. Sorry about that.
- I'll add it to the backlog and let you know.
The discovery approach
- I'm not sure if that's on our current plan, but I want to understand how you'd use it to see if we have a workaround.
- We don't have that specific button, but what's the end goal you're trying to achieve with it?
- That's not something we've built yet. Can you walk me through what happens right before you'd use it?
Dig for the underlying problem
A feature request is rarely about the feature itself. It's a request for a specific outcome. Your job is to peel back the layer of the tool they are asking for to find the pain they are feeling. Ask about the workflow before and after the missing step.
Use questions that force a concrete answer. 'How do you handle that today?' is better than 'Why do you need it?' because it gives you a process, not an opinion. Ask them to describe the last time they hit the problem. Specific stories reveal more than hypothetical needs.
If they say they need a Slack integration, ask what message they would send to Slack and who would read it. If they say they need a custom field, ask what they would put in it and what decision it would change.
Don't ask leading questions. 'So you need it for reporting, right?' puts words in their mouth. Ask open questions and let them describe the problem in their own words.
Example
- Prospect
This looks great, but do you have a Slack integration?
- You
We don't have that right now. What would you want to push into Slack?
- Prospect
I just want my team to see when a lead replies without checking another tab.
- You
Got it. So the goal is real-time visibility for the team, not Slack specifically.
Paste this job
Discovery questions to paste into your notes: 1. What are you doing today to solve this? 2. Walk me through the last time this problem came up. 3. Who else on your team feels this pain? 4. What happens if you can't solve it for another six months? 5. If you had the feature tomorrow, what would change in your workflow?
Qualify the need
Once you know the problem, you need to decide if this is a dealbreaker. Some prospects ask for things because they are used to another tool, not because they actually need the function to get the job done.
You can determine the priority by asking about their current state. If they have a manual workaround they've used for a year, the feature is a convenience. If their entire process is broken without it, it's a requirement. The difference matters because you don't want to lose a good customer over a nice-to-have, and you don't want to promise a feature that will never ship to win a deal that will churn.
Ask directly: 'If we can't do this, is that a dealbreaker for you?' Most prospects will tell you the truth. They appreciate the honesty more than a vague promise.
Write down the request and the underlying problem in your notes. If you use a shared inbox, tag the conversation. When the same request comes up three times from different prospects, that's a signal for the product team, not a one-off.
- 1
Ask about current workarounds
Ask how they handle this problem today. If they have a system, the pain is manageable. If they have nothing, the pain is urgent.
- 2
Test the timeline
Ask what happens if the feature doesn't exist for another six months. If they can't operate, it's a dealbreaker. If they can wait, it's a preference.
- 3
Categorize the request
Decide if this is a must-solve for their workflow or a nice-to-have for convenience. Write it down so you remember when you follow up.
Current workaround
- Signal
- No workaround exists
- Dealbreaker
- Manual process they've used for months
Timeline
- Signal
- Needs it before next quarter
- Dealbreaker
- Can wait six months or more
Budget impact
- Signal
- Won't sign without it
- Dealbreaker
- Will sign and ask for it later
Team impact
- Signal
- Blocks the whole team
- Dealbreaker
- Only one person cares
Offer an alternative solution
Many times, you can solve the underlying problem with a different feature you already have. The prospect just doesn't know it's possible because they are focused on the specific tool they're used to.
Present the alternative as a way to achieve the outcome faster. Don't argue about why the requested feature is unnecessary. Instead, show them a path to the result they want. If you don't have an alternative, say so and explain what you do have. Then ask if they want to proceed without it. Sometimes they will.
Be careful not to oversell the alternative. If it's a workaround, call it a workaround. Prospects can tell when you're stretching a feature to fit their request.
If the alternative is a real solution, show it. Don't just describe it. Send a screenshot or a short video. Prospects believe what they see more than what you say.
Automated weekly email reports
- Feature request
- Needs to show boss progress without logging in
- Underlying problem
- Export CSV of activity every Friday in two clicks
Direct API integration
- Feature request
- Needs data in another tool for reporting
- Underlying problem
- Weekly CSV import into the reporting tool
Custom dashboard widgets
- Feature request
- Needs to see a specific metric at a glance
- Underlying problem
- Set up a filtered view and bookmark the URL
Slack notifications
- Feature request
- Team needs real-time visibility of replies
- Underlying problem
- Email alert on every reply and a shared inbox
The brush-off
- We don't have that, but you can just use the export.
- That's not on our roadmap. Let me know if you still want to buy.
The alternative
- You mentioned you need the team to see replies without checking another tab. We don't have Slack, but the unified inbox shows every reply in one place and you can set an email alert for new replies. Would that cover it?
- I hear you on the custom dashboard. We don't have widgets, but you can save a filtered view and bookmark it. That gives you the same number in one click. Want me to show you how?
Write the reply so it doesn't sound like a brush-off
The tone matters. A blunt 'we don't have that' feels like a dead end. A reply that acknowledges the request and asks a follow-up question keeps the conversation alive.
Use a three-part structure: acknowledge, ask, offer. Acknowledge the request without promising anything. Ask about the underlying need. Offer a next step or an alternative. This works in a LinkedIn message, an email, or a call.
Keep it short. You don't need a paragraph. Two sentences is enough to show you're listening and you're not going to promise something you can't deliver.
If the prospect asks for a feature that already exists but they didn't see it, point them to it without making them feel stupid. Say 'We do have that. It's called X and here's where to find it.' Then ask if that solves their problem.
Example
- Prospect
Before we book a call, can you confirm you have a custom fields feature?
- You
We don't have custom fields yet. What would you store in them?
- Prospect
I need to tag leads by industry so I can filter my list.
- You
Got it. We don't have custom tags, but you can use lead groups to separate by industry and filter from there. Would that work for your list?
- Prospect
Maybe. Can you show me on the call?
Never say 'I'll add it to the roadmap' unless you have the authority and a real date. Say 'I'll share it with the product team' instead.
Paste this job
Reply template: "We don't have [feature] right now. Can you tell me what you'd use it for? I want to see if we have another way to get you the same result."
Doing this with Kinlead
Kinlead helps you find leads and start conversations. When a prospect brings up a custom feature in a reply, you can set the campaign to hand the conversation to you at the first reply. That way you run the discovery yourself and don't let an AI reply promise something you can't deliver.
All replies from every campaign land in one inbox, classified by intent, with interested replies first. You can see which prospects are asking for features and prioritize the ones that sound like dealbreakers. Use the unified inbox to manage those conversations.
To handle feature requests manually, set your campaign to hand off at the first reply. You can change this per campaign.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to handle requests for custom features on LinkedIn.md