[Market] (4) A product is not 'what you want to build' — Why choosing the wrong 'weapon' leads to defeat even in a winnable market

As I wrote last time, choosing a market is not enough.

It only becomes a strategy once you break it down to SAM/SOM and decide where and how to capture it.

Click here for the previous article.

So, what do you decide next?
There is only one answer.

Decide what you will use to capture it.

This is where the product comes in.

However, many companies make a mistake here too.
They think of the product as 'what they want to build'.

I want to include this feature
I want to create this experience
I want to realize this worldview

Of course, there is nothing wrong with that in itself.
However, that alone does not guarantee victory.

This is because a product is not a work of art.

A product is a weapon for capturing the market.

No matter how beautiful it is,
no matter how much philosophy it has,
it is meaningless if you cannot win in that market.

What is important is
not whether it is a good product.

It is whether it is a product that can win
in that market,
for those customers,and in that competitive environment.

1. Even in a winnable market, you can lose because of the product

The market selection is correct.
The SOM is sharp.
The pain points are deep.

Yet, some companies still lose.
The reason is simple.

The weapon is misaligned.

What customers want is not an all-in-one solution.

It might be something that works quickly.
It might be something that can be introduced with peace of mind.
It might be something that the front line can use immediately.

It might be about being naturally embedded into existing workflows.

However, many companies overlook this.
They start with 'what can we build?'

What happens then?

It has many features.
The explanation is impressive, too.

But it doesn't resonate.

That is because what customers buy is not the features,
but the change they gain after implementation.

In other words, this is what you should really be asking about your product.

To capture this market,
have you created a reason for the customer to buy in the first place?

If you miss this, you will lose even in a winnable market.

--

2. What is a product?

Let's clarify this first.

A product is not
a collection of features you want to build.

It is a design to solve customer problems
with a higher probability than competitors,
with less friction,
and faster.

To put it another way,

Product = A mechanism for delivering value

It is not just the UI.
It is not just a list of features.
It is not just an expression of philosophy.

It solves problems, gets implemented, is continued, and spreads.

A product is the mechanism that makes this entire flow possible.

Therefore, fundamentally, a product should not be considered in isolation.

- Which market to capture
- Which customers to capture
- In what order to expand

Only when built upon this strategy does it have meaning.

A product is not an independent entity.
It is a part of the strategy.

--

3. Mistakes many companies make with products

There are three common mistakes.

1. Trying to win with features

Once competition begins, this happens immediately.

We need that feature too
We'll lose if we don't have this feature
It looks weak on a comparison chart

As a result, features increase.
However, the win rate does not improve.

Why?

Because customers do not buy comparison charts.
They buy what solves their problems with the least amount of friction.

The number of features is not the strength of the value.

2. Trying to make it sellable to everyone

Even though the initial SOM is decided,
you start wanting to expand halfway through.

It seems like it could work in this industry too
It seems like it could be used for that task too
It might appeal to both large enterprises and small-to-medium businesses

As a result, the product becomes half-baked.

If you make it for everyone to use,
it will not deeply resonate with anyone.

What is needed first is not versatility.
It is sharpness for a specific customer.

(3) Building becomes the goal

The stronger a product organization becomes, the more it falls into this trap.

Building new features,
iterating on improvements,
advancing the roadmap

At first glance, it looks like you are moving forward.

However, if that does not lead to order rates or retention rates, you are just building for the sake of building.

A product should not be evaluated by whether it is moving forward.
It should be evaluated by whether it is getting closer to winning.

--

4. What you really need to look at is 'alignment with the winning path'

What you really need to look at in a product is not its level of completion.
It is its alignment with the winning path.

So, what is alignment with the winning path?

(1) Is the initial reason for purchase clear?

Is there a reason for the customer to buy it in the first place?

- Works immediately
- Easy to understand
- Easy to compare
- Easy to implement
- Easy to get approval for

What is needed first is not to solve everything.

It is about getting the first 'Yes'.

② Is the adoption friction low?

