One of the first things I noticed while working on B2B products was how quickly we defaulted to company size when talking about customers.

Enterprise.

Mid-market.

SMB.

It was easy to understand and even easier to put into a spreadsheet.

But over time, I realized something important.

Two companies with 5,000 employees could use the same product in completely different ways. And two smaller companies could have almost identical workflows, even if they looked completely different on paper.

That’s when use-case segmentation started making much more sense to me.

Instead of asking who the customer is, ask what they’re trying to accomplish with your product.

What Is Use-Case Segmentation?

Use-case segmentation groups customers based on the specific problem they’re solving or the way they’re using your product.

For example, an assessment platform might have customers using it for:

• Pre-employment screening
• Leadership assessment
• Internal mobility
• Development and coaching
• Post-hire evaluation

These customers may use many of the same features.

But their goals, workflows, success criteria, and expectations can be completely different.

That difference matters.

Company Size Doesn’t Tell the Whole Story

Firmographics are useful.

Company size, industry, geography, and revenue can help sales and marketing teams understand the market.

But they don’t always tell Product Managers what needs to be built.

Imagine two enterprise customers.

Customer A uses your platform to assess thousands of candidates every month.

Customer B uses it to assess a small group of senior leaders twice a year.

Both are enterprise customers.

But their product requirements are likely very different.

Customer A might care about automation, bulk operations, integrations, and speed.

Customer B might care more about customization, reporting, and assessment depth.

Same segment by company size.

Completely different product needs.

Use Cases Reveal the Real Job

One of the biggest benefits of use-case segmentation is that it gets closer to the customer’s actual job.

Instead of asking:

“What type of company are they?”

You can ask:

“What are they trying to accomplish?”

That question changes the product conversation.

A customer isn’t simply an “enterprise account.”

They’re trying to reduce hiring time.

Or improve leadership development.

Or automate a manual workflow.

Or make better decisions.

Once you understand the job, product opportunities become much easier to identify.

The Same Feature Can Have Different Value

Another reason I like use-case segmentation is that it changes how we think about feature value.

Take reporting.

For one customer, reporting might be about compliance.

For another, it’s about helping managers make decisions.

For someone else, it’s simply about tracking operational performance.

The feature is identical.

The value isn’t.

This is why feature requests can sometimes be misleading.

Two customers may request the same feature for completely different reasons.

Understanding the use case helps you determine whether you’re solving the same problem or simply building the same functionality.

Use Cases Help With Prioritization

This becomes particularly useful when the roadmap is crowded.

Suppose three customers request an integration.

Instead of simply counting the requests, look at the use cases behind them.

Are all three customers solving the same problem?

Is this use case growing?

How many other customers have the same need?

Does solving it unlock a larger segment?

Suddenly, prioritization becomes more strategic.

You’re no longer asking:

“How many customers requested this?”

You’re asking:

“How important is this problem across the customers who share this use case?”

Use-Case Segments Can Change Over Time

Customers aren’t locked into one use case forever.

A company might start using your product for recruitment and later expand into employee development.

That transition can be a powerful product signal.

It tells you that your product has created enough value in one area for the customer to trust it with another.

Tracking these changes can reveal expansion opportunities that traditional segmentation would miss.

Don’t Create Too Many Segments

There is one trap to avoid.

Once you start looking at use cases, you can easily create dozens of segments.

That doesn’t help anyone.

A useful segment should influence a decision.

If two customers have different use cases but require exactly the same product experience, separating them may not provide much value.

The best segments are actionable.

They change what you build, how you onboard, how you communicate, or how you measure success.

Combine Use Case With Behaviour

The most interesting insights often appear when use case and behaviour are combined.

For example:

Use case: Pre-employment screening
Behaviour: High-frequency usage

versus:

Use case: Leadership development
Behaviour: Low-frequency usage

Both customers might be successful.

But success needs to be measured differently.

This prevents Product Managers from applying the same engagement expectations to fundamentally different customer workflows.

Final Thought

I’ve learned that B2B customers are rarely defined well by a single label.

Company size tells you something.

Industry tells you something.

Revenue tells you something.

But use case often tells you what matters most to the product team.

When you understand why customers are using your product, you can design better experiences, prioritize more intelligently, and identify opportunities that traditional segmentation can easily miss.

Because the most useful question isn’t always:

“Who is our customer?”

Sometimes it’s:

“What are they trying to accomplish with us?”