A product strategy is the commercial roadmap that connects an idea to a viable business. It defines who the product is for, what makes it worth choosing, what you are trying to achieve, and how you will get it to market. This guide walks through building one in the order the decisions tend to arise, and it sits above the hands-on work covered in our guides to design research and idea validation.
A product strategy is the plan that carries an idea from concept to market, and it exists to keep every later decision pointed at the same goal. Without one, development tends to drift: features get added because they are possible rather than because they are wanted, and the cost of that drift usually surfaces late, when it is expensive to correct. Over fifteen years and more than 1,600 projects, the pattern we see most often is that the products which succeed had their commercial direction settled early, before the design work began in earnest.
A strategy does not need to be a long document. It needs to answer a handful of questions clearly, and it needs to be revisited as the market and the product both develop.
Start with the market you are for
Every strategy begins with the target market, because that is where the project ends: with those people choosing to buy, or not. Be specific about who they are, what problem they have, and how they currently deal with it. A common and expensive mistake is to assume the problem you have is a problem others share in the same way. Confirming that the need is real, and shared, is the first commercial decision, and it is far cheaper to make now than after tooling has been cut.
Understanding the market also means understanding the competition. Knowing what already exists, what it does well, and where it leaves people frustrated is what tells you whether there is genuine room for your product and where that room sits.
Define the value you offer
Once the market is clear, the strategy needs a value proposition: a plain statement of why someone would choose your product over what they already use. This is not a marketing slogan. It is the one or two things your product does better, and it shapes everything downstream, from which features matter to how the product is priced and sold.
The discipline here is restraint. Over-designing, adding features beyond the core value, tends to raise the price and dilute the message, and it rarely wins the customers it was meant to. A tighter proposition, aimed squarely at what the market values, is usually the stronger commercial position.
Set objectives you can measure
A strategy needs objectives that connect the product to the wider goals of the business, whether that is a target price point, a margin, a market position, or a launch window. Clear, measurable objectives do two things: they give the development team something concrete to design against, and they let you judge progress honestly rather than by feel. Vague ambitions tend to produce vague products.
Test viability before you commit
This is the stage that most defines how we work. Before significant money is spent, a product idea should be tested from several angles, because a strategy built on an unviable concept is a plan to lose money efficiently. We consider viability at each stage of the process rather than treating it as a single gate, and the main assessments are:
- Marketing insight. Understanding the market opportunity and current conditions, and gauging whether the product's likely appeal justifies going further.
- Technical feasibility. Establishing whether the concept can actually be made reliably, by researching the mechanisms, electronics or materials it depends on.
- Commercial viability. Producing an approximate unit cost, including tooling and production setup, so you know whether achievable margins exist at a price the market will accept. It is entirely possible to design an excellent product that no one buys because it is simply too expensive for its market, and this is the check that catches it.
- Production feasibility. Confirming that what has been designed can be manufactured, which is not always a given.
The value of these checks is that they surface barriers, high component costs, complex assembly, compliance hurdles, while they are still cheap to act on. Sometimes they tell you to stop, and when they do, that is a result worth having: it saves the far larger cost of finding out later.
Plan the route to market
A strategy should look ahead to how the product reaches its buyers and how it scales. That means thinking early about funding, since development costs vary widely and a clear, evidenced strategy is often what unlocks investment, grants or a crowdfunding campaign. It also means thinking about the manufacturing route, because decisions made now about how and where the product is made affect cost, quality and how quickly you can scale when demand grows. Manufacturing is a substantial subject in its own right, covered in our guide to getting a product manufactured.
Build the right team around it
Few founders take a product from idea to market alone, and part of the strategy is deciding who does the work. An in-house team gives you close control and a strong sense of ownership, but carries the cost and management load of permanent staff and specialist skills. Outsourcing to a design and development partner gives you access to a breadth of specialist experience, workshop and prototyping capability, and a sounding board, usually at lower cost for a defined project. Many products are best served by a hybrid: in-house knowledge of the business and the market, combined with outside expertise in design, engineering and manufacture.
Treat the strategy as a living plan
A product strategy is not fixed at the outset and then filed. Markets shift, and feedback from research, prototyping and early customers will teach you things the plan could not anticipate. The strongest strategies are revisited as the product develops, adjusting to what the evidence shows rather than defending the original assumptions. That is not a failure of planning; it is what keeps the plan useful.
In short
A product strategy is a short, practical sequence: define the market you are for, state the value you offer, set objectives you can measure, test viability before you commit, plan the route to market, and build the right team around it. Settle that direction early, keep it honest as the evidence comes in, and the rest of the development process has something solid to build on. Most founders do this best with experienced help, but understanding the path is what keeps you in control of it.
Related guides: Design Research for Product Development · Idea Validation · Commercial Viability Assessment · Designing a Product: A Step by Step Guide
FAQ
What is a product strategy? It is the commercial roadmap for a product: who it is for, what makes it worth choosing, what it aims to achieve, and how it will reach the market. It guides development, marketing and sales decisions and keeps them aligned with the goals of the business.
How is a product strategy different from a product design process? The strategy sets the commercial direction, the market, the value, the objectives, the viability. The design process is how that direction is turned into a resolved product. The strategy decides whether and what to build; the design process decides how.
When should I write a product strategy? Before the design work begins in earnest. The point of it is to settle the commercial questions while they are still cheap to change, so that later decisions have a clear direction to follow.
What is the most common strategic mistake? Assuming the market shares your problem and values it as you do, then building for that assumption without testing it. Confirming the need is real, and that the numbers work, is what a viability assessment is for.
