TL;DR Commercialization isn't a phase that starts after engineering and regulatory finish. It starts the day you decide what to build, because every design decision either removes friction for the buyer or adds it. The breakthrough ideas that become real businesses are usually the ones that were easiest to adopt, not the ones with the most impressive technology.
From the LifeSci Continuum podcast: In my conversation with Nathalya Mamane and Dr. Michael Mina of Anywhere Dx, one line stuck with me more than any other. A simple user experience is not simple to build.
That sounds like a throwaway. It's actually the whole game.
Anywhere Dx is working on a saliva-based molecular strep test a family can use at home. The chemistry behind that is hard. The point of the company is to make sure none of that hardness lands on the parent holding the test at 7 a.m. with a sick kid. Every bit of complexity they absorb inside the product is complexity the customer never has to deal with. That's an engineering choice, a design choice, and a commercial choice, all at once.
Here's what most teams get wrong about that.
Why do so many breakthroughs never become businesses?
Healthcare is full of amazing inventions. Far fewer become successful businesses.
The gap is rarely the science. Most of the failures I've watched had real technology behind them, sometimes technology that was clearly better than what the market was using. What they didn't have was a path to adoption that anyone had designed on purpose.
That gap has a name. It's commercialization, and it's badly misunderstood.
Ask ten technical founders when commercialization starts and you'll hear some version of "after we have a product to sell." After the design freezes. After the submission clears. After we hire a sales team and build a website. Commercialization, in that view, is the stuff that happens once the hard work is done.
That's backwards, and it's an expensive kind of backwards.
Commercialization starts the day you decide what to build. Every requirement you set, every feature you include, every step you ask the user to perform is a commercial decision wearing an engineering costume. You're either making the product easier to adopt or harder to adopt, and you're doing it long before anyone writes a tagline.
Why does commercialization actually start on day one?
Because by the time the product is finished, most of the decisions that determine whether it sells are already locked.
Think about what gets set during development. Who the product is for. What job it does. How many steps it takes to use. What it costs to make, which sets the floor on what it costs to buy. What evidence you'll be able to show. What claims you can make. What workflow it assumes.
Every one of those shapes adoption. And every one of them gets harder to change as you go.
Early on, changing the target user is a conversation. After a 510(k) is written around a specific intended use, it's a new submission. Early on, cutting three steps out of the workflow is a design sketch. After manufacturing tooling is committed, it's a redesign and a revalidation. The cost of a commercial decision climbs steeply the longer you wait to make it, and the decisions you never consciously made get made for you by default.
This is why I push founders to treat commercialization as an input to development, not an output of it. The question isn't "how will we sell this once it's built?" It's "what should we build so that it sells?" Those produce very different products.
Anywhere Dx is a clean example. They didn't start with a molecular platform and then hunt for a market. They started with a frustrated parent and a specific job — confirm strep at home without losing a day — and let that job set the requirements. Saliva instead of a throat swab, because a swab is miserable for a kid. A result a parent can trust without a clinician reading it. A price a household can actually pay. Those aren't marketing decisions bolted on at the end. They're product decisions that are commercial to the core, made at the beginning.
Who actually sells your product when no one from your company is in the room?
Your product does. And in complex markets, it's doing that far more than your sales team is.
Gartner's research on the B2B buying journey found that 75% of B2B buyers say they prefer a rep-free buying experience, and that buyers move through the purchase by looping through six "jobs" — problem identification, solution exploration, requirements building, supplier selection, validation, and consensus creation — in no fixed order. Most of that happens without a salesperson anywhere near the buyer.
Sit with what that means for a health tech product. For most of the decision, the thing representing your company is your product, your evidence, your website, and whatever a champion can forward to the people who have to say yes. If those don't do the commercial work on their own, no amount of sales effort at the end recovers it.
So the product has to be built to sell itself. That's not a slogan. It's a design requirement, and it changes what you build.
It means the evidence a buyer needs exists because you planned the studies that generate it. It means the workflow is simple enough that a champion can explain it in one sentence to a skeptical colleague. It means the value is obvious enough to survive being passed secondhand through an organization. Gartner's own guidance to suppliers is blunt about this: the content that moves buyers is grounded in the buyer's needs, not the product's capabilities. That's a commercialization principle you build in, not a campaign you run later.
What does building for commercialization actually look like?
It comes down to a handful of decisions, made early and revisited often. None of them are marketing. All of them are commercial.
Start with the customer outcome, then work backward. Define the result the customer wants in their own terms, and let that set your requirements. "A parent gets a trustworthy strep answer at home in minutes" is an outcome. "A saliva-based molecular assay" is a means to it. Lead with the outcome and the means has to earn its place.
Write product requirements from real problems, not internal wish lists. The best requirements come from watching people struggle with the current way, not from a whiteboard of features you're capable of building. If a requirement can't be traced back to a real customer problem, it's a candidate for cutting.
Prioritize simplicity, because simplicity is a commercial advantage. Every step you remove for the user is a reason to adopt. Dr. Mina's point about a simple experience being hard to build is exactly right, and it's worth the cost. The complexity has to live somewhere. Better it lives inside your product than in your customer's day.
Design for the workflow the customer already has. A product that fits how people already work gets adopted. A product that demands they change five habits gets admired and shelved. Map the real workflow — including the boring parts — and design to slot into it. This is where journey mapping earns its keep, because it shows you the friction you can't see from inside the company.
Build the evidence your buyers actually care about. Clinical performance matters, but buyers also need economic and practical proof — what it costs, what it replaces, what changes for them. Decide early what evidence each decision-maker needs, then make sure your development plan produces it. Evidence you didn't plan for is evidence you won't have when a deal depends on it.
Align product, marketing, sales, and regulatory before launch, not at it. When these four groups meet for the first time at launch, you discover the claims marketing wants aren't the claims regulatory cleared, and the workflow sales is promising isn't the one the product supports. Getting them in the same room during development is unglamorous and it prevents most launch disasters.
Treat commercialization as a thread through development, not a stage after it. The teams that do this well keep one question live the entire time: does this decision make the product easier to adopt, or harder? Asked often enough, that question reshapes the roadmap.
Why does the easiest product to adopt usually beat the best technology?
Because buyers aren't grading your technology. They're deciding whether adopting it is worth the risk and effort, and "best" and "easiest to adopt" are not the same axis.
Geoffrey Moore made this point decades ago in Crossing the Chasm, and it holds up. The early adopters who love a product for its brilliance are a different crowd from the pragmatic majority who decide most of your revenue. That majority doesn't buy the most advanced option. They buy the one that's proven, low-risk, and easy to fold into what they already do. A breakthrough that never crosses from the first group to the second is a breakthrough that doesn't become a business.
I've watched two products go head to head where the technically superior one lost. Not because the buyer couldn't tell the difference. Because the "better" product asked for a workflow change, a revalidation, and an internal argument that no one wanted to have, and the "good enough" product slid in without a fight. Adoption went to the path of least resistance, and it usually does.
This is the uncomfortable part for technical founders, so I'll say it plainly. The quality of your science sets whether you deserve to win. How easy you make adoption often decides whether you actually do. You need both, and teams reliably overinvest in the first and underinvest in the second.
What are the most common commercialization mistakes founders make?
A few patterns show up again and again. Each one comes from treating commercialization as a later problem.
Sequencing it last. Building the product, then asking how to sell it. By then the decisions that determine sellability are frozen.
Confusing commercialization with promotion. Thinking it's the website, the deck, and the ad spend. Those are the visible tip. The real work is product, positioning, evidence, and pricing, decided far earlier.
Designing for the demo, not the workflow. Optimizing for the impressive first impression instead of the hundredth real use. A demo wins the meeting, but it's workflow fit that earns the renewal.
Generating the wrong evidence. Proving what's scientifically interesting instead of what a buyer needs to say yes. Great data aimed at the wrong question doesn't move a deal.
Keeping the teams apart. Letting product, regulatory, sales, and marketing operate in sequence instead of together, so their assumptions only collide at launch.
The thread through all of them is the same. Commercialization got treated as something that happens to a finished product, instead of something the product is built around.
Where a fractional CMO changes the outcome
Commercialization isn't advertising, and it isn't a function you bolt on when you're ready to launch. It's the work of aligning product decisions, customer insight, positioning, evidence, pricing, sales enablement, and go-to-market — and most of that work has to happen while the product is still being shaped.
That's where a fractional CMO earns their place. The value isn't running campaigns. It's sitting in the room during development as the person asking the commercial questions while they're still cheap to answer.
Is this requirement solving a customer problem or an internal preference? What evidence will each decision-maker need, and does our plan generate it? What has to be true about price for this to reach the buyers we're aiming at? Where is the friction that will keep a champion from getting a yes? Are we building around a real job, or around a capability we're proud of?
Those aren't questions a marketing team answers after launch. They're questions that reshape the product before launch, which is exactly why they need a commercial voice in the room early. The point of an outside partner is objectivity and timing — someone who can connect the customer to the product decisions before those decisions harden, and who isn't personally attached to any one feature.
Done at the right time, this is the difference between a launch that confirms a market and a launch that goes looking for one.
The founder takeaway
The best technology doesn't always win. The product that's easiest to adopt usually does.
That's not an argument for building something worse. It's an argument for spending as much of your ingenuity on removing friction for the customer as you spend on the science itself. The companies that turn breakthroughs into businesses are the ones that made adoption easy on purpose, starting on day one.
Anywhere Dx understood the assignment. The hard chemistry is in service of a simple experience, and the simple experience is what gets adopted. That order is the whole strategy.
Frequently asked questions
When does commercialization start?
The day you decide what to build. Every requirement and design choice either makes the product easier or harder to adopt, so commercialization is an input to development, not a phase after it.
Isn't commercialization just sales and marketing?
No. Those are the visible end of it. The larger part is product decisions, positioning, evidence, and pricing — most of which are set during development, long before a campaign exists.
Why do clinically superior products sometimes lose commercially?
Because buyers weigh risk and effort, not just performance. A product that fits the existing workflow and lowers the risk of switching often beats a better one that asks for change.
What does "build the product to sell itself" mean?
Most of the B2B buying journey happens without a salesperson present. The product, its evidence, and its story have to do the commercial work on their own, so they have to be designed to.
How early should we involve commercial thinking in development?
From the first requirements. The cost of changing a commercial decision climbs steeply through development, so the cheapest time to get it right is before anything is locked.
What evidence should we plan to generate?
Whatever each decision-maker needs to say yes — clinical, economic, and practical. Decide that early and build your development plan to produce it, rather than discovering the gap during a deal.
Where to start
If your commercialization plan starts after product development, you're already behind. The good news is that it's fixable at almost any stage, and the earlier you look, the cheaper the fix.
Bring me the product you're building and the buyer you're building it for. We'll find the friction while it's still cheap to remove.
