(or: why most commercial pipelines in engineering companies break early)
I keep seeing the same pattern.
A company has built a solid product:
Then I ask:
“What market are you targeting?”
And the answer is:
“Industry.”
“Companies that need heat.”
“District heating.”
Now let's pause for a second. 'Cause hthis is the part where I need to repeat myself again and again:
That’s not a market.
That’s a universe.
And once you start from a universe, everything downstream gets messy.
A few months later, it usually looks like this:
And internally, you hear:
“It depends…”
“Every project is different…”
That’s often true technically.
But commercially, it’s usually a sign that the market was never defined properly.
In engineering, you would never design a system without knowing:
You wouldn’t even start.
But commercially, many companies do exactly that.
They go to market first… and define the conditions later, inside the sales process.
That’s expensive.
Let’s make it simple. Let's see what it isn't.
A market is not:
“who could use this”
A market is:
the set of conditions where your solution works — and will be bought
Two parts:
If one of those is missing, it’s not a market.
I once had a dialogue with a CEO of a company selling heat solutions.
They said:
“We target food & beverage.”
Sounds reasonable.
But when we looked at their actual projects, a pattern showed up:
Everything else?
Early conversations. No decisions.
So “food & beverage” wasn’t the market.
(think like an engineer and define the operating window)
Instead of starting with industries, start with conditions.
Here’s a checklist I use in practice.
If this doesn’t fit, nothing else matters.
Ask:
If a site doesn’t have grid capacity → stop.
No amount of marketing will fix that.
No source? No project.
Already here, you’ve removed a big part of the “market”.
Good. That’s the point.
Now translate that into real operations.
Ask:
Not:
“food industry”
But:
“continuous steam-based processes like pasteurization or drying”
Now it becomes concrete.
Your solution never stands alone.
Ask:
I’ve seen it work best as:
Same product. Different markets.
Not who uses it. Who feels the pain.
Ask:
Usually:
If you can’t point to a clear owner, expect slow movement.
This is the one most teams underestimate. Even if everything fits, nothing happens without a trigger.
Typical ones I keep seeing:
No trigger?
Then it’s a “nice idea”. Not a project.
“Companies looking to decarbonize”
Steam-based production sites
with stable demand
existing boiler setup
access to electrical capacity
and a boiler approaching replacement
Now we’re talking.
That’s something you can actually build a pipeline around.
This is where things start to feel different internally.
Instead of broad messages, you can say:
“If your boiler is reaching end of life and you have grid capacity, this is worth a look.”
That lands.
Because it reflects a real situation.
You get faster conversations like:
“This fits, let’s move forward”
or
“This won’t work, let’s not spend time on it”
Both are valuable.
When projects come from similar conditions:
You already think in systems when you build your product. The shift is to do the same commercially.
Not more campaigns. Not a new CRM.
But starting with:
Ask your team:
“Can we describe our market like a system specification?”
If the answer is vague, you don’t have a defined market yet.
If one is missing, expect friction later.
I’ve yet to see a company struggle with growth because they didn’t run enough campaigns.
I’ve seen many struggle because they started from a universe instead of a defined system.
Define the system first.
Then build everything else on top.