A Small Problem. A Very Real Possibility.

A useful product starts with a recurring problem. Look for repeated work, confusing decisions, or an awkward process that people already spend time or money solving.

Test the outcome before the product.

You may be able to deliver the result manually before building a tool. A simple template or a worked example can help someone assess whether your approach is useful.

Your next move

Sketch a sample and show it to three people who experience the problem. Ask them to use it on a real task. Notice where they struggle and whether they ask to use it again. Interest is a signal to investigate, not proof of a business.

Look more closely.

Start by watching how someone handles the task now. Where do they repeat work, make mistakes, or lose time? A sample built around that moment will tell you more than a list of features. If you can deliver the result manually, learn from that before automating it.

A working example

Imagine a coach who repeatedly assembles the same onboarding information for each client. The useful result is a clearer onboarding process. A checklist, a template, or a small tool could deliver it. This example illustrates a test; it does not establish a market.

Questions for your notebook

• Who repeats this task, and how often?
• What does the current workaround cost in effort or money?
• Can a simple sample improve a real instance of the task?
• What would make someone choose this over doing nothing?

A download is only the beginning.

Notice whether someone returns, uses the sample in real work, or asks for it again. Ask what they would miss if it disappeared. Keep track of support questions and delivery effort, too: they are part of whether the idea can become a workable business.