NOTE 002

How to Enter a New Market in Physical Technology

How to Enter a New Market in Physical Technology

A field-tested method for learning unfamiliar systems, earning credibility, and deciding where to spend the work required to expand.

THE OPERATING METHOD

The work does not compound away. You get better at knowing where to apply it.

SWIPE TO EXPLORE →

SWIPE TO EXPLORE →

The operating method: 01 Understand the system, 02 Earn credibility, 03 Test the path, 04 Carry forward.
The operating method: 01 Understand the system, 02 Earn credibility, 03 Test the path, 04 Carry forward.

02 / ANALYSIS

A company can know its customer and still struggle to enter the next market.

The product may travel. A lot of what surrounds the product does not.

I learned this while working on market expansion in advanced nuclear. After doing the work in one market, the next one was easier to investigate. We had a better sense of who to look for, where useful public information lived, which questions exposed real issues and what weak signals looked like.

But we still had to learn the local system. A constraint that barely mattered in one market could shape the entire conversation in another. The relevant institutions changed. So did the history, politics, relationships and proof people needed before taking a new company seriously.

This is common in physical technology. A company can have a working product, a clear customer and real traction, then become an outsider again when it moves into a new geography, industry or customer environment.

The first market does not give you the answers to the second. It should make you better at finding them.

01 / UNDERSTAND THE SYSTEM

01 / UNDERSTAND THE SYSTEM

Start with what has to be true for a deployment to happen here.

Who buys? Who operates? Who can stop the project? Which regulators, integrators, suppliers, infrastructure owners or local institutions matter? What physical constraints are different? What has already been tried? Where does authority actually sit?

Research gets you to a first pass. Public filings, planning documents, regulations, meeting minutes, network data and previous company learning can now be pulled together quickly. AI helps with the grunt work.

Then go test it.

A few good conversations can show that the person you assumed was the buyer does not own the decision, that the same name keeps coming up for a reason, or that what looked like a product issue is really an installation, permitting or infrastructure problem.

You do not need to understand the whole industry. You need to find the things that could change the decision to enter.

This is what should improve with each expansion. You get faster at finding the right people, locating useful evidence, asking questions that expose problems and recognizing when a market is weaker than it looked from the outside.

The local facts still have to be learned.

A company can have a repeatable customer and still face a different path to deployment in every market.

02 / EARN CREDIBILITY

02 / EARN CREDIBILITY

At some point, people in the new market have to take a chance on you.

That can mean a customer agreeing to a pilot, a partner making an introduction, a regulator spending time with the team, an integrator putting its name next to yours or an industry veteran telling someone else that you are worth taking seriously.

There is usually some cost to being wrong. In conservative industries, the safe choice is often the known company, even when the new company might be better.

So ask a more useful question than “How do we meet the right people?”

Why would this person take a chance on us, and what would make that easier?

The answer changes by person and institution.

A customer may care about economics and proof that the product works. A partner may care about the team. An operator may care about how the product behaves in the field. Someone putting their reputation behind an introduction may care about who else is already involved.

Do not look for one credibility story. Build several real reasons to believe.

SWIPE TO EXPLORE →

SWIPE TO EXPLORE →

The same applies to introductions. Some simply get you a meeting. Some come with a light endorsement. The rare ones carry a specific judgment: this team understands the problem, or these people can execute.

That borrowed trust helps, but you still have to earn your own.

This is also why hiring an industry veteran is useful but not a complete market-entry strategy. Their judgment may travel across markets. Their relationships often do not.

Hire the insider when technical judgment, reputation or local relationships are critical. But if the company plans to keep expanding, it also needs to get good at entering systems no single person already knows.

03 / TEST THE PATH

03 / TEST THE PATH

Demand is not enough.

A market can contain real customers and still be a bad place for the next deployment. The surrounding system may be too slow, too hostile, too fragmented or simply not ready.

One useful signal is whether your success matters to people in the market.

When a project creates meaningful economic, political or operational upside locally, people have a reason to help. They make introductions. They explain how things actually work. They pull the right people into the room. They help solve problems because they want the project to happen.

