Two Customer Segments. Same Product. Or Is It?

A common pattern in early-stage startups: a founder builds a product, gains some D2C traction, then spots an opportunity to sell to enterprises.

Twice the market opportunity? Perhaps.

But potentially twice the product and GTM challenges too.

Another sales channel, or another product strategy?

Take Australian success stories like Canva and Atlassian.

Both have built businesses where individuals and teams can discover, try and adopt products with little involvement from salespeople. As adoption spreads, opportunities emerge to sell larger enterprise arrangements.

This is where product-led growth (PLG) and sales-led growth (SLG) work together.

Individual adoption helps create demand. Sales turns that demand into larger commercial relationships.

It can work in reverse, too. An enterprise sales conversation stalls, a product trial helps demonstrate value, and sales has a reason to re-engage.

The two motions reinforce each other, with the product playing a central role in both.

Now consider a different scenario.

Same technology. Two different products to build?

Imagine an AI career platform serving individuals, now looking to sell workforce planning to employers.

Same technology, but different problems, buyers and product needs. Individuals want career guidance. Employers want workforce insights, reporting and integrations.

Suddenly, the roadmap has two competing sets of priorities.

And here's the question:

Does success with individual users actually validate what enterprise customers need?

Perhaps some of it. But strong individual adoption doesn't automatically prove that employers have the same problem, need the same capabilities or will pay for the proposed solution.

Nor does it necessarily help acquire enterprise customers.

Sharing technology doesn't automatically mean sharing a product proposition or a growth engine.

I understand why founders pursue these opportunities.

Startups are still discovering their best markets. You don't want to ignore a promising opportunity because it wasn't in the original pitch deck.

Sometimes the unexpected opportunity becomes the better business.

But exploring a market isn't the same as committing to building for it.

Three promising enterprise conversations don't prove a repeatable market. One customer's feature request doesn't necessarily justify a roadmap change.

Meanwhile, the team is juggling existing customer needs with an entirely new proposition.

The trouble isn't having two strategies. It's having to validate two strategies.

That's why founder-led sales and product discovery still matter. Before building for a new market, establish whether the problem is real, shared by enough customers and worth paying to solve.

So when should you pursue the second customer segment?

I wouldn't suggest waiting until your first product and GTM are perfectly optimised. Startups rarely have that luxury.

But before committing significant product and commercial resources, I'd want answers to five questions.

1. Are we solving the same problem for a different buyer, or a completely different problem?

The further apart the customer problems, the more likely you'll need different product capabilities, experiences and commercial approaches.

2. Does one customer segment genuinely help us grow the other?

Does individual adoption create enterprise demand? Do enterprise customers bring more individual users? Can the same product experience deliver value to both?

Or are we assuming that success in one market will somehow translate to the other?

3. What have we actually validated?

Customer interest? The problem? Willingness to pay? The proposed solution? A repeatable way to acquire customers?

Those are very different milestones.

One enterprise customer asking for a particular capability might be a useful discovery opportunity. It isn't necessarily a reason to put that capability on the roadmap.

4. What will we stop doing to make room for this?

Probably my favourite question, because it forces a little operational honesty.

Product capacity, founder time and organisational attention aren't free.

If we're building enterprise capabilities, which improvements to the existing product are we delaying? What happens to activation, retention and the experience of the customers we already have?

If the plan is for the existing team to simply do both, what gives?

5. What evidence would make us double down - or walk away?

Treat the second segment as an experiment before treating it as a strategy.

Pick a customer segment. Validate the problem and proposition. Test willingness to pay, ideally before committing to substantial product development.

Set a reasonable timeframe and budget. Decide what evidence justifies further investment.

And be willing to discover it's not the right opportunity. Or not the right opportunity yet.

Two customer segments can be a strength. Two sets of product assumptions can be expensive.

There's nothing inherently wrong with pursuing multiple customer segments. Sometimes it's exactly how a startup discovers its strongest market.

But when the segments have different problems, buying behaviours and product needs, you need to recognise that you're not simply adding another sales channel.

You're potentially validating another product proposition, another commercial model and another way of building a business.

That's a perfectly legitimate bet.

Just make sure you know you're making it.