Using LinkedIn to validate a B2B idea
Learn how to validate a B2B software idea on LinkedIn by interviewing target customers about their problems instead of pitching a product.
Get startedShort answer
To validate a B2B software idea on LinkedIn, stop pitching a product and start interviewing people about their problems. The goal is to find a recurring pain point that people are willing to pay to solve. Identify a specific target profile, reach out for their expertise, and ask open ended questions about their current workflow.
Define the problem you are testing
Most founders fail validation because they ask for opinions on a solution. People are polite and will tell you your idea is great, even if they would never pay for it. This creates a false positive that leads to building a product nobody wants.
You need to prove that a specific problem exists and that it is painful enough for someone to change their current behavior to fix it. Focus on the job to be done, not the tool you imagine using to do it.
Validation is about finding a gap between the current result and the desired result. If a person is not already trying to solve the problem with a clumsy workaround, they likely do not care enough about it to pay for a professional tool. Your goal is to find those clumsy workarounds.
Avoid asking if someone would use your product. Instead, ask how they currently solve the problem. If they say they do not have a way to solve it, the pain is not high enough. If they describe a complex system of spreadsheets and manual emails, you have found a real opportunity.
Pitching a solution
- Asking 'Would you use a tool that does X?'
- Sending a landing page or slide deck before talking to people
- Asking 'Does this feature sound useful to you?'
Validating a problem
- Asking 'How do you currently handle X and what is the most frustrating part?'
- Identifying a specific job title and a task they hate
- Asking 'When was the last time this problem cost you time or money?'
Find the right people to interview
Broad targeting leads to vague feedback. If you target 'Marketing Managers', you'll get generic answers. If you target 'Head of Demand Gen at Series A SaaS companies with 20 to 50 employees', you'll get specific insights into a shared set of constraints.
Look for people who are actively talking about the problem. People who post complaints or questions about a specific workflow on LinkedIn are the most likely to give you honest, raw feedback because they are already feeling the pain.
You can also look for people who have recently changed roles. A new executive often spends their first 90 days identifying what is broken in their department. They are more likely to admit to inefficiencies than someone who has been in the role for five years and has accepted the status quo.
Create a list of profiles before you start messaging. If you message people as you find them, you will be tempted to broaden your criteria just to get more replies. Stick to a strict persona to ensure the data you collect is consistent.
- 1
Pick a narrow niche
Define your target by a specific job title and company type, such as Head of Logistics at mid sized food distributors.
- 2
Search for problem-aware users
Use LinkedIn search to find people who have posted keywords related to the frustration you are solving.
- 3
Target recent role changers
Find people who started a new role in the last 90 days. They often notice inefficiencies in old processes and are more open to change.
- 4
Build a target list
Create a list of 20 to 50 profiles that fit this exact persona before sending a single message.
The outreach script
The goal of your outreach is to get a conversation, not a sale. If you sound like a salesperson, people will ignore you or give you the 'polite' answers you are trying to avoid.
Position yourself as a researcher or a founder trying to understand a problem. People are generally more willing to share their expertise than they are to listen to a pitch. Avoid using words like 'revolutionary', 'disruptive', or 'efficient' in your first message.
Keep the request small. Asking for a 45 minute demo is a big ask. Asking for 15 minutes of expertise to validate a hypothesis is a small ask. People like being viewed as experts in their field, so frame the request around their knowledge.
If they accept the connection but do not reply to the message, wait two days and send a follow up that mentions a specific detail from their profile. This shows you are not using a mass automation tool and actually care about their specific perspective.
Example
- You
Hi Sarah, I'm researching how Head of Logistics handle route optimization. I'm not selling anything, just trying to understand if the manual entry part is a common headache. Would you be open to a brief chat?
- Prospect
I've definitely struggled with that. Happy to chat for a few minutes.
- You
Thanks for connecting. I've noticed most people in food distribution struggle with the gap between the dispatcher and the driver. Is that true for you, or have you found a way around it?
- Prospect
It's a nightmare. We use a mix of WhatsApp and spreadsheets and it's a mess.
- You
I'm building a potential solution and want to make sure I'm not solving a problem that doesn't exist. Could I get 15 minutes of your expertise next Tuesday?
Running the validation call
During the call, your only job is to listen. If you start talking about your product, the interview is over because the person will switch from 'expert' mode to 'critic' mode. They will start telling you why your product won't work instead of telling you why their current process is broken.
Listen for the 'workaround'. If someone has built a complex spreadsheet or is paying a virtual assistant to do a manual task, you've found a real problem. If they say it's a problem but aren't doing anything to fix it, it's not a priority.
Ask about the cost of the problem. This does not always mean money. It could be hours of lost sleep, the risk of losing a client, or the frustration of a team. If there is no cost to the problem, there is no reason for them to buy a solution.
End the call by asking for referrals. People who are frustrated with a process usually know other people in their industry who are equally frustrated. This is the fastest way to grow your interview list with high-quality leads.
Tell me about the last time you dealt with this problem.
- Question
- Get a concrete example of a recent failure instead of a theoretical one.
What have you tried to do to fix this?
- Question
- See if they are already spending money or time on a workaround.
What happens if you don't fix this?
- Question
- Determine the cost of inaction and the urgency of the problem.
Who else should I talk to about this?
- Question
- Expand your lead list through referrals from trusted peers.
Analyzing the results
After 15 to 20 interviews, look for patterns. If every person describes the same frustration in the same words, you have a validated problem. If everyone gives you different answers, your target niche is too broad or the problem isn't acute enough.
The strongest signal is not a compliment, but a request for a timeline. When a prospect asks when they can try the solution, they have moved from being a research subject to a potential customer. This is the point where you can start talking about your product.
Categorize your interviews by the intensity of the pain. Some people will say it is an annoyance, while others will say it is a disaster. Focus your product development on the 'disaster' group. They are the ones who will pay for an early, unpolished version of your software.
If you find that people are not interested, do not try to convince them. Use the lack of interest as a signal to pivot. It is better to find out your idea is wrong now than after spending six months of engineering time building a feature nobody wants.
Avoid 'The Consensus Trap': If 10 people say the idea is 'interesting' but 0 people show you their current messy workaround, the idea is not validated.
Doing this with Kinlead
Kinlead automates the process of finding and contacting the people you need to interview. Instead of manual searching, you can describe your ideal customer and the system scores leads from 0 to 100 to ensure they fit your persona.
You can use the Steal Customers agent to watch competitor pages and identify people commenting on posts who are complaining about specific issues. This gives you a list of people who are already expressing the pain you want to validate.
Outreach runs from your own account through Unipile. To keep your account safe, Kinlead sends at a human pace, performing at most one action every 5 minutes and staying within the daily limits you set.
You can use AI-written connection notes under 200 characters that open with the reason why that person became a lead. This helps you avoid sounding like a generic bot and increases the chance that a busy executive will agree to a research call.
- 1
Find high-fit leads
Use Kinlead to identify people matching your profile and keep only those above your fit line.
- 2
Target competitor critics
Use the Steal Customers agent to turn commenters on competitor posts into leads, keeping the post URL and their specific comment.
- 3
Send research notes
Launch a campaign with AI-written connection notes that explain why you are reaching out for their expertise.
- 4
Manage the hand-off
Use the [unified inbox](/features/unified-inbox) to track replies and hand the conversation to yourself once they agree to a validation call.
You can see how this works by booking a demo.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? Using LinkedIn to validate a B2B idea.md