Tiny Offer Decision Engine — 31 Fast Filters for Choosing Digital Product Ideas
A practical mini-ebook for solo creators who keep collecting ideas but struggle to choose the next product to finish.
Use it: score 3–7 ideas, choose the strongest small version, and avoid vague products that become too large to ship.
The complete ebook
# Tiny Offer Decision Engine — 31 Fast Filters for Choosing Digital Product Ideas A practical mini-ebook for solo creators who keep collecting ideas but struggle to choose the next product to finish. This is not a trend report, income promise, or magic validation system. It is a calm decision tool: 31 fast filters, scored in plain language, for picking digital product ideas that are small enough to ship and useful enough to sell. ## How to use this ebook 1. Write down 3–7 product ideas. 2. Run each idea through the filters below. 3. Mark each filter: **Green**, **Yellow**, or **Red**. 4. Choose the idea with the strongest green pattern and the fewest expensive unknowns. 5. Cut the first version until it can be completed in one focused build cycle. ### Simple scoring - **Green = 2 points**: clear, useful, low-friction. - **Yellow = 1 point**: promising but needs a tighter decision. - **Red = 0 points**: risky, vague, expensive, or dependent on luck. A good small product usually scores **44+ out of 62** and has no more than three red filters.
## The 31 fast filters ### 1. Pain is already named Can the buyer describe the problem in their own words without you teaching them the vocabulary first? - Green: they already say things like “I need a checklist for…” or “I keep forgetting…” - Yellow: the pain exists but the wording is fuzzy. - Red: you need a long explanation before they understand why it matters. ### 2. Buyer can use it today Does the product create a result in the buyer’s current situation? - Green: no special software, team, or perfect conditions required. - Yellow: useful, but only after some setup. - Red: requires a future version of their life or business. ### 3. Outcome fits one sentence Can you finish this sentence cleanly: “After using this, the buyer can…”? - Green: one concrete outcome. - Yellow: two or three outcomes fighting each other. - Red: vague improvement language such as “transform your productivity.” ### 4. Small enough to finish Can version one be finished without turning into a course, app, or full business system? - Green: ebook, template, checklist, calculator, mini app, or swipe file. - Yellow: could be small if scoped aggressively. - Red: only valuable if huge. ### 5. Clear before-and-after Would a buyer know what changed after 20 minutes with the product? - Green: they leave with a decision, script, plan, worksheet, or setup. - Yellow: they learn something but the output is less visible. - Red: mostly inspiration. ### 6. Avoids regulated advice Does the product avoid giving medical, legal, financial, or safety-critical instructions unless professionally sourced and disclaimed? - Green: practical education with clear limits. - Yellow: adjacent to regulated areas but can be framed safely. - Red: depends on personalised professional advice. ### 7. Buyer already pays for similar help Is there evidence people pay for templates, books, workshops, software, or services around this problem? - Green: yes, adjacent products are common. - Yellow: free content is common, paid products are mixed. - Red: no visible spending behaviour. ### 8. Not a commodity clone Can the product have a specific angle beyond “another planner” or “another prompt pack”? - Green: niche, situation, buyer, or workflow is specific. - Yellow: angle exists but title still sounds generic. - Red: interchangeable with thousands of existing products. ### 9. Demo is easy Can you show the value in five gallery images or a short preview? - Green: visual structure is obvious. - Yellow: needs careful explanation. - Red: value is hidden until after a long read. ### 10. Delivery is simple Can the buyer receive the product as PDF, HTML, Markdown, spreadsheet, SVG, or ZIP without account setup? - Green: instant download works. - Yellow: requires one common free tool. - Red: needs logins, integrations, or manual onboarding. ### 11. Support risk is low Will customers understand what they bought and how to open it? - Green: quick-start guide solves most issues. - Yellow: some support likely. - Red: many edge cases or technical dependencies. ### 12. Ethical promise Can you sell it without exaggerating outcomes? - Green: promises a tool, process, or decision aid. - Yellow: marketing needs careful wording. - Red: depends on unrealistic guarantees. ### 13. Repeatable structure Can the same product format become a series later? - Green: yes, niche editions or companion tools are natural. - Yellow: maybe, but not obvious. - Red: one-off with no adjacent path. ### 14. Specific buyer label Can you name the buyer without saying “everyone”? - Green: “solo Etsy sellers”, “new tutors”, “parents of 7–10 year olds”. - Yellow: broad but still identifiable. - Red: general adults, creators, businesses, humans. ### 15. Buyer urgency Would the buyer care this week, not someday? - Green: tied to a task, deadline, recurring pain, or decision. - Yellow: useful but not urgent. - Red: nice-to-have someday. ### 16. Low copyright risk Can you make it fully original without relying on another brand’s style, text, screenshots, or data? - Green: original frameworks and examples. - Yellow: needs citation or careful abstraction. - Red: value depends on copied material. ### 17. Price feels natural Would a simple price between £5 and £19 feel reasonable for the result? - Green: yes, saves time or reduces confusion. - Yellow: value needs a bundle or stronger proof. - Red: buyer expects it free. ### 18. Title contains the job Does the title tell the buyer what job the product does? - Green: job is visible in the title. - Yellow: subtitle explains it. - Red: clever but unclear. ### 19. First page delivers Can the first page give a buyer something useful immediately? - Green: a checklist, map, scorecard, or decision rule appears early. - Yellow: short intro required. - Red: long theory before usefulness. ### 20. Works offline Can it still help if the buyer saves it locally and disconnects? - Green: fully offline. - Yellow: mostly offline with optional links. - Red: relies on live services. ### 21. No fragile timing Will it stay useful beyond this month? - Green: evergreen method. - Yellow: partly trend-based but refreshable. - Red: obsolete quickly. ### 22. Clear exclusions Can you say what the product does not include? - Green: boundaries are simple. - Yellow: exclusions need careful wording. - Red: buyers may assume too much. ### 23. Build assets are manageable Can you create all buyer files, listing copy, gallery slides, and QA notes in one production pass? - Green: yes. - Yellow: possible with tight scope. - Red: too many moving parts. ### 24. One buyer action After downloading, is there one obvious next action? - Green: fill the scorecard, run the script, print the cards. - Yellow: several possible starts. - Red: buyer must design their own workflow. ### 25. Strong sample use case Can you include one believable example that proves the framework? - Green: example is easy and specific. - Yellow: example needs more detail. - Red: example feels invented or generic. ### 26. Search phrase exists Can you imagine a buyer searching for the thing in normal words? - Green: “digital product ideas checklist”, “quote follow-up scripts”. - Yellow: phrase is niche but plausible. - Red: no obvious search language. ### 27. Complements the shop Does it fit the shop’s existing promise and audience? - Green: strengthens the shop category. - Yellow: acceptable but not central. - Red: confusing beside other products. ### 28. Easy refund/support note Can the support policy be honest and simple? - Green: digital file access support; no physical shipping; no outcome guarantee. - Yellow: needs special caveats. - Red: likely disputes about expectations. ### 29. Upgrade path exists Could a future version add worksheets, templates, examples, translations, or a mini-app? - Green: natural upgrade path. - Yellow: maybe. - Red: no meaningful extension. ### 30. Founder energy Would you still be willing to improve this after the first sale? - Green: yes, the topic is useful and expandable. - Yellow: maybe if it sells. - Red: you are already bored. ### 31. Decision confidence After scoring, do you know whether to build, shrink, park, or kill the idea? - Green: clear action. - Yellow: one more check needed. - Red: still foggy.
## One-page scorecard Copy this for each idea: ```text Idea: Buyer: One-sentence outcome: Delivery format: Price range: Green filters: Yellow filters: Red filters: Total score out of 62: Decision: Build / Shrink / Park / Kill First version cut: Next action today: ``` ## Worked example Idea: “A 20-page planner for small bakery Instagram marketing.” - Buyer: owner-operated bakery with limited time. - Outcome: choose and schedule one week of low-effort posts. - Delivery: printable planner + caption prompts. - Strong filters: specific buyer, visible demo, one action, evergreen, low support. - Weak filters: crowded market, title needs differentiation. - Decision: **Shrink and sharpen** into “Quiet Week Bakery Marketing Map — 14 low-effort posts for owner-operated bakeries.” The improved idea has a clearer buyer, clearer use case, and stronger gallery potential. ## Build / shrink / park / kill rules - **Build**: 44+ points, no severe red flags, first version is small. - **Shrink**: promising but too broad. Cut audience, outcome, or format. - **Park**: useful but poor timing, weak evidence, or support-heavy. - **Kill**: unclear buyer, weak pain, high legal/copyright risk, or huge scope. ## Final note The best small product is rarely the biggest idea. It is the idea with the cleanest buyer, the clearest first result, and the fewest hidden obligations.