A Company is not a person: A Founder's Guide to Customer Roles

You have an idea that you’ve mapped out some of your customer segments. Maybe you even connected to someone in a company in one of your customer segments through LinkedIn. That person may have even said, “that’s a real problem you are working on.” And now you feel validated and so you continue building.

Here’s the uncomfortable truth: you may have talked to completely the wrong person. Not because they were dishonest, but because in most businesses, the person who feels the problem most acutely is rarely the person who decides whether to buy your solution, and is almost never the person who pays for it. Understanding this distinction isn’t a small nuance. It is the difference between building something that gets purchased and building something that gets admired but never bought.

This is what customer discovery is really about and it starts with getting clear on two foundational concepts: customer segments and customer roles.

Segments Tell You Where to Look. Roles Tell You Who to Talk To.

Think of it this way: a customer segment defines who you are targeting as a group, while a customer role defines what function or job a specific person plays within that group. They work together, but they are not the same thing. Confusing them is one of the most common early mistakes founders make.

A customer segment is a distinct group of people or organizations that share similar characteristics and common needs. Segments exist at a group level. They scope which market or population your discovery efforts should focus on. In B2B contexts, segments are typically defined using two types of traits:

• Firmographic traits — industry, company size, revenue, geography
• Technographic traits — what technology they use, their adoption behavior, their current tech stack

(this is the most basic level of segmentation by the way)

The key test for whether a group deserves its own segment: do they have materially different needs, and could each independently drive your business outcome? If yes, treat them as distinct segments and run separate discovery for each. Mixing segments in early interviews is one of the fastest ways to generate useless, contradictory data.

A customer role (sometimes called a buyer persona, user, or stakeholder role) represents the individual within a segment. In B2B, a single deal almost always involves multiple roles, each with distinct goals and pain points:

• Economic Buyer — approves the budget; cares about ROI, risk, and cost justification
• Decision Maker — gives the final yes or no on adoption; may or may not control the budget
• Technical Buyer / Evaluator — assesses product fit and integration; cares about specs, security, and compatibility
• End User — interacts with your product daily; cares about usability, workflow, and time savings
• Champion — advocates for your product internally; cares about making their team look good
• Influencer — can sway the decision without making it directly; often a respected peer or KOL
• Saboteur — a person who stands to lose something if your solution is adopted, and will quietly work against it

These roles may all live within the same customer segment — say, “independent pharmacy chains with 5–20 locations.” They need to be interviewed and understood separately. The champion who invited you in sees your product completely differently than the CFO who has to approve the purchase order.

How Segments and Roles Work Together in Discovery

The relationship between segments and roles is hierarchical: the segment tells you where to look and the role tells you who to talk to and what to ask. A segment without role clarity leads to generic interviews that conflate misaligned pain points. Role clarity without segment clarity leads to talking to the right type of person at the wrong type of company.

In practice, a structured discovery process moves through four steps:

• Define the segment first — be specific. “Outpatient orthopedic surgery centers with 3–10 operating rooms in the southeastern US” is a segment. “Hospitals” is not.
• Map the roles within that segment — who is the end user, the decision maker, the economic buyer, the champion, and the saboteur?
• Recruit interview subjects by role — so you can triangulate the full buying and usage dynamic, not just one perspective
• Synthesize by role, then across the segment — identify where role-specific needs overlap or conflict, and where blockers live

This structure prevents the most common trap in early discovery: interviewing only the champion — the enthusiastic person who invited you in — while completely missing the technical evaluator or end user whose friction will kill adoption after the sale closes.

The Customer Roles Discovery Template

Use this table as a template to map your segment and roles before your first interview. Fill it in with your best current hypotheses, then let your conversations challenge and refine it.

(I recommend to translate this template into an interview tracking spreadsheet)

The Edge Computing Example: The Saboteur Nobody Planned For

Now consider a hardware startup building on-premise computer vision for contract electronics manufacturers that assemble components for medical device and aerospace OEMs. Quality defects are costly, rework rates are high, and OEM audits are getting stricter.

Role mapping reveals a layered picture:

• End User — the quality technician on the floor who runs manual visual inspections and knows exactly which defect types get missed
• Decision Maker — the plant GM or VP of Operations who needs a concrete ROI case before approving any capital expenditure
• Economic Buyer — the CFO or finance lead who sets the capex budget and wants a clear payback period
• Saboteur — the QC supervisors whose teams run manual inspection today

That last one catches founders off guard every time. Nobody is formally eliminating jobs. But the fear of that outcome is enough for a supervisor to slow-roll adoption, question the system’s reliability data, or quietly frame it as a compliance risk to leadership. If you haven’t surfaced this dynamic in discovery, you’ll encounter it in your sales cycle — and by then, it costs you far more to address.

Why Your Beachhead Segment Is Everything

Here is the counterintuitive lesson that trips up nearly every first-time founder: trying to serve multiple segments simultaneously doesn’t accelerate your learning, it destroys it.

When you pick a beachhead, you’re not saying you’ll only ever serve that segment. You’re saying: this is the group whose pain is acute enough, whose buying process is accessible enough, and whose needs are similar enough that I can actually learn something actionable right now. Then, within that beachhead, you still map the roles. Even in a narrow segment, the person who feels the problem is rarely the person who buys the solution.

Five Things You Can Do This Week

Start here before you execute another interview.

1. Write your segment in one specific sentence. Force yourself past vague categories. “Mid-market SaaS companies” is not a segment. “Series A SaaS companies with 50–200 employees using Salesforce as their CRM” is getting there.

2. Draw a role map for that segment. Using the definitions above, write down your best hypothesis for who fills each role — end user, decision maker, economic buyer, champion, influencer, and saboteur. You won’t have all the answers. That’s fine. The point is to make your assumptions visible.

3. Fill out the Customer Roles Discovery Template above with your current hypotheses. Treat every cell as a question to be answered, not a fact you already know.

4. Recruit your first three interviews by role. Don’t just talk to “someone in the industry.” Intentionally target one end user, one decision maker, and one person who might be a saboteur. The contrast in their perspectives will teach you more than ten interviews with the same role.

5. Before each interview, write down your riskiest assumption. The most valuable thing discovery can do is kill your assumptions early and cheaply — before you’ve built something expensive on top of them.

The best founders don’t guess who their customer is. They build a map, go test it, and let reality refine it. Start this week.