How to Find People to Interview About a Business Idea

Finding ten people to interview about a new business idea is a mechanical sourcing problem. You do not need a warm network, and you do not need a working prototype. You only need to identify where people are already spending time or money to solve the exact problem you want to tackle. Most founders fail at this stage because they post vague requests on their personal social media accounts. This yields feedback from friends who want to be supportive, rather than truth from buyers who want a solution. To get real data, you must go to the places where the pain is already acute.

Mining review platforms for demand signals

The most direct route to your target user is through the tools they already pay for. When a customer pays for software and it fails them, they leave demand signals in the form of two-star and three-star reviews. One-star reviews are often unhelpful rants. Five-star reviews are useless praise. The middle tiers contain specific, detailed friction points from users who desperately wanted the product to work.

If you are building a tool for ecommerce operations, go to the Shopify App Store. Find the top three inventory management apps. Filter the reviews to show only the three-star ratings. You will find entries like "This app is great but it fails to sync bundled products correctly." The reviewer will almost always leave their store name. Take that store name to LinkedIn. Search for the company, look at the employee list, and find the Operations Manager or the Ecommerce Director. You now have a verified lead who experiences the exact problem you want to solve.

This method works across industries. For B2B software, use G2 or Capterra. For consumer hardware, use Amazon. For developer tools, search GitHub issue trackers. A founder spending four hours on G2 can easily extract fifty names of specific individuals who are actively frustrated by a competitor.

Infiltrating professional niche communities

Broad networks like Reddit or Twitter are too noisy for targeted sourcing. You need professional watering holes. These are highly specific Slack communities, Discord servers, and private forums where practitioners talk shop.

Finding these groups requires specific search operators. Do not search for "marketing community". Search for the exact phrases practitioners use when asking for access. Search Google for "join our slack" plus "operations managers". Look through directories like Slofile. Once you are in, do not introduce yourself as a founder doing research. This triggers immediate skepticism.

Instead, use the search bar. Query the core keywords of your business idea. If you are building a tool for API rate limiting, search the community history for "rate limit", "throttling", or "API blocked". You will find historical threads of users asking for help with this exact issue. Note the names of the people who asked the questions and the people who provided the most detailed answers. These are your interview targets. They have already demonstrated that they care enough about the topic to discuss it publicly.

Send a direct message referencing their specific post. State that you saw their question from three months ago, ask how they ended up solving it, and ask if they would be open to a ten-minute chat about their current workflow. This approach converts at a high rate because it is contextual and flattering. You are treating them as an expert based on their own public words.

Mining technical platforms for developer tools

If you are building a tool for developers, the sourcing strategy shifts to technical repositories. StackOverflow and GitHub are massive repositories of demand signals. Developers do not write reviews on G2. They open issues on GitHub. They post bounties. They ask highly specific architectural questions on StackOverflow.

To find interview targets for a developer tool, go to the GitHub repository of an open-source project in your target space. Look at the "Issues" tab. Filter by issues labeled "enhancement" or issues that have been open for more than a year with multiple comments. Read the thread. You will find developers who are blocked by a specific limitation. Their GitHub profiles usually link to their personal websites or Twitter accounts.

Email them with extreme specificity. "Hi David. I saw your comment on the open issue regarding memory leaks in the GraphQL parser. I am researching a new approach to schema validation that bypasses that parser entirely. I know you spent weeks fighting this bug last year. Would you be open to an email exchange about how you eventually patched it?"

Developers respect technical depth. If your outreach proves you understand the exact technical friction they experienced, they will respond. They will not respond to generic requests for customer discovery.

Writing cold outreach that gets answered

Cold outreach is a numbers game, but the baseline conversion rate is dictated by your pitch. The standard approach fails. A message that says "I am building a new startup and would love fifteen minutes of your time to get your feedback" will be ignored. It asks for a favor from a stranger and offers nothing in return.

A successful cold message does three things. It establishes relevance immediately. It makes a highly specific request. It lowers the friction of saying yes.

Here is a template that works. "Hi Sarah. I saw your review on G2 about the reporting limitations in Tool X. I am researching how logistics teams handle custom reporting. I am not selling anything. Would you be open to answering three quick questions via email, or jumping on a ten-minute call next Tuesday?"

Notice the structure. The first sentence proves you did the work to find them specifically. The second sentence defines the scope of the research. The third removes the fear of a sales pitch. The fourth offers an asynchronous option. By giving them the choice to answer via email, you lower the barrier to entry. Many will choose email, provide detailed answers, and then naturally agree to a follow-up call once rapport is established.

The mathematics of cold sourcing

You must treat this like a sales funnel. To get ten interviews, you need a twenty percent conversion rate on fifty highly personalized emails. If you send generic spam, your conversion rate will drop to one percent, meaning you would need to send one thousand emails. Sending one thousand personalized emails is impossible. Sending fifty is a solid afternoon of work.

Spend five minutes researching each lead. Find their exact review, their exact forum post, or their exact GitHub issue. Reference it in the first line. This five minutes of research buys you a twenty percent response rate. If you skip the research, you will get zero responses and conclude that nobody wants your product. The data will be false, corrupted by your own lazy outreach.

The compensation problem

Founders often assume they need to pay for user interviews. They offer a twenty-dollar Amazon gift card in exchange for thirty minutes on Zoom. This is a mistake.

Offering small monetary rewards attracts the wrong demographic. It attracts people who optimize their time for twenty-dollar gift cards. These are rarely the busy professionals or serious buyers you need to speak with. Furthermore, offering a small amount of money to a high-earning professional actually cheapens the interaction. A Director of Engineering makes too much money to care about a coffee gift card. Offering it frames the conversation as a cheap transaction rather than a peer-to-peer exchange of value.

Instead of money, offer proprietary data. Professional curiosity is a massive motivator. When you reach out, tell them exactly what you are doing. "I am interviewing twenty Directors of Engineering about how they manage technical debt. If you are willing to share your process with me, I will send you the aggregated, anonymized report of how the other nineteen companies are doing it."

This offer is irresistible to a professional who wants to know how they stack up against their peers. It costs you nothing but time, and it positions you as an industry insider rather than a begging founder. You become a hub of valuable information.

Leveraging automated demand signals

Manually scraping reviews and forum posts is highly effective, but it is also slow. If you want to accelerate the sourcing phase, you need tools that aggregate these signals for you. This is where Unthinkable is useful. The app surfaces business ideas by tracking demand signals across the web. Instead of manually reading hundreds of Shopify reviews to find frustrated users, you can use the platform to identify where the concentration of pain is highest, and immediately see the context of those frustrations. This lets you skip the scraping phase and move directly to the outreach phase.

The trap of the survey

Many builders try to avoid the hard work of sourcing interviews by posting a Google Form link on social media. They think a survey will give them the data they need without the awkwardness of cold calling strangers. Surveys are useless at the idea stage.

A survey forces the respondent into your pre-defined assumptions. If you ask "Would you pay ten dollars a month for a better calendar app?", you are not discovering their real problems. You are just asking them to validate your hallucination. People will click "yes" because it costs them nothing to click a button.

An interview allows for open-ended exploration. When a user tells you they hate their calendar, an interview lets you ask "What did you do last time it frustrated you?" If they say they did nothing, you know the problem is not severe enough to monetize. A survey cannot capture this nuance. You must do the manual work of finding ten humans and speaking to them directly.

Structuring the initial contact

Once you have your list of ten to twenty qualified leads, you must manage the logistics flawlessly. Do not send a Calendly link in the first message. Sending a scheduling link before they have agreed to speak is presumptuous. It forces them to do the work of finding a time on your calendar.

Instead, ask for permission first. Once they say yes, offer two specific times in their time zone. "Great, I can do Tuesday at 10 AM Eastern or Wednesday at 2 PM Eastern. Do either of those work for you?" If they say no, then you can offer the scheduling link as a fallback. "No problem, here is my calendar if it is easier to find a time that fits your schedule."

Keep the initial call strictly to the promised time limit. If you asked for ten minutes, set a timer. At the nine-minute mark, pause the conversation. Tell them you want to respect their time and that you have reached the ten-minute mark. Give them the option to leave. "We are at ten minutes. I have one more question, but I want to respect your schedule. Do you need to run?" In most cases, if the conversation is about a problem they genuinely care about, they will wave you on and continue talking. Giving them the out builds immense trust.

Moving from interviews to a panel

Your goal is not just to conduct ten isolated interviews. Your goal is to build a panel of early advisors. When an interview goes well, do not let the relationship end when you hang up.

At the end of a strong call, ask for permission to follow up. "This has been incredibly helpful. I am going to take these insights and build a wireframe over the next two weeks. Would you be open to me sending you a five-minute video walkthrough of the wireframe to see if I am heading in the right direction?"

Almost everyone will say yes. You have now converted a cold lead into an active participant in your product development cycle. When you finally launch the product, these ten people will be your first beta testers and your first paying customers. They will buy the product because they helped design it.

Finding people to interview is not magic. It is a process of finding where the pain is documented, reaching out with a specific and contextual message, and offering genuine professional value in return for their time. Stop asking your friends for feedback. Go find the people who are already leaving demand signals for your future competitors.