High Expectation Customers (HECs) are the users who define your product-market fit. They're the most demanding users in your base — and if you build for them, everyone else benefits. If you ignore them and build for the average user, you'll end up with a product nobody loves deeply.

Rahul Vohra, CEO of Superhuman, coined this concept and used it to drive Superhuman from 33% to 58% PMF in one year.

What Is a High Expectation Customer?

A High Expectation Customer (HEC) is the most demanding user in your product — the person who has a real, urgent problem, high standards for how it should be solved, and will leave if you don't deliver. HECs define your PMF because they're the users who say "very disappointed" on the Sean Ellis survey. Build for them, and everyone else benefits.

Specifically, a High Expectation Customer is someone who:

Has a real, urgent problem that your product solves
Has high standards for how that problem should be solved
Will be disappointed if your product doesn't meet those standards
Gives specific, actionable feedback — both positive and critical

They're not just power users. They're the users who push you to be better because they know what "better" looks like. Understanding HECs is essential for knowing whether you have product-market fit. They've tried alternatives. They have opinions. They'll tell you exactly what's wrong — and they'll also become your strongest advocates if you deliver.

HEC vs. Low-Expectation User

Characteristic	High Expectation Customer	Low-Expectation User
Problem intensity	High — this problem matters to them daily	Low — nice to solve, not urgent
Standards	High — compares you to the best in any category	Low — "good enough" is fine
Feedback quality	Specific, detailed, actionable	Vague ("it's fine"), minimal
Churn risk if underserved	High — they'll leave for something better	Low initially — but they'll drift away quietly
Growth potential	High — they refer, advocate, expand	Limited — passive users
Response to "very disappointed" question	"Very disappointed"	"Not disappointed" or "somewhat"

Why HECs Matter for Product Growth

Here's the counter-intuitive truth: optimizing for your average user is dangerous.

The Problem with Building for Low-Expectation Users

If you optimize for low-expectation users, you'll:

Dilute your product — adding simple features that don't push the product forward
Miss growth opportunities — HECs drive word-of-mouth; low-expectation users don't talk about you
Create weak PMF signal — "somewhat disappointed" doesn't create the retention and referral flywheel you need
Face silent churn — low-expectation users don't complain before leaving. They just drift away

Low-expectation users are easy to please but don't generate the compounding growth that builds a business.

The Power of HECs

High-expectation users create a virtuous cycle:

They drive iteration — their feedback is specific enough to act on immediately
They create word-of-mouth — when an HEC loves you, they tell everyone in their network
They validate PMF — if HECs say "very disappointed," you've built something genuinely valuable
They pay premium prices — they value quality and will pay for it without extended negotiations
They expand usage — they find new use cases, upgrade plans, and bring their team

HECs are your PMF. Build for them, and the growth engine starts itself.

How to Identify HECs in Your User Base

Look at Behavior Patterns

HECs typically:

Use your product frequently and deeply (not just daily logins — deep feature usage)
Complete onboarding fully and quickly
Use multiple features in combination
Engage with your content (blog, newsletter, changelog, community)
Respond to surveys with detailed, specific feedback
Contact support with specific feature requests (not just bug reports)

Ask the Right Question

In your PMF survey, add this follow-up:

"What type of people do you think would most benefit from [product]?"

HECs give specific, insightful answers:

"Product managers at early-stage SaaS companies who need to validate before scaling"
"Solo founders who can't afford to hire a research team but need PMF data"

Low-expectation users give vague answers:

"Anyone who wants to improve their product"
"Startups"

The specificity of the answer tells you who understands your product deeply enough to be an HEC.

Segment Your PMF Data

Run the Sean Ellis survey, then look at your "very disappointed" respondents as a group:

What do they have in common? (Role, company size, use case, acquisition source)
How does their usage pattern differ from "somewhat disappointed" users?
What features do they use that others don't?

Your HEC profile emerges from this analysis. It's not a persona you invent — it's a pattern you discover in your data.

Serving HECs vs. Low-Expectation Users

This is where most founders get it wrong. You can't build for everyone equally — and you shouldn't try.

Prioritize HECs in Your Roadmap

Build for them first — their needs define your product direction
Accept lower scores from other segments — that's the tradeoff, and it's the right one
Don't dilute for breadth — adding features for low-expectation users weakens your product for HECs
Delight consistently — exceed HEC expectations, and they become your sales team

The Vohra Prioritization Framework

Rahul Vohra split Superhuman's roadmap:

50% on strengthening what "very disappointed" users already love
50% on removing the specific blockers that keep "somewhat disappointed" users from crossing over

This balance ensures you're deepening your core value while systematically expanding your audience. Not chasing every feature request — just the ones that move the PMF needle.

Using HEC Data to Prioritize Features

1. Separate Feedback by PMF Segment

Don't mix all feedback together. Create three buckets:

"Very disappointed" feedback — what to protect and double down on
"Somewhat disappointed" feedback — what to build next (specific blockers)
"Not disappointed" feedback — largely ignore for now

2. Find the Blocker Patterns

Look at "somewhat disappointed" feedback for patterns. Usually 2-3 themes emerge that represent the gap between "I see value" and "I can't live without this."

Those themes are your highest-leverage product investments.

3. Validate Before Building

Before committing to a major feature, validate that it would actually move users from "somewhat" to "very disappointed." User interviews with 5-10 "somewhat disappointed" users can confirm whether the blocker is real and whether your proposed solution would actually resolve it.

The Superhuman Example

Superhuman's PMF journey is the canonical case study for the HEC approach:

Started at 33% PMF — below the 40% threshold
Identified HECs — users who valued speed and keyboard shortcuts above all else
Built exclusively for them — instant loading, keyboard-first design, minimal UI
Accepted that others wouldn't love it — if you don't value email speed, Superhuman isn't for you
Reached 58% PMF in 4 quarters — 33% → 47% → 56% → 58%

The key insight: Superhuman didn't try to make everyone happy. They found their HECs, built specifically for them, and let the growth compound from there. The users who didn't fit the HEC profile either self-selected out or became satisfied by the spillover quality.

The Bottom Line

Your product-market fit is defined by your most demanding users — the ones who would be "very disappointed" if your product disappeared. Find them, study them, and build specifically for them.

Low-expectation users will never be your growth engine. They're fine to have, but they're not where you invest your limited resources.

Identify your HECs. Serve them obsessively. Improve your PMF score by building for them. Let everyone else benefit from the quality you build for your most demanding users.

FitSignal segments your PMF data automatically — so you can identify your High Expectation Customers and build specifically for them. Start free at fitsignal.com.