Chapter 10. Moving from an Idea to a Testable Offering
A business idea becomes more meaningful when founders can place it in front of prospective users, observe what happens, and use the results to make informed decisions. Before investing heavily in full-scale product development, hiring, inventory, facilities, or marketing, founders can create a testable offering that helps answer important questions.
A testable offering may be a prototype, minimum viable product, service pilot, limited release, demonstration, or feasibility test. Its purpose is not necessarily to represent the final product. It is designed to reduce uncertainty by showing what can be built, what customers value, what problems remain, and what the company should do next.
Moving from an idea to a testable offering can represent an important early-stage business achievement. However, building something is only part of the progress. Founders should also document the assumptions tested, evidence collected, lessons learned, and changes made afterward.
Beginning with a Clear Assumption
Every new product or service is based on assumptions. Founders may assume that a particular customer has an important problem, that the proposed solution can address it, that customers will pay for it, or that the business can deliver it affordably.
A useful test begins by defining one assumption clearly. For example:
- Small retailers need a faster way to manage inventory.
- Patients will use virtual appointments for routine follow-up care.
- Manufacturers will pay for software that reduces equipment downtime.
- Local businesses want a managed service for producing short educational videos.
These statements can be investigated. In contrast, a broad claim such as “everyone will love our product” does not define a specific customer, problem, behavior, or result that can be tested.
Creating a Prototype
A prototype is an early representation of a proposed product. It may be a sketch, digital model, interactive screen, physical sample, technical demonstration, or partially functioning version.
Different prototypes answer different questions. A visual mock-up may help test whether users understand an interface. A physical model may reveal problems involving dimensions, materials, or usability. A technical prototype may determine whether a proposed capability can function under defined conditions.
A prototype does not need every planned feature. It should contain enough detail to investigate the most important uncertainty. Founders should explain what the prototype was designed to test and avoid presenting it as a completed commercial product.
Developing a Minimum Viable Product
A minimum viable product, commonly called an MVP, is a usable early version containing the essential capabilities needed to test the offering with real users. “Minimum” should not mean careless, unsafe, unreliable, or noncompliant. The product must still meet applicable quality, legal, privacy, security, and regulatory requirements.
An MVP can help a company learn:
- Whether customers understand the offering
- Which features they use
- Whether the product solves the intended problem
- Whether users return
- Whether customers will pay
- What prevents adoption
- Which improvements should receive priority
For example, a software company may release an MVP to 50 selected users. If 35 use it repeatedly, 12 purchase a subscription, and several request the same additional capability, the company has gathered more useful information than it would receive from general expressions of interest alone.
The results may be encouraging, but they do not necessarily establish broad market demand, profitability, scalability, or long-term customer retention.
Testing a Service Through a Pilot
Service businesses can also create testable offerings. A consultant, healthcare organization, training provider, logistics company, or marketing agency might introduce a limited pilot for a defined customer group.
A service pilot should specify:
- Who will participate
- What service will be delivered
- How long the pilot will operate
- What responsibilities each party has
- What success will look like
- Which measurements will be collected
- What happens when the pilot ends
For example, a training company might deliver a six-week pilot to one employer and measure enrollment, completion, participant feedback, skill improvement, and the employer’s willingness to continue. A successful pilot can demonstrate early value, but one organization’s experience may not represent the wider market.
Conducting Feasibility Testing
Feasibility testing examines whether an idea can be implemented under realistic conditions. Technical feasibility asks whether the product can work. Operational feasibility considers whether it can be produced and delivered reliably. Commercial feasibility examines whether customers will pay enough to support a viable business.
Depending on the offering, founders may also need to examine legal, regulatory, financial, manufacturing, security, supply-chain, or environmental feasibility. A technically functional product may still be too expensive to manufacture, difficult to distribute, or unable to satisfy applicable requirements.
Founders should identify which form of feasibility was tested. Passing one test should not be presented as proof that every aspect of the business model has been validated.
Turning Test Results into Product Progress
Not every successful test confirms the original idea. A test may show that customers prefer another feature, resist the proposed price, require a simpler buying process, or experience a problem the founders did not anticipate.
This information can still produce valuable progress. A disciplined company uses the evidence to revise the product, change the target customer, improve delivery, adjust pricing, or discontinue an unsupported feature.
Early product development is often a cycle:
- Define an assumption.
- Build the simplest responsible test.
- Observe customer behavior.
- Measure the result.
- Identify what was learned.
- Make a documented change.
- Test again.
Investors may value this process because it can demonstrate execution, learning, customer awareness, and responsible use of capital. However, prototypes, MVPs, feasibility tests, and pilots do not guarantee investment, commercial success, or product-market fit.
Product-Progress Exercise: Define What You Built and Learned
Select one prototype, MVP, service pilot, or feasibility test and document:
- Original assumption: What did the company believe?
- Uncertainty: What important question needed to be answered?
- Testable offering: What exactly did the company build or deliver?
- Participants: Who tested or experienced it?
- Test performed: What did the company ask participants to do?
- Measurement: Which behaviors, responses, costs, or results were tracked?
- Result: What actually happened?
- Learning: Which assumption was confirmed, rejected, or revised?
- Change made: What did the company modify afterward?
- Evidence: What records support the test and its results?
- Limitations: What has not yet been demonstrated?
- Next test: Which uncertainty should be examined next?
Complete this statement:
We originally assumed __________. To test this assumption, we built or delivered __________ for __________. The test produced __________, which taught us __________. Based on that evidence, we changed __________ and will next test __________.
A strong product-progress record does more than announce that something was built. It shows how the company converted an idea into evidence, used that evidence to learn, and made a better-informed product-development decision.