Build an MVP product
To build an MVP product, define it and its buyer, make the right prototype, choose suppliers, check costs and margins, get production-ready, then launch and learn.
Prototype to Productionfollows the order of Cydney Mar's Concept-to-Reality Pathway, because order matters as much as effort. Most product ideas that stall were not bad ideas. They took the right steps in the wrong order, and paid for it in rework, delays, and wasted samples.
Last updated: Published by Cydney Mar
Six steps, in this order. Each one protects the next.
Write down what you are making, who it is for, the problem it solves, and the price a buyer would pay. Lock this before sampling. Jumping into samples without clarity is one of the most common and expensive mistakes.
Make only the samples that answer real questions about fit, function, or finish. A clear, professional tech pack helps a sample come back right the first time instead of after months of back-and-forth.
Vet suppliers for quality, communication, and reliability. Request samples, notice how clearly they respond, and get minimum order quantities and lead times in writing.
Add up the full landed cost per unit: materials, labour, packaging, freight, and duties. Compare it with your selling price and the margin each sales channel needs.
Finalize specifications, approve the sample, and set up systems for consistent manufacturing, quality checks, and reorders.
Put your MVP in front of real buyers through retail, DTC, or TV. Measure what they do, hold budget back for changes, and scale what works.
An MVP should include only what a buyer needs to decide whether the product solves their problem and is worth the price. For physical goods, that usually means the core function, acceptable quality and finish, accurate sizing or dosage, and protective packaging.
WeWeb cites studies showing roughly 64% of features in software products are rarely or never used (WeWeb). Physical products have their own version of this: extra colourways, sizes, and scents multiply samples and minimums before you know what sells.
According to Cydney Mar, founders usually stall for four reasons: they jump into sampling without clarity, choose suppliers on guesswork, ignore margins until it is too late, and try to figure it out as they go.
Each of those maps to a step above. If you want to know what the steps cost, read how much an MVP costs. If you want help, compare your options in how to choose an MVP product development consultant, or go back to the main MVP product development guide.
Short answers below. Read all 48 on the MVP and product development FAQ.
To build an MVP, define the product and its buyer, make the right prototype, test it with real people, then fix what they tell you before committing to production. For physical products, add supplier selection, costing, and margin checks before you order. The Concept-to-Reality Pathway follows this order: clarity, prototypes, suppliers, costs and margins, production readiness, and launch.
The steps in developing a physical product MVP are: clarify what you are making and who it is for, develop the right prototypes, choose vetted suppliers, calculate costs and margins, finalize specifications for consistent manufacturing, and launch through retail, DTC, or TV. Taking the right steps in the wrong order is a common reason product ideas stall.
An MVP should include only what a customer needs to judge whether the product solves their problem and is worth the price. For a physical product, that usually means the core function, acceptable quality and finish, accurate sizing or dosage, and protective packaging. Extras can wait. WeWeb cites studies finding roughly 64% of features in software products are rarely or never used.
You get an MVP by building it yourself, hiring a developer or agency, or working with a product development consultant who guides you through samples, suppliers, and production. For software, agencies are common. For physical products, an experienced guide helps you avoid expensive sampling mistakes. Cydney Mar's Concept-to-Reality Pathway is one structured option for founders with a product idea.
Published software timelines vary widely. Techformation says MVP development typically takes 6 to 12 weeks depending on project size and tech stack, and Brocoders reports published build windows from 8 weeks (Emerline) to 6 months (ScienceSoft on a low-code base). Physical product timelines depend on sampling rounds, supplier lead times, and order sizes, so confirm yours directly.
A tech pack is the technical document that tells a factory exactly how to make your product: measurements, materials, construction, colours, and labelling. Cydney Mar describes a clear, professional tech pack as the difference between a sample that is right the first time and months of expensive back-and-forth. It is a core part of her product development work.
Back to the main guide: working with an MVP product development consultant.
Share your idea, your stage, and where you feel stuck. You will leave the conversation knowing your next step.
Published by Cydney Mar
