How to Figure Out Who Your SaaS Is Actually Built For

You built the product. People are signing up. But something feels off.

Some users are asking for features that do not fit your roadmap. Others sign up and never come back. A few actually get it and stick around. The problem is you cannot tell which group matters most or where to focus next.

This is one of the most common places early-stage SaaS founders get stuck. Not because the product is bad. But because the customer was never clearly defined.

Why "Everyone Who Needs This" Is Not a Target Customer

It feels logical to say your product is for anyone who has the problem it solves. But marketing does not work that way.

When you write for everyone, you connect with no one. Your copy becomes vague. Your onboarding tries to serve too many use cases. Your messaging ends up bland because you are trying not to exclude anyone.

The founders who grow fastest are usually the ones who got uncomfortably specific about who they are building for. Not because they want to turn people away, but because specificity is what makes your message land.

A product for "marketers" is forgettable. A product for "solo founders running paid ads without a marketing team" is something a very specific person reads and thinks: that is me.

What Mixed Signups Are Actually Telling You

If you have a mix of different types of users signing up, that is not a bad thing. It is data.

Most early-stage founders look at this and feel confused. What they should do instead is treat it like a research problem.

Look at who signed up and ask: which of these people actually activated? Which ones hit the core value of your product within the first week? Which ones reached out with questions that made sense? And which ones churned without ever doing the one thing the product is designed for?

The answers usually point to a pattern. One or two types of users tend to behave completely differently from the rest.

That gap is your ICP hiding in plain sight.

The Difference Between a User, a Buyer, and Your Actual ICP

These three things are not the same and mixing them up causes a lot of wasted effort.

A user is anyone who interacts with your product. A buyer is the person who hands over money. Your ICP is the specific type of person who gets real value from your product, has a clear reason to pay for it, and is likely to tell others about it.

In early-stage SaaS, these three things are often different people. A technical tool might be used by a developer but bought by a team lead. A marketing tool might be signed up for by a founder but only stick if their team uses it too.

When you are doing ICP work, focus on who gets the most value and who makes the buying decision. Those two things should be close to the same person if your positioning is going to work.

Five Questions That Help You Narrow Down Who to Focus On First

Go through your current signups or early users and ask these questions for each type of person you see:

What job or role does this person have? What was the specific problem they came with before finding your product? Did they activate and reach the core value within the first week? Did they churn, and if so, at which point? Would they be genuinely upset if your product stopped existing tomorrow?

The users who score well across all five are your starting point. You do not need a big list. Even two or three people who clearly get your product and keep using it tells you more about your ICP than a hundred signups who disappear.

How to Look at Your Current Signups and Find the Pattern

Pull a list of everyone who has signed up. Even if it is small. Now sort them by behavior, not by what they told you when they signed up.

Who logged in more than three times? Who completed the core workflow? Who reached out to you with a specific and relevant question? Who referred someone else?

These are your signal users. Now look at what they have in common. Job title, company size, the problem they came with, the channel they found you through. You are looking for something that shows up two or three times across different people.

That commonality is your ICP hypothesis. It is not final. But it is something you can test.

Once You Have a Hypothesis, Test It Before You Commit

A lot of founders define an ICP and then immediately start building campaigns around it. That is moving too fast.

Before you commit to an ICP, test it. Write one piece of content directly for that person and see if it resonates. Reach out to three or four people who fit the profile and have a short conversation. Change one line of your homepage copy to speak directly to them and see if signups improve.

You are looking for early confirmation that this is the right person before you build your whole positioning around them.

If the signal is strong, you have found your customer. If it is quiet, go back to your signup list and look again.

What to Do When Your ICP Hypothesis Is Wrong

This happens. And it is fine.

The point of doing this work early is to find out before you spend money on ads or commit six months of content to the wrong person. A wrong hypothesis is useful. It eliminates a segment and points you somewhere else.

If your hypothesis does not hold, do not panic. Go back to your activated users, look harder at who is staying, and ask why. The answer is usually there. You just need to look with fresh eyes.

Some founders use structured research frameworks and tools like Infinall.ai to organize customer research, map ICP patterns, and build positioning before launching any campaigns. That kind of structure is worth building early, even if it feels like overkill at the start.

The Real Cost of Skipping This Step

It is not that your product will fail. It is that everything becomes harder.

Your content will not convert because it is speaking to the wrong person. Your cold outreach will not get replies for the same reason. Your ads will get clicks but no signups. And every new feature you build will be pulled in three directions by three different types of users who all want something different.

Getting your ICP right is not a marketing task. It is the foundation every other decision sits on. And the earlier you do it, the cheaper every mistake gets.

FAQ

How do I define my ICP if I have no customers yet?
Start with your best hypothesis based on who you built the product for and why. Then do a small number of customer interviews with people who fit that description. Use those conversations to either confirm the direction or adjust it. You do not need paying customers to start ICP work.

What is the difference between ICP and target audience for SaaS?
Target audience is broad. It describes a general group of people who might be interested in what you do. ICP is specific. It describes the exact type of customer who gets the most value from your product, has a clear reason to buy, and is likely to stay. For early-stage SaaS, ICP is what actually matters.

How many customer segments should an early-stage SaaS focus on?
One. Maybe two if there is strong evidence for both. Spreading your positioning across three or more segments early on almost always leads to weak messaging and confused product direction. Go narrow first. You can expand later when you have the revenue to support it.

What happens if I pick the wrong ICP?
You waste time and money marketing to people who will not pay or stay. The good news is that an early wrong ICP is fixable. The danger is committing to it for too long. Test before you build your whole strategy around one assumption.

How do I know when my ICP definition is specific enough?
When you can read it out loud and it immediately makes you think of a real person. If it still sounds like a job category or a vague demographic, it is not specific enough. A good ICP definition includes role, company stage, the specific problem they have, and what they have already tried before finding you.