No matter how valuable it is, if it is difficult to implement, it will not sell.

- Initial setup is heavy
- Integration with existing systems is complex
- Training costs are high
- Field operations change too much

This friction lowers the win rate more than you can imagine.

A product is not just about value,
it is also about the design of friction.

③ Is there a reason to continue?

Once adopted, will it continue to be used?

- Does it fit into daily operations?
- Are the effects visible?
- Will it be a problem if you stop using it?
- Is the usage frequency high?

Products that sell and products that remain are different.

What is truly strong is a product that has a structure for continuity.

④ Can it be a starting point for horizontal expansion?

After capturing the initial SOM, can you expand?

- To other departments of the same customer
- To adjacent tasks with the same issues
- To adjacent industries where the same track record is effective

The first product is necessary to win at a point.

However, at the same time,

it must also be the starting point for creating the next surface.

--

5. Practical framework for product design

In practice, it is best to think in the following order.

1. Work backward from the problem

First,
do not start with features.

Clarify whose problem you are solving, which problem it is, and
at what exact moment you are solving it.

'Operational efficiency' is too vague.
Break it down to something like 'Month-end aggregation takes three days'.

If this is ambiguous, the product will also be ambiguous.

2. Narrow down to one initial winning strategy

Next, ask:
What will you win with first?

Is it price?
Speed?
Accuracy?
Ease of use?
Ease of implementation?
Sense of security?

If you try to win on everything, you will lose on everything.
At first, you should narrow your winning strategy down to one.

3. Discard what is unnecessary for your winning strategy

This is important.

A product is defined more by what you do not include
than by what you do include.

Features that do not contribute to the first order,
features that do not contribute to retention,
and complexity that slows down learning—

discard these for now.

Strong products are not created by addition.
They take shape by cutting things away.

4. Design sales, implementation, and retention as a single unit

A product does not end within the screen.

How to sell it,
how to implement it,
how to ensure adoption.

You need to design with all of this in mind.

Even if the product itself is excellent, if it

fails to be communicated in sales,
stalls during implementation,
and does not lead to adoption, you cannot win.

(5) Structure it to increase learning speed

What you should seek in your first product is not perfection.
It is learning speed.

Which customers resonate,
what resonates,
where they drop off,
what the reason for retention is.

Is it structured to gather this information quickly?
This is what determines the next stage of growth.

--

6. Once the weapon is decided, the way you fight is also decided

The market is decided,
the way to capture it is decided,
and the weapon is decided.

Then, management suddenly becomes concrete.

It is decided who to sell to.
It is decided what to build first.
It is decided what to discard.
It is decided where to win and where to expand.

Conversely, if the product is ambiguous, everything becomes ambiguous.

Sales does not know what to emphasize.
Development does not know what to prioritize.
Customers do not know what they should buy.

In other words, a product is
not just a deliverable.

A product is a weapon that makes strategy executable

What matters is not building a magnificent weapon.

It is having a weapon that can win in that market.

--

Conclusion

A product is not about building what you want to build.

It is about deciding what to win with in order to capture the market.

It is not about whether it has many features.
It is not about whether it is beautiful.

In that market,
for those customers,
in that competitive environment,

will you get the first 'Yes',
will it be continued,
and will it spread?

Only then does a product have meaning.

Therefore, this is what you should ask.

Not 'What should I build?' but 'What should I win with?'

A product is not a work of art.
It is a weapon to capture the market.

Next time

[Market Series]

(1) TAM (The Illusion)

(2) Market Selection (Where to capture)

(3) SAM / SOM (How to capture it)

(4) Product (What to use to capture it) ← This time

(5) Game change (Changing the rules)

(6) Summary (What is a market?)

Next time, game change.

You have chosen a market, decided how to capture it, and armed yourself.
If you still cannot win, there is only one thing left to ask.

Can you change the rules themselves?

As long as you fight by the same rules as the incumbent, it is difficult to win against them.

Truly strong companies do not just capture a market; they change the very way the market is captured.