How to Find Your First Digital Product Idea in Your Sent Folder

A blank document invites ambitious, fuzzy ideas: a complete course, an all-in-one operating system, a template library for every kind of founder. Those ideas can be hard to test because they ask you to invent both the problem and the answer. Your sent messages already contain a better starting point: a problem another person cared enough to ask about.

Open email, Slack, DMs, client follow-ups, or proposal threads. Search for phrases such as “how do I,” “can you send,” “what would you do,” “do you have an example,” and “I am stuck.” Then read the replies you wrote. Do not look for the cleverest thing you have said. Look for the useful response you have written in a similar shape more than once.

Repetition matters because it reduces a common risk of first products: building around a problem only you can see. Two or three related requests do not prove a market, but they do give you a grounded hypothesis. You have evidence of a buyer, a moment of need, and a type of help they found valuable enough to request directly.

Pick one promising thread and write a plain-language brief. Start with the person who asked. What was happening when they reached out? What were they trying to finish, decide, or avoid? Next, name the smallest useful outcome. “Draft a credible launch page today” is a better first outcome than “market your business better.”

Then list the artifact that would have made your reply reusable. If you sent a paragraph explaining a process, the product may be a fill-in-the-blank guide plus an example. If you rewrote an announcement, it may be a prompt pack with a short editing checklist. If you walked someone through tradeoffs, it may be a decision worksheet. Keep the format subordinate to the job.

This also shows you what not to productize yet. Custom context, high-stakes judgment, and work that depends on access to a client’s business usually belong in a service. A first digital product works best when the buyer can bring their own context to a well-bounded tool and make visible progress independently.

Keep the exact phrases from the original messages. They are not ready-made marketing copy, but they help you avoid vague labels. A buyer who says “I cannot tell what to include on this page” is describing a different problem from someone who says “I do not know whether the offer is worth building.” The first may need a copy pack; the second may need validation support.

Before you build, test the brief with a small conversation or a narrow page. The goal is not applause. Ask whether the trigger feels familiar, whether the proposed asset would be useful in that moment, and what would make it more practical. The offer validation guide can help you set that test up without expanding the work too early.

The first idea is usually stronger when delivery is simple. A well-organized PDF, editable document, Notion template, or compact set of prompts can be enough if it helps someone complete the job. Do not make a complicated portal, recorded course, or large automation setup the price of learning whether the core asset is useful.

Simple delivery also makes revision easier. When buyers use the first version, you can see where they pause, which examples they reference, and what question still appears. Those observations tell you whether to improve the instructions, add a missing example, or choose a different buyer moment. They are more useful than trying to predict every possible need in advance.