How to handle requests for a product roadmap
Learn how to respond when a LinkedIn prospect asks for your product roadmap without sending a static document that kills the sales conversation.
Get startedShort answer
Don't send a PDF or a link to a public board when a prospect asks for a roadmap. Static documents end conversations because buyers stop talking to you and start auditing a list. Instead, use the request to find the specific problem they're solving, then describe the future state of the product to confirm it fits their needs.
Why you shouldn't send the document
Founders and SDRs often think sending a roadmap PDF shows transparency. It actually shifts the power. Once you send a document, the prospect stops talking to you and starts auditing a list. They look for the one thing you don't have, decide it's a dealbreaker, and ghost you without telling you why.
A roadmap is a set of priorities, not a promise. When you send a static file, you commit to a timeline that might change by next Tuesday. If you miss a date listed in a PDF, you lose trust before the contract is signed. The prospect remembers the missed date, not the reason behind it.
The request for a roadmap is usually a proxy for a specific fear. The buyer isn't interested in your internal sprint planning. They're worried your product can't solve a specific problem they have right now. Your goal is to find that problem before you describe anything that might happen later.
There is also a practical problem with sending a document. A PDF or a public board gives the buyer something to compare against every competitor they are evaluating. They will put your roadmap next to three other roadmaps and look for the feature that appears in all four. That comparison rarely helps you, because the buyer is not comparing the thinking behind each plan. They are comparing checkboxes.
Sending the file
- Prospect asks for a roadmap.
- You send a PDF of the next two quarters.
- Prospect sees a missing integration.
- Prospect stops replying.
Asking why
- Prospect asks for a roadmap.
- You ask which functionality they need most.
- Prospect explains their specific workflow gap.
- You explain how that gap is being handled or prioritized.
The first response
Your first reply should be a pivot. You aren't hiding the roadmap, but you're refusing to let a document do the selling for you. The goal is to move from a general request to a specific requirement.
Don't say you don't have one, as that makes the company look unplanned. Instead, frame the roadmap as a dynamic tool that evolves based on user feedback. This makes the prospect feel like their input could influence the product direction. It also gives you a reason to keep the conversation open.
Keep the tone helpful and curious. You want to sound like a partner trying to ensure the product is a fit, not a salesperson dodging a question. If the prospect senses you are avoiding the request, they will assume the worst. If they sense you are trying to solve their problem, they will usually answer the question.
Example
- Prospect
This looks interesting. Do you have a product roadmap I can see?
- You
I do, but it changes quickly based on what our users need. Which specific functionality are you looking for to see if it fits your workflow?
- Prospect
I need to know if you'll support SOC2 compliance by Q3. We can't buy without it.
- You
That's helpful. Compliance work is on our list, and the timing depends on the audit window. Before I get into dates, what would you need to see in place to feel comfortable moving forward?
Categorizing the request
Once the prospect tells you what they're looking for, categorize the feature. Not all future features are equal. Your level of commitment should match the certainty of the build.
Be honest about where the feature stands. If you over-promise a date and miss it, you create a trust gap that's hard to close. If you're honest about a feature being in the backlog, you can often find a workaround that satisfies the buyer for now.
Use this to qualify the lead. If they require a feature you know you'll never build, it's better to find out now than after a month of demos. A clear no early in the process saves both sides time, even if it feels uncomfortable in the moment.
Confirmed (in development)
- Status
- It is coming in the next quarter.
- What to tell them
- Create urgency and confidence.
Planned (backlog)
- Status
- It is on our list. How would you use it specifically?
- What to tell them
- Uncover the actual use case.
Unknown (new idea)
- Status
- We haven't built that yet, but I'll share this with the team.
- What to tell them
- Validate demand without promising.
Moving from the roadmap to a call
The roadmap conversation is a bridge to a discovery call. Once you've identified the feature they need, don't just confirm it exists. Explain why it's a priority. This proves you understand their industry and their pain.
The transition should be based on the gap between where the product is today and where it will be. If the feature they want is coming in six months, ask if the current version solves their other immediate problems. This prevents the wait until it's ready trap. It also gives the buyer a reason to keep talking now.
Suggest a short, focused call. The objective isn't a full demo, but a synchronization of their needs and your build plan. A 15 minute call is easier to accept than a 45 minute presentation, and it keeps the conversation about their problem rather than your slide deck.
- 1
Acknowledge the need
Confirm you understand the specific feature or compliance standard they mentioned. Repeat it back in plain language so they know you heard it.
- 2
Explain the priority
Tell them why that feature is being built and how it fits into the overall direction of the product. Keep it to two sentences.
- 3
Test current fit
Ask if the existing features solve their most pressing problems today. If they do, the roadmap item becomes a bonus rather than a blocker.
- 4
Propose a sync
Suggest a 15 minute call to align their requirements with your development timeline. Give two specific times instead of asking for their availability.
What to say when the feature is not on the roadmap
This is the moment most reps get wrong. They either invent a date to keep the deal alive or they shut the conversation down with a flat no. Both responses end the relationship in different ways.
Start with the problem behind the feature. If the prospect wants a specific integration, ask what they are trying to accomplish with it. There is often another way to reach the same outcome, whether that is an export, a manual step, or a different workflow inside the product.
If there is no workaround, say so clearly. Then explain what you are watching for and why. You can say the request has come up before, that the team is aware of it, and that you will add this conversation to the notes. Do not promise a date you cannot control.
Leave the door open without misleading them. A prospect who hears an honest no and a clear explanation will often come back when the feature ships. A prospect who hears a fake yes will tell other buyers what happened.
Closing the door
- That isn't on our roadmap.
- We don't support that use case.
- Let me know if anything changes.
Keeping it open
- We don't support that today. What are you trying to do with it?
- There may be another way to get the same result. Can I show you?
- I'll add your use case to the notes for our product team. If it moves up, I'll reach out.
When to walk away
Some roadmap requests are not really about the roadmap. They are a way to test whether you will over-promise. If the buyer keeps pushing for a written commitment after you have been clear, that is a signal about how the rest of the deal will go.
You should also walk away when the missing feature is the entire product for them. If they need a compliance certification, a specific integration, or a workflow you do not support, a workaround will only delay the problem. They will churn or ask for a refund later.
Use the conversation to decide whether the fit is real. A prospect who can describe their problem, listen to your answer, and discuss alternatives is usually worth pursuing. A prospect who only wants a date on a calendar is not buying your product. They are buying a promise.
- They need a feature you have no plan to build and no workaround for.
- They ask for a written commitment before they will discuss their problem.
- They compare your roadmap to competitors line by line without explaining their own workflow.
- They keep changing the feature they need each time you answer.
Doing this with Kinlead
Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept. You can start these conversations with AI-written connection notes that explain why the person became a lead.
When a prospect asks for a roadmap, use hand-off workflow mode. The AI replies until the first reply and then hands the conversation to you. That gives you control over the nuance of a roadmap request without making the prospect wait for a human to notice the message.
You can also use the Steal Customers agent to watch competitor company pages and optional founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented. Those comments often mention missing features, which gives you a natural opening to ask what the person is trying to solve.
Roadmap requests need a human. Use hand-off mode so you can ask why the feature matters before you describe what is coming.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to handle requests for a product roadmap.md