1.5 Defining Your First Customer

“Small business owners” is not a customer. “B2B SaaS companies” is not a customer. These are ghost categories, collections of millions of people with different problems, different budgets, and different reasons to care about what you’re building. You cannot write for a ghost. You cannot sell to a ghost. You cannot build for a ghost.

The reason founders hide behind vague categories is fear. If you say your customer is “marketing teams,” you can’t be wrong. If you say your customer is “a content manager at a 10-person e-commerce brand who spends 3 hours a week repurposing podcast episodes into social posts,” you can be wrong, and that specificity terrifies people. But that specificity is the only thing that makes selling possible.

Vikash built Bulk Mockup to $12,000 MRR by starting with one human: a print-on-demand store owner who needed 1,800 mockups created. Not “e-commerce sellers.” Not “creative entrepreneurs.” One person with one specific, painful, time-consuming problem. Vikash’s content strategy reflects that same discipline. He says he creates content for one specific problem for one specific customer. That content doesn’t get millions of views. It gets customers every day.

There’s a difference between a persona and a real person. A persona is a fiction you write in a conference room. “Meet Sarah, 34, Marketing Manager, values work-life balance.” Sarah doesn’t exist. She can’t tell you why she won’t pay for your product. She can’t tell you what words she uses to search for a solution. A real person has a name, a job title, a company you can look up, and a specific frustration you can describe in their exact words. Build for the real person first.

Nick built BlockToPin to $16,000 MRR with 400 active subscribers by centering his entire product around one specific person’s pain. His framing is simple and worth stealing: your app should be the best one for one specific person. Not the best for everyone, not competitive across the board, the best for one specific person. That constraint forces clarity. It forces you to say no to feature requests that don’t serve that person. It forces your marketing to get precise.

Here’s the format that cuts through the noise. Your ICP in one sentence: [specific role] at [specific company type] who [specific pain]. Thomas built Packager to $60,000 MRR serving IT administrators at small to medium-sized businesses who were spending an hour per application on Microsoft Intune packaging. That’s a sentence. It’s also a product, a market, and a sales pitch compressed into 20 words.

If you can’t write that sentence right now, you don’t have a customer yet. You have a hypothesis. That’s fine, but be honest about it.

The test is whether you can name a single human being who fits that description. Not a type. A person. Their LinkedIn profile should exist. Their company should be real. You should be able to write an email to them tonight that references their specific situation in the subject line.

Write that email. Don’t send it yet if you’re not ready, but write it. If you can’t write it without it sounding generic, your ICP isn’t specific enough. Tighten it until the email would make that one person think you’ve been watching them work.