Who is your customer? The first question, answered properly

Ask any first-time founder who their customer is and the answer is almost always some version of everyone who has this problem. It feels generous. It is actually a problem. A product built for everyone is built for nobody specifically, and nobody specifically is the only kind of customer who buys things. This lesson is about how to replace “everyone” with a real person, in plain language, by the end of an afternoon.

You do not need a research budget for this. You need a willingness to make a call and live with it being wrong for a while. The point is not to find the perfect customer on the first try. The point is to be specific enough that the next thing you do (writing a homepage, picking a channel, designing the onboarding) actually has a target.

// 01Why “everyone” is the wrong answer

Saying your product is for everyone sounds inclusive. In practice it does three damaging things at once.

• It produces vague copy: Words written for everyone read like they were written for nobody. The homepage ends up promising "save time, work smarter, scale faster," which a hundred other tools also promise.
• It hides the wrong channel choices: Every channel has a different audience. If you do not know which audience you are after, you cannot pick a channel; you end up trying all of them shallowly and learning nothing from any of them.
• It blocks word of mouth: Recommendations happen when one specific person realizes a specific friend has the same specific problem. "It is for everyone" is not a sentence anyone repeats.

// 02The two questions that define a customer

At the basics level, you can describe a customer with two questions:

• Who are they?: In the most concrete language you can use. A role, a context, a moment in their life or work. Not "small businesses." A bookkeeper at a 4-person law firm using QuickBooks Online.
• What are they trying to get done?: In their words, not yours. Not "automate financial reporting." Close the books faster on the last day of the month so I can leave at a normal hour.

Notice what is missing: the words “everyone,” “people,” and any version of “anyone who needs.” If your sentence works without those, you are being specific. If it does not, you are being vague.

// 03ICP: ideal customer profile, in plain language

You will hear the term ICP, ideal customer profile. It sounds like something a consultant would charge to write. The basics version takes ten minutes:

• Role: What does this person do for a living, or what is their position relative to the problem? "Founder", "marketing manager at a 30-person company", "freelance designer who just got their first client".
• Context: What is true about their situation that makes the problem real? "Has been freelancing for under a year and has not been paid by a client yet." Context is where the problem lives.
• Pain: What is the friction you are removing? Stated as something they would say at the end of a long day, not as a feature.
• Alternative: What are they doing now to handle this? A spreadsheet, a competitor, an assistant, nothing. Knowing the alternative tells you what you have to be better than.
• Trigger: What had to happen recently for them to start looking? "Their last client paid 60 days late." A trigger is the reason today is the day they care.

// 04Jobs to be done: what they hire your product for

Another piece of language you will hear is jobs to be done (often shortened to JTBD). The idea is simple: people do not buy products, they hire them to do a specific job. A drill is hired to make a hole in a wall. The customer does not want a drill. They want a shelf they can hang.

For a product to feel necessary, you need to know the job in the customer’s words, not in the language of features. Three useful questions:

• When do they hire your product?: A moment, not a personality. "When a freelancer realizes a client is 30 days late and they need to send a polite reminder without sounding desperate."
• What do they fire to make room for it?: There is always something they were doing instead. A spreadsheet, a sticky note, a reluctant phone call. If nothing gets fired, the job was not real.
• What does success look like?: In the customer's life, not in your dashboard. "I do not have to think about this for another month."

JTBD is not in opposition to ICP. The ICP is who. The job is what they want done. You need both. The ICP tells you who to talk to. The job tells you what to say once you do.

// 05The exercise: write it down

Put down a sheet of paper and answer the following, in plain sentences. Do not write a deck. Do not use bullet points. Write paragraphs that sound like you are explaining your customer to a smart friend at a dinner.

• One paragraph: who they are: Role, context, the situation that makes the problem real. Resist generality.
• One paragraph: what they are trying to get done: In their words, including the small frustrations.
• One paragraph: what they are doing about it now: Their current alternative, even if it is "they put up with it."
• One sentence: the trigger: The thing that made today different from yesterday.

// 06Five things to carry forward

• 01: “Everyone” is not a customer. It is the absence of one. Picking a customer is the first decision that lets every later decision happen.
• 02: Two questions define a customer: who are they, and what are they trying to get done. In concrete words, not categories.
• 03: ICP is the role, context, pain, alternative, and trigger. Five fields, one paragraph, ten minutes.
• 04: Jobs to be done is the job your product is hired for. The customer is hiring your product instead of an alternative; know what they are firing.
• 05: If you cannot name three real people who fit your description, the description is not specific enough yet.

Now you have a person and a job. The next question: how does this kind of company grow? Some grow by selling, some by marketing, some through the product itself, some through community. Picking the right approach for your customer is the next lesson.