Writing your business plan: product development
Updated: Oct 7

What will your product do? Who is it for? How will you know it is useful? Who will build it and what will it cost?
These questions belong together. Your product development plan should connect what you intend to build with the customer need, the resources available and the evidence you want to gather.
It should help you make decisions as well as explain your approach to someone else.
For founders, that means being clear about what needs to happen next without pretending you can predict every feature or requirement years in advance.
Start with the customer and the outcome
Describe who the product serves and what it helps them achieve.
Explain how they handle the problem today and why they might change. If you have several possible customer groups, identify which you will focus on first.
Be clear about what already exists. Are you exploring an idea, testing a prototype, improving a working product or expanding something customers already use?
If you run a service business, the same questions apply to how the service is designed and delivered. Think about the experience from first contact through to the outcome the customer receives.
Where demand is still uncertain, revisit whether your solution fixes a problem that needs fixing before committing to substantial development.
Decide what the first version needs to prove
A minimum viable product, or MVP, should help you learn something important by putting a usable offering in front of the intended customer.
The word “minimum” can become an excuse for an experience that is too incomplete to be useful. Equally, trying to make the first version perfect can delay learning and consume the budget.
I like the ambition behind creating something customers can love. The practical question is what needs to work well for them to experience the value you are promising.
Identify the assumption you need to test. For example:
Can customers complete the task the product is designed for?
Does it improve enough on their current approach to matter?
Will they keep using it?
Will the buyer pay for the benefit?
Choose the smallest sensible version that helps you investigate that assumption. Some questions can be explored with a prototype or a manually delivered service before you build a complete product.
Be clear about the limitations. A successful demonstration is different from evidence that a product works reliably in everyday use.
Explain who will develop the product
Your plan should identify the capabilities required and how you intend to access them.
That might involve a technical co-founder, employees, freelancers or a development partner. The right arrangement depends on the work, its complexity and how much ongoing development you expect.
Include who will decide priorities and assess the quality of what is delivered. Someone needs to understand the customer need, make trade-offs and keep the work connected to the business.
If you are a non-technical founder, consider where you need experienced technical input to assess proposals and explain risks.
Think beyond the first build too. Who will maintain the product, resolve problems and take over if a supplier or team member leaves?
For more on that decision, see whether your startup needs a full-time developer.
Build customer learning into the work
Plan how you will gather feedback throughout development.
Recruit people who reflect the customers you intend to serve. Friends and supportive contacts may help you get started, but their circumstances and willingness to participate can differ from those of a paying customer.
Decide what each round of testing is intended to reveal. You might observe someone attempting a task, discuss their experience or examine how they use the product over time.
There is no single number of participants that answers every research question. A small round of testing can reveal useful problems, but it cannot establish everything about demand, usability or the wider market.
Use the findings to decide what to investigate next.
Make participation straightforward and allow time for recruitment. Finding suitable people can be part of the work, especially when you need access to a particular role or buying situation.
Decide how you will judge progress
Choose measures that relate to the outcome you are trying to create.
Depending on the product, you might look at whether customers complete a task, how much help they need, whether they return or whether they choose to pay.
Combine those observations with conversations. Usage figures can show what happened, while customer feedback can help you understand why.
Avoid treating every request as an instruction to add a feature. Ask what the person is trying to achieve and whether the request reflects a wider need among your intended customers.
Your plan should explain what evidence would justify continuing, changing direction or stopping a piece of work.
Create a roadmap that explains your priorities
A product roadmap should show the direction of development and the reasons behind it.
Focus on the customer or business outcome each stage is intended to support. A list of features and dates can leave those reasons unclear.
For each priority, record:
The problem or opportunity you are addressing.
The outcome you want to achieve.
The evidence supporting the work.
The main dependencies or uncertainties.
How you will assess the result.
Keep near-term work more specific than work further into the future. Explain where timing depends on research, hiring or another piece of development.
If everything is a priority, the roadmap is not helping you choose. Be prepared to leave worthwhile ideas for later so the team can concentrate on what matters most now.
Plan how the product will reach customers
Development and commercial planning need to inform each other.
How will suitable customers find the product? What will they need before they can use it? Will they require setup, training, integration or support?
If you are offering a trial or pilot, agree what it includes, how long it lasts and what you both want to learn. Make the next step clear, including whether and how the arrangement could become paid work.
Your sales plan should reflect the buying process. Your development plan should account for what you need to deliver on those commitments.
Be cautious about promising new features to win individual customers. Consider whether the work supports your wider direction and whether the team can realistically deliver it.
Include the costs beyond the first build
Estimate what each stage will require and when you expect to spend the money.
Alongside development, consider customer research, testing, hosting, maintenance, support and any specialist input the product needs.
Identify requirements involving areas such as accessibility, data handling, security or sector-specific standards early enough to seek appropriate advice and include the work in your plan.
Make uncertain estimates visible. Explain what might change the cost and when you will have better information.
You will not always be able to attach a direct financial return to each improvement. Some work supports learning, reliability or the ability to serve customers properly. Explain the purpose and how it connects to the business.
Bring the product development section together
Your finished section should explain:
Who the product serves and the outcome it provides.
What exists today and what the next version needs to prove.
Who will build, manage and maintain it.
How customers will be involved in testing.
The priorities and reasoning behind the roadmap.
How you will introduce and support the product.
The costs, dependencies and decisions ahead.
Keep detailed specifications elsewhere. The business plan should make the development approach understandable and show how it supports the wider business.
Keep making deliberate choices
As you learn, some ideas will become more valuable and others will lose their appeal.
The difficult part is often choosing what to build, what to delay and what to stop. Those decisions become harder when customers, investors and team members want different things.
Return to the customer outcome, the evidence and the resources available. Update the plan when your understanding changes.
If you would value space to work through product priorities, competing demands and your role in those decisions, explore working with me through founder coaching and mentoring.
Cheers,
Duncan




Comments