How to Find People Who Need Your Product: A Founder’s Guide

The people who need your product are not necessarily the people who match your demographic. They are the people experiencing the problem, feeling its consequence, and showing some reason to act. Your job is to find the evidence.

The mistake: looking for an audience instead of a problem

A founder says, “My customers are small businesses.” Another says, “My customers are marketers.” Another says, “My customers are SaaS founders.”

Those descriptions can be useful starting points, but they do not tell you who needs your product today.

A person can fit your target market and have absolutely no reason to buy.

Customer discovery gets much easier when you stop asking, “Where can I find my audience?” and start asking, “Where can I observe people experiencing the problem I solve?”

The Cusicon Need Signal

Use this simple model to decide whether someone is merely a possible customer or someone worth investigating.

The more of these you can observe, the stronger your reason to start a conversation.

Step 1: Write the problem in the customer’s language

Before you search for people, write down the problem without using your product's name.

Suppose you built a tool that helps small sales teams follow up with inbound leads. “People who need my CRM” is product language.

A better starting point is:

These phrases are valuable because people discuss problems more naturally than they discuss the category you assigned to your product.

Step 2: Find where the problem is already being discussed

Now look for places where your potential customers already talk about work, frustrations, decisions and alternatives.

• Search engines and question results
• Reddit and niche communities
• LinkedIn posts and professional discussions
• Industry forums and communities
• Product reviews and comparison discussions
• Job postings that reveal a growing operational problem
• Competitor reviews, complaints and feature requests
• Customer communities around tools your buyers already use

Do not begin by asking which platform is “best.” Start with the problem language and follow it to the places where real people use that language.

Step 3: Search for evidence, not keywords alone

Keywords are useful for finding conversations, but a keyword match does not prove need.

Compare these:

The last example contains context, a problem and an active search for a solution.

Step 4: Look for triggers

People can live with the same problem for years. A trigger changes the economics of doing nothing.

Common triggers include:

• rapid growth
• new employees
• new funding
• a new customer segment
• an operational failure
• a tool becoming too expensive or limiting
• a new regulation or requirement
• a change in leadership
• a new project or launch
• increasing volume that makes the old workaround break

A useful customer search therefore becomes:

This is much more precise than building a giant list of people who merely match your ICP.

Step 5: Study the workaround

If the problem matters, people usually do something about it, even if their current solution is ugly.

Look for:

• spreadsheets
• manual processes
• multiple disconnected tools
• hiring someone to handle the problem
• expensive incumbent software
• asking other people for recommendations
• building an internal workaround
• doing the work manually because no acceptable option exists

The workaround tells you something important: the customer has already spent effort trying to solve the problem.

Step 6: Build a small evidence list

Do not immediately build a database of 10,000 prospects. Start small enough that you can actually understand every person.

A useful first research list might contain 20–50 people or companies.

The purpose of the list is not volume. It is to find patterns.

Step 7: Talk to the person before trying to scale the channel

Once you have evidence that someone may need your product, have a human conversation.

Ask about the situation rather than immediately pitching your product:

• What are you doing today?
• When did this become a problem?
• How often does it happen?
• What happens when it goes wrong?
• What have you tried already?
• What do you dislike about the current workaround?
• Who else is involved in solving it?
• What would make you change the current approach?

You are trying to discover whether the problem you found publicly is real, important and connected to behavior.

Step 8: Separate “could use” from “needs”

This distinction will save you enormous amounts of wasted prospecting.

Not everyone will move through every stage. The model is a way to prioritize research, not a promise that a particular signal leads to a sale.

The 20-person customer discovery exercise

If you have no idea where to start, run this exercise before spending money on acquisition.

1. Write your customer's problem in plain language.
2. Write five variations of how a customer might describe that problem.
3. Search those phrases across places where your buyers gather.
4. Save 20 people or companies showing credible problem evidence.
5. Record the trigger and current workaround for each.
6. Group the evidence into patterns.
7. Talk to the strongest examples.
8. Update your ICP based on what you learn.
9. Make a specific offer to the people with the clearest need.
10. Record what happened and repeat.

This turns “I need more customers” into a research process you can execute.

What not to do

Do not buy a giant list and call it customer discovery

A contact database can give you names. It cannot tell you whether those people currently have the problem.

Do not confuse audience size with demand

A huge community can contain very few people who need your solution today.

Do not search only for your product category

Your future customer may never type the category name. They may search for the underlying problem or describe the workaround they want to escape.

Do not pitch every person who mentions the problem

Public problem discussions are opportunities to learn and help, not permission to spam. Context matters.

Do not scale before you know what you're looking for

If you cannot describe a strong prospect manually, automation will usually give you a larger pile of weak prospects.

The Cusicon Buyer Discovery Loop

The goal is not to become better at finding random prospects.

The goal is to become better at recognizing the specific circumstances in which someone is likely to need what you built.

The bigger lesson

Your customers are not hiding behind a mysterious “marketing channel.” They are living their normal lives, doing their jobs, searching for answers, complaining about broken workflows, comparing alternatives and creating workarounds.

Your job as an early-stage founder is to learn how to recognize those moments.

Find the problem first. Then find the people experiencing it. Then find the reason it matters now.