A practical specialised ebook for creators and solo founders who need to choose, test, and document product ideas without wandering into endless planning.
A practical specialised ebook for creators and solo founders who need to choose, test, and document product ideas without wandering into endless planning.
Solo creators, tiny ecommerce operators, and practical founders choosing between too many possible digital products.
Most digital product ideas fail before the sales page because the maker tries to answer every
question in their head. This logbook replaces imagination loops with tiny evidence sprints. Each
sprint is deliberately small: one question, one action, one decision. You are not trying to prove
that an idea is perfect. You are trying to learn whether it deserves the next hour, the next
weekend, or a clean no.
Every product candidate passes through four filters: painful problem, reachable buyer, compact
deliverable, and repeatable promise. A strong idea does not need to score ten out of ten everywhere.
It needs enough evidence that a specific person would pay for a specific improvement in a specific
format. Use the filters before design work, automation, branding, or long content production.
Set a timer for forty-five minutes. Pick one idea and one question. Gather only the evidence needed
for that question. Write a decision at the end even if the decision is only “pause for now”. The
written decision matters because it protects future you from reopening the same uncertainty every
Monday morning.
The tests in this ebook are grouped by buyer pain, offer shape, proof, production, pricing, and
launch readiness. Run three to five tests per idea. If an idea survives five honest tests, build the
smallest sellable version. If it fails, archive it with gratitude. A rejected idea is not wasted
effort; it is inventory discipline.
Keep one page per idea. Record the question, the evidence, the decision, the next action, and the
date. Over time the library becomes a private map of your market judgement. Patterns appear: which
buyers are reachable, which promises are too vague, which products can be delivered cleanly, and
which ideas only look attractive when they are safely theoretical.
Write the buyer pain in one sentence without using “easy”, “simple”, “ultimate”, or “AI-powered”. If the sentence becomes vague, the offer is not ready.
Describe what the buyer has before purchase and what they can do one hour after opening the product.
Look at public search/autocomplete phrasing and write five buyer phrases in plain language. Do not copy listings; capture intent.
List three ways the buyer currently solves this manually. If there is no workaround, the pain may be weak.
Rewrite the promise as if spoken by the buyer: “I need a way to…”
Replace “creators” with a tighter group: “solo Notion template sellers”, “local plumbers”, “parents teaching pocket money”.
Outline the product on one page. If it needs twelve modules to make sense, shrink the promise.
Define the first useful action the buyer can complete within ten minutes.
Choose the format: checklist, scripts, workbook, mini ebook, calculator, template pack, or SVG cards. Explain why.
Write what the product does not include so buyers do not expect consulting.
Mark which parts can be reused weekly by the buyer. Reusability increases value.
Write three proof points the product can truthfully claim without screenshots, testimonials, or income claims.
Write five titles. Delete any title that could belong to fifty other products.
List every file the buyer receives. Remove anything decorative that does not help the promised outcome.
Create a tiny sample. If the sample is hard to make, the full product will sprawl.
Write the five buyer objections. Answer them inside the product, not just the listing.
Name the minimum price that respects the production effort and buyer value. If it feels too high, improve specificity.
Write the digital-item support note before launch. Clear boundaries reduce anxiety.
Circle anything that will expire in ninety days. Replace it or label it.
If using factual claims, identify sources needed. If you cannot verify, remove the claim.
Search your own catalogue for similar titles and promises. Differentiate before publishing.
Plan five gallery slides: promise, contents, workflow, example page, buyer outcome.
Choose a preview that proves usefulness without giving away the full product.
Estimate build time for a credible v1. If over four hours, reduce scope.
Define the checks: links, filenames, ZIP structure, preview route, shop route, metadata.
Name one place the buyer already spends attention. Internal listing only here; this informs copy.
Compress the promise to twelve words. If impossible, the offer is muddy.
Decide whether the buyer is beginner, intermediate, or advanced. Do not write for all three.
Before evidence gathering, write what result means build, pause, or kill.
Describe how your product differs by buyer, workflow, tone, or deliverable, without attacking others.
List likely customer questions. Add answers to the quick-start if repeated.
Name two future products that could bundle with this one. If none, the niche may still be okay.
Write exactly how the buyer uses it across one week.
Remove manipulative scarcity, fake urgency, income promises, or scraped content.
Write the sentence you would use to explain the product to one real buyer.
If you reject the idea, write why. The archive protects your future focus.
| Field | Notes |
|---|---|
| Product idea | |
| Buyer | |
| Pain sentence | |
| Tiny test chosen | |
| Evidence found | |
| Decision | Build / Pause / Kill |
| Next action | |
| Date | |
Give each filter a score from 0–2: painful problem, reachable buyer, compact deliverable, repeatable promise. Build at 7–8, pause at 5–6, kill or reshape at 0–4. Never use the score as a substitute for judgement; use it to make judgement visible.
A product decision is not a personality test. It is a reversible business choice. Run the small test, write the decision, and keep moving.