An idea can be personally exciting and still lack paying customers. Before ordering equipment, buying expensive software or printing hundreds of packages, try to find out what problem people actually experience and what they currently do about it. Market research cannot guarantee a successful business, but it can reduce decisions driven only by enthusiasm. The goal of this seven-day exercise is to learn something that could change the idea before you make large commitments.
Useful first step: Understand the problem, seek evidence or consent where needed, and choose a small action that remains safe, respectful and practical.
Define a customer problem without selling the solution
Write a clear sentence about the person you hope to serve, the situation they face and the practical difficulty they experience. Avoid describing your app, logo or product features first. For example: ‘Small community organizers struggle to collect reliable attendance confirmations.’ That is more testable than ‘Everyone will love my new events platform.’ Separate what you know from what you assume. If you have only experienced the issue personally, treat the assumption of broad demand as untested. The US Small Business Administration recommends market research and competitive analysis to understand customers and differentiate an offer.
Study existing alternatives respectfully
Search for services, informal workarounds and competing products that help the same audience. Make a short table of their value proposition, limits, public pricing and distribution method where available. Do not copy private data or violate platform terms to gain insights. A competitor may already solve the problem well, which can be useful evidence against building another solution. Conversely, an underserved niche may value something different, such as accessibility, local language or trustworthy support. Avoid claiming a market gap simply because you have not heard of a product.
Talk to people without leading them
Instead of asking ‘Would you use this amazing idea?’, ask when they last faced the problem, how they handled it, what was inconvenient and what the solution cost in time or money. Listen for concrete behaviors rather than polite compliments. Tell participants why you are collecting feedback and avoid gathering unnecessary personal details. Five conversations may reveal useful questions, but they do not statistically represent a population. Do not advertise invented survey percentages or treat compliments as proof that people will pay.
Calculate costs before pricing
List recurring costs, payment fees, delivery or fulfillment expenses, refunds, customer support and likely compliance obligations. Add the one-time costs of prototypes, tools and professional advice where needed. For a hypothetical product sold for 200 units with 80 units of direct costs and 20 units of fees, the contribution before fixed expenses is 100 units. This is illustrative arithmetic, not a recommended price or profit forecast. Taxes, returns, acquisition costs and local laws can change the economics substantially. Avoid offering regulated services without qualified review.
Run a small ethical demand test
When feasible, build a one-page explanation, sample service description or simple prototype rather than a complete platform. Ask potential customers to perform a meaningful action: request a demonstration, join a transparent waitlist or explain which existing expense the offer could replace. Do not use fake scarcity, hidden charges, invented reviews or collect payments for something you cannot deliver. Clearly disclose that the concept is being tested. A small test can reveal confusing language or missing features even when it does not produce sales.
Choose a decision rule before seeing results
Decide what evidence would make you continue, revise or stop. It could be a realistic number of qualified demonstration requests, repeated reports of the same problem or a cost estimate that stays within your budget. Do not turn an arbitrary threshold into a scientific certainty. After the test, write which assumptions were supported, which were contradicted and what you will investigate next. Stopping a weak idea before large spending may be a useful outcome. A project is not a moral test of whether you are entrepreneurial.
A realistic worked example
A student considers a reservation tool for local hobby groups. Instead of coding a full platform, the student interviews organizers about missed bookings and current spreadsheets. Several report they already use free tools successfully, but two struggle with collecting cancellation notices. The student creates a basic demonstration addressing that narrower problem and tests whether it fits actual workflows. One possible outcome is a smaller product; another is deciding not to build it. Neither result requires pretending that research guarantees a market.
Seven practical steps
- Write the customer problem in one sentence
- List five competing or substitute approaches
- Interview potential users about recent behavior
- Estimate real delivery and support costs
- Create a simple transparent demonstration
- Choose a realistic test metric beforehand
- Continue, revise or stop based on evidence
Questions people ask
Do I need to register a company before testing?
Legal and tax requirements vary by jurisdiction and activity. Research and nontransactional prototypes may differ from selling regulated goods or services.
Are five interviews enough?
No small set can prove market size. Interviews are useful for finding patterns and improving questions.
What if people say they love it?
Ask what they currently do, what they would replace and what concrete next action they are willing to take.
Related reading
For more ideas, read Side-hustle starter plan or Free weekly planner. Discover additional articles in the Practical Guides Library.
Sources and important context
This is educational material, not individualized medical, legal or commercial advice. The example is an editorial illustration, not a reported case study. Reviewed October 2026. See our editorial standards.