That can make a smaller market more executable than a larger one.

But interest can also fool you.

In one market we explored, there was customer demand and real local enthusiasm. There were also regulatory and institutional barriers that would have made a first deployment unusually hard. The company was already taking on first-of-a-kind technology and commercial risk. Adding another first-of-a-kind problem at the market level was not worth it when better paths existed elsewhere.

We stopped investing there.

Do not stack frontiers unnecessarily.

If the product is already new, be careful about choosing a market that also requires a new regulatory pathway, new infrastructure, a new procurement model and a skeptical local system. Sometimes those risks are unavoidable. Do not volunteer for all of them at once.

History matters too.

New companies inherit opinions formed by projects, technologies and companies that came before them. A market may have been burned by an earlier deployment. A customer may have sat through five startup pitches that went nowhere. A community may have a long memory around the technology itself.

You did not create that history, but you still have to deal with it.

Before committing to a market, ask:

Does anyone here have a real reason to help us succeed?

Can this system actually get us to deployment?

What extra frontier or old fight are we taking on by entering here?

If those answers are weak, another round of introductions will not fix the market.

Demand is not enough.

A market can contain real customers and still be a bad place for the next deployment. The surrounding system may be too slow, too hostile, too fragmented or simply not ready.

One useful signal is whether your success matters to people in the market.

When a project creates meaningful economic, political or operational upside locally, people have a reason to help. They make introductions. They explain how things actually work. They pull the right people into the room. They help solve problems because they want the project to happen.

That can make a smaller market more executable than a larger one.

But interest can also fool you.

In one market we explored, there was customer demand and real local enthusiasm. There were also regulatory and institutional barriers that would have made a first deployment unusually hard. The company was already taking on first-of-a-kind technology and commercial risk. Adding another first-of-a-kind problem at the market level was not worth it when better paths existed elsewhere.

We stopped investing there.

Do not stack frontiers unnecessarily.

If the product is already new, be careful about choosing a market that also requires a new regulatory pathway, new infrastructure, a new procurement model and a skeptical local system. Sometimes those risks are unavoidable. Do not volunteer for all of them at once.

History matters too.

New companies inherit opinions formed by projects, technologies and companies that came before them. A market may have been burned by an earlier deployment. A customer may have sat through five startup pitches that went nowhere. A community may have a long memory around the technology itself.

You did not create that history, but you still have to deal with it.

Before committing to a market, ask:

Does anyone here have a real reason to help us succeed?

Can this system actually get us to deployment?

What extra frontier or old fight are we taking on by entering here?

If those answers are weak, another round of introductions will not fix the market.

04 / CARRY FORWARD

04 / CARRY FORWARD

After a market works, it is tempting to save the playbook and repeat it.

Keep the parts that actually travel.

The useful carryover is usually not the contact list. It is knowing which kinds of people tend to matter, where to look for information, which questions expose viability, what evidence builds credibility and when to stop spending time.

Other things need to be rebuilt: local relationships, physical constraints, regulation, permitting, political history, who holds influence and what proof this market needs.

So keep the search pattern. Relearn the market.

This does not need a giant knowledge-management project. Keep enough structure that the next person can see what was tested, what changed the team's mind, what kept coming up and why the company decided to keep going or walk away.

AI is useful here too. It can pull prior work forward, compare what the team is hearing across markets and surface patterns that would otherwise live in meeting notes and people's heads.

It cannot tell you whether someone actually trusts you, whether a local stakeholder has real influence or whether an encouraging conversation will turn into a deployment.

Those still require judgment.

By the fifth market, the company should not expect relationships or credibility from the first four to magically transfer. It should be much better at finding the right people, asking the questions that matter, figuring out what proof will move them and walking away from bad paths earlier.

That matters more in physical technology because learning can be expensive. The wrong market can consume hardware, engineering time, regulatory goodwill and months of runway before the mistake becomes obvious.

THE OPERATOR NETWORK

Built with people actually building frontier companies.