Chapter 3: Target Customer & Jobs-to-Be-Done

Step 2: Who Exactly Are You Building For?

"Everyone could use this" is the most dangerous sentence in startup history. If you're building for everyone, you're building for no one.

This step is about getting ruthlessly specific about who your customer is. Not demographics. Not "males 25-35." The real person—their situation, their struggles, their daily life. This is where most founders trip up—not because they don't know their product, but because they don't know their customer well enough to build something that resonates.

Think about the last product you loved. Not liked—loved. The one that felt like it was built specifically for you. That feeling isn't an accident. It happens when a founder understands your situation so deeply that every feature, every word of copy, every design choice speaks directly to your experience. That's what we're building toward here.

The uncomfortable reality is that specificity feels limiting. Your instinct says "if I narrow my target, I'll have fewer customers." The opposite is true. When you try to serve everyone, your product is mediocre for all of them. When you serve a specific person brilliantly, word spreads within that community and you grow faster than any "broad appeal" strategy ever could. Facebook started with Harvard students. Slack started with gaming companies. Shopify started with snowboard shops. Specificity isn't a constraint—it's a growth strategy.

Demographics Are Not Enough

Traditional marketing loves demographics: age, gender, income, location. That's fine for Facebook ads, but it's useless for building products. Demographics tell you who someone is on paper. They tell you nothing about what someone needs.

Why? Because two people with identical demographics can have completely different needs. Their circumstances, their ambitions, their frustrations—these are shaped by context, not by age or zip code. A 28-year-old in Austin earning $80K could be a first-generation entrepreneur launching a food truck or a mid-level project manager at a Fortune 500 company. Same demographics. Completely different product needs.

Context Is Everything

What matters is the situation your customer is in—what's happening in their life right now that makes this problem urgent. Context includes their role, their company stage, their recent experiences, and the pressures they're under. Two marketing managers might have the same title, but one just inherited a team of 5 with a mandate to double leads in Q3, while the other has been in the role for 4 years with a stable operation. These two people need fundamentally different tools.

The best personas read like character descriptions in a novel, not entries in a census database. Give your persona a name and a context:

The "Day in the Life" Exercise

One of the most powerful things you can do at this stage is map out a typical day for your persona. What do they do first thing in the morning? What tools do they open? What meetings fill their calendar? Where do they feel friction, frustration, or wasted time? This exercise forces you to think beyond the moment your product would be used and understand the entire ecosystem of your customer's workflow.

Who Are You NOT Building For?

Equally important as defining your customer is defining who you're excluding. An anti-persona is a description of the person who looks like they could be your customer but actually isn't. Maybe they don't have the budget. Maybe their problem isn't severe enough. Maybe they'd need so much customization that serving them would drain your resources.

For example, if you're building a cash flow tool for freelancers earning $75-150K, your anti-persona might be the freelancer earning $25K who tracks everything in a notebook and doesn't see the need for software, or the freelancer earning $500K who already has a bookkeeper. Both might encounter your marketing, but neither will convert well. Knowing this saves you from chasing leads that will never close and from building features for people who aren't your core customer.

What Job Are They Trying to Get Done?

Here's a mindset shift that changes everything: People don't buy products. They hire products to do a job.

This framework—Jobs to Be Done (JTBD)—was pioneered by Harvard professor Clayton Christensen, and it fundamentally reframes how you think about customer needs. Instead of asking "what features should I build?", you ask "what progress is my customer trying to make?"

A drill isn't bought for the drill. It's hired to make holes. A milkshake isn't bought for the milkshake. It's hired to make a boring commute less boring (true story—McDonald's discovered this through their research, which found that most milkshakes were sold before 8 AM to solo commuters who wanted something thick enough to last a 20-minute drive). This insight didn't come from asking customers what flavors they wanted—it came from observing when and why they bought.

The power of JTBD is that it separates the customer's underlying motivation from any specific solution. When you understand the job, you can evaluate whether your solution actually fulfills it—or whether you're building a feature that misses the point entirely. The job stays constant even as technologies and products change. People have always needed to "stay informed about industry trends"—they just used to hire newspapers, then RSS feeds, then Twitter, then newsletters, then AI summaries. The job didn't change. The solutions did.

Job Stories Beat User Stories

You may have heard of "User Stories" from agile development: "As a [user], I want [feature], so that [benefit]." The problem? They bake the solution into the story. The moment you write "I want a dashboard," you've already decided what to build. You've skipped the crucial step of understanding why the customer needs information presented that way in the first place.

Job Stories, developed by the team at Intercom, fix this by focusing on the situation that triggers the need, the motivation behind it, and the expected outcome—without prescribing a solution:

The Three Layers of Every Job

Every job your customer is trying to do has three layers. Miss any of them, and you miss what really matters. Most founders focus exclusively on the functional layer because it's the most concrete. But the emotional and social layers often drive purchasing decisions more powerfully than functionality alone. Think about why people choose Apple over cheaper alternatives, or why enterprise buyers choose Salesforce over objectively simpler CRMs. The emotional and social layers are doing heavy lifting.

How to Uncover the Real Job

Customers rarely tell you the real job directly. If you ask "what do you want?", they'll describe a solution—usually a slightly better version of what they already use. Henry Ford's (possibly apocryphal) quote applies: "If I asked people what they wanted, they would have said faster horses."

To uncover the real job, you need to look at behavior, not stated preferences. Here are three techniques:

What You Walk Away With

By the end of this step, you should have:

• A Named Persona: Not "small business owners" but "Sarah, the solo freelancer who just hit $100K revenue and is drowning in admin work she used to handle easily." A person you can picture, whose daily struggles you can articulate in their own words.
• Their Context: What situation are they in? What's changing? What's the urgency? What triggered their need now rather than six months ago?
• An Anti-Persona: Who looks like your customer but isn't—and why serving them would distract you from your core audience.
• A Job Story: "When [situation], I want to [motivation], so I can [expected outcome]." Written from the customer's perspective, without prescribing a solution.
• All Three Job Layers: What's the functional, emotional, and social job they're hiring your product to do? The emotional and social layers are often what differentiate you from competitors who can match your features.

The work you've done here isn't just an exercise—it's the foundation everything else builds on. Your problem statement, value hypothesis, lean canvas, and eventually your entire product will reference back to this persona and these jobs. If you get this wrong, everything downstream is built on a shaky foundation. If you get this right, every decision becomes clearer because you can always ask: "Would Sarah want this?"

Now that you know who you're building for and what job they need done, it's time to dig into the problem itself. How bad is it really? Is it a mild inconvenience or a genuine crisis?