How do we turn a new business concept into a strategy we can evaluate?

A new product or business innovation concept that has not yet been turned into a specific strategy causes a particular kind of trouble, and it rarely gets recognized for what it is.

In a review, two people who both support the concept still argue for an hour without agreeing. One of them is picturing the company selling a finished product differentiated by a new technology. The other is picturing the company selling that same technology as an ingredient to the manufacturers who build those finished products. Neither says so, because neither realizes the other is describing a different business. Simply because those strategy choices haven’t been made or stated explicitly. Separately, the financial model cannot be built, because nobody can say who is buying or what they are paying for. And when the opportunity is set beside another one for funding, there is no honest basis for comparison, because the two were never described in the same terms or worked to the same depth.

In the room, none of this gets named as the actual problem. It looks like a difficult project, or a team that needs more time.

A concept usually describes more than one business

An idea arrives as a direction, not a plan. Inside that direction sit consequential choices nobody has made yet. Which customer segment, and which unmet need of theirs. What the offering has to be better at, and better than what. How much of the whole solution the company provides and how much comes from somewhere else. How it gets built and delivered. How it makes money. What gets done first and what waits.

Until enough of those are settled, the concept still describes several different potential business strategies. You cannot test it, because there is no specific claim to test, and many of the undefined choices may at best be inconsistent with each other and at worst contradict each other outright. You cannot easily compare it to another opportunity, because one of them is defined and the other is a range. You cannot decide what to spend on it next, because the answer depends on which version you meant.

This is the work that has to happen before validation can start, and it is more often the reason a promising concept stalls than any failure of analysis. As we have written elsewhere, the hardest part of early strategy work is usually not the analysis, it is discovering how much of the strategy was never actually decided.

The strategy choices that no one actually chose

The open choices are the more obvious part of the problem. The larger one is the choices that were made without anyone experiencing them as choices.

In a mature company, a new venture often unwittingly inherits strategy choices from the core business. It will be built in house, because that is how we build our core business products. It will carry the company brand. It will go through the existing sales channel, to something like the existing customer, with the same sales model. None of those were considered and consciously decided for the new venture. They were unconsciously taken as givens without even considering alternatives.

As our Strategy Framework page puts it, strategy assumptions often go unstated precisely when they are assumed to be consistent with the core business. That is what makes them dangerous. A choice nobody made is an assumption nobody wrote down, which means alternative and potentially better choices never get considered, it never reaches an assumptions list, never gets tested, and is invisible to the person reviewing the case. When the venture later fails on channel economics or a brand mismatch, it reads as a surprise. It was a decision, taken by default, months earlier.

The useful move is not to challenge every inherited answer. Some of them are right, and near-core ventures legitimately share a great deal with the core. The move is to make them visible, so that keeping one is a decision rather than an accident.

Why staying general is the rational (but wrong) thing to do

Teams do not define concepts vaguely because they are careless. They are vague because narrowing is often punished.

Most corporate funding decisions are binary. Fund it or do not. In that setting, committing early to one customer and one business model feels like betting the whole concept on choices you cannot yet defend, when or if those assumptions turn out to be wrong. The investment method does not leave room to learn and modify the strategy before significant resources are committed. Staying general keeps options open and keeps the concept alive a little longer.

It also makes the concept impossible to evaluate and fund honestly on its merits. That is the trap: the behavior that protects a concept in the short term is the same behavior that prevents it from ever being evaluated appropriately. It may get funded on the strength of the story or on confidence in the venture leader, but the investment cannot be sized appropriately, and the work cannot be prioritized around the most consequential assumptions. If it succeeds, that is more likely to be luck than repeatable discipline.

What a “good enough” strategy hypothesis looks like this early

Not certainty, and not a detailed business plan. Nobody has certainty about a business that does not exist yet, and pretending otherwise produces a different kind of failure.

Good enough means a stated choice with the belief behind it visible. Not “we will sell to enterprises” but “we believe the buyer is the operations lead in mid-sized logistics firms, because they carry the cost of this problem and already hold budget for adjacent tools.” The first cannot be argued with. The second can be argued with, tested, and revised as evidence arrives.

That is the standard worth holding at this stage. Every consequential choice named, each one paired with the belief or assumption that supports it, all of it written where someone else can see it and push back. The strategy then has somewhere to go: beliefs get tested, some survive, some change, and the strategy evolves with the learning rather than being rewritten from scratch each time.

Why canvases and frameworks alone often do not get a team there

Most teams reach for a canvas or framework at this point, which is the right instinct. Then they hit three practical problems.

The frameworks in wide circulation are introduced and explained with finished, already-worked examples: a complete strategy mapped neatly into the boxes. Reading one of those is a different exercise from using the same framework to define a strategy that is still forming, and the tidy example makes it look easier than it is.

They also do not fit together. Each covers a slice, and the slices were not built to interlock, so assembling several leaves gaps between them and uneven depth within them. Nothing tells you that the dimension that matters most to this particular venture got less attention than the one the team already understood.

And a framework on a page cannot respond. It cannot tell you that a choice you just made contradicts one you made two boxes ago, or that the assumption you have leaned on is carrying more weight than any other assumption in the model.

Those are solvable problems, and most of them are the kind software is good at: enforcing completeness, checking consistency, and giving feedback while the work is being done. Which makes it strange how few products do it. There is no established directory category for this work, which is a gap we wrote about in an earlier post in this series, and the thin supply follows from the missing category.

There’s an app for that: how Growth Forge® Software addresses this

Growth Forge treats the strategy hypothesis as a model rather than a document: the choices in each dimension stated explicitly, the beliefs behind them attached, and the whole thing examinable as a set rather than read as a narrative.

The part that matters at this stage is that the fidelity rises with your commitment, and the same dimensions carry through as it does. Low Fidelity Strategy Modeling is the early entry point, about as quick to populate as a one-page canvas, and it is built from the same underlying inputs the fuller tools use. So the hour spent on it is not thrown away when the venture earns more attention.

Financial logic shows the progression clearly. It starts as a handful of order-of-magnitude assumptions. It becomes a simplified view of what the business would look like at maturity. As the venture earns more work, that single dimension breaks out into discrete tools: market segmentation and sizing, the sales model and revenue forecast, unit economics, and eventually a full cashflow forecast. Every other dimension expands the same way, from a stated choice into focused analysis, without the earlier work being discarded. The full set of tools maps onto the strategy dimensions rather than onto a process the team has to follow in order.

The model also records how much evidence sits behind each assumption and how uncertain the quantitative ones are. That is what makes it possible to tell which assumptions are actually carrying the strategy, and therefore which ones are worth spending time and money to test first.

What software cannot fix

No software can address the reason teams stay general in the first place.

If the funding process is still binary, a team that defines its strategy precisely has simply given the review a clearer target. Their specific choices get picked apart while a vaguer proposal passes untroubled, and the whole organization draws the obvious conclusion about how to write a proposal.

What changes that is a track record built on a different mindset and a different governing framework for exploratory growth investment: staged commitment, smaller decisions taken more often, against evidence appropriate to the stage the venture has reached rather than to the standard a core-business proposal would face. An emphasis on highlighting the pivotal assumptions to be validated, on discovery and learning, and on strategy as a hypothesis that evolves with evidence and insight.

That is an organizational design question, not a tooling one. It means agreeing what a venture has to show at each stage, who decides, and what clearing the bar earns it. Someone inside the organization has to define that and champion it, usually the person running the innovation function. An outside perspective can help design it and can sometimes argue for it more freely, but the internal work of making it stick belongs to whoever owns the function.

Putting it into practice

For a concept that has been discussed more than once without a decision, a few steps move it toward something a review can evaluate. Write down the consequential choices still open inside it: which customer and which need, what the offering has to be better at, how much of the whole solution the company provides, how it gets built and delivered, and how it makes money. State each choice with the belief behind it. Then mark which ones were actually decided and which were simply inherited from the core business. These steps can be worked through with a framework, facilitated by an experienced consulting firm, or with purpose-built software such as Growth Forge, where Low Fidelity Strategy Modeling, Strategy Aspiration and Strategy Builder provide the guidance and the analysis. A concept with its choices written down is not necessarily a good strategy, but it is one that can be tested, compared and improved.

If the gap is not in how your venture strategies get defined but in whether your organization is set up to carry this kind of work at all, our Innovation Capability Assessment is a short scored read on where that stands.

Next in this series: where concepts come from in the first place, and why a capability the company already has so often arrives with a problem attached to it after the fact.

BRI Associates helps companies grow by drawing on decades of practitioner experience in corporate innovation and new business development — practitioners, not pundits or academics — through direct consulting, training workshops, and Growth Forge® Software, built for the unique requirements of corporate innovation and growth organizations.