A Lightweight Qualifier
Tiny Tool
Idea
Scorecard.
Pressure-test one tiny online tool idea in a few minutes — before you spend time building it.
The ScorecardHow to Use
Positioning
Score the idea
before you build it.
Before we tell someone what to build, we make them ask better questions. This scorecard is the ten-minute pressure test — one idea, ten criteria, a total out of fifty, and a clear next action.
How to Use It
- Choose ONE idea. Do not score several ideas at the same time.
- Write the idea in one sentence: “A [tool type] that helps [specific user] do [one useful job].”
- Score each of the 10 criteria from 1 to 5 using the anchors below.
- Add the scores for a total out of 50.
- Use the result band to decide the next action. Do not interpret a high score as proof of demand.
The Frame
A strong score means “this idea is clear enough to deserve a real validation test.” It does not mean demand is proven. Clarity is a permission slip to test — not a shortcut past testing.
The ScorecardIdea Snapshot
Step 1
Idea snapshot.
Write it down before you score it. If the sentence is hard to finish, that is already a signal — the criteria on the next pages will tell you where the idea needs sharpening.
The 10 Questions and Scoring Anchors
Score each criterion from 1 to 5 using the anchors on the next pages. Score honestly — an inflated score just wastes a real test later. Your criterion scores auto-tally into the Score Summary on page 8.
Criteria 01 — 03Step 2 · Score
Can you describe the problem in one sentence?
1
The problem is vague or mixed with several problems.
2
I can partly describe it, but it still needs explanation.
3
The problem is understandable but still broad.
4
The problem is clear and narrow.
5
The problem is specific enough that another person would immediately understand the job to be solved.
Can you name the specific person who has it?
1
The user is basically ‘everyone’.
2
I have a broad audience category only.
3
I can name a likely user group.
4
I can name a clear user group and situation.
5
I can name a specific user, context, and why this problem matters to them.
Criterion 03Step 2 · Score
Does the problem repeat or become meaningfully urgent?
1
It is rare and not particularly important when it happens.
2
It happens occasionally with low urgency.
3
It happens often enough to notice or becomes important in some situations.
4
It repeats regularly or is clearly urgent when it occurs.
5
It repeats frequently, is costly/annoying when ignored, or becomes highly urgent at the moment of need.
Is the current workaround slow, annoying, error-prone, or inconvenient?
1
The current way is already easy.
2
The workaround causes only minor inconvenience.
3
There is noticeable friction, but people can tolerate it.
4
The workaround wastes time, causes errors, or needs repeated effort.
5
The workaround is clearly painful enough that a simpler tool would feel immediately useful.
Criteria 05 — 06Step 2 · Score
Does a tiny utility clearly improve the task?
1
A tool does not obviously help.
2
The tool idea feels forced.
3
A tool could help, but the format is not obvious.
4
A specific utility format clearly improves the task.
5
The problem naturally maps to a generator, calculator, checker, QR/barcode utility, form, converter, graph, or similarly focused tool.
Can the user provide the necessary input without a long setup?
1
The tool needs complex setup, accounts, files, or lots of information.
2
The user must provide many inputs before anything useful happens.
3
The input is manageable but could be simplified.
4
The user can provide the essential input quickly.
5
The tool needs only a few obvious inputs and the user can start almost immediately.
Criteria 07 — 08Step 2 · Score
Is the result immediately useful?
1
The output is mostly decorative or unclear.
2
The result has limited practical value.
3
The result is useful in some cases.
4
The result clearly helps the user complete a task or make a decision.
5
The user gets an immediate answer, file, code, chart, recommendation, calculation, or transformation they can use right away.
Can version one work without accounts, dashboards, or many features?
1
Version one already requires a complex product.
2
Several heavy features feel necessary.
3
A small version is possible, but still has unnecessary complexity.
4
A useful first version can be built with limited features.
5
The first version can be one page, one main action, and one useful output with minimal infrastructure.
Criteria 09 — 10Step 2 · Score
Can you test interest before fully building it?
1
I do not know how I would test it.
2
Testing would require building most of the tool first.
3
I can think of one rough validation route.
4
I can test the problem or concept cheaply before a full build.
5
I can name a specific low-cost test using audience questions, search behavior, Pins, a mockup, waitlist, manual version, or similar evidence.
If people use it, is there a sensible next value or monetization path?
1
There is no obvious reason for the tool to exist beyond the novelty.
2
Possible value is speculative and disconnected from the user.
3
There may be a useful follow-on path, but it is not clear yet.
4
There is at least one realistic follow-on value path.
5
There is a clear fit with a relevant next step such as a digital product, newsletter, affiliate resource, lead, sponsorship, paid feature, or advertising once usage exists.
The ScorecardScore Summary
Step 3
Score summary.
Your scores from the previous pages tally here automatically. Update any number and the total recalculates. Then take the total to the result bands on the next page.
Reminder. A high total means the idea is clear enough to deserve a real validation test — not that demand is proven. Use the total to pick a next action on the following page.
The ScorecardResult Bands & Next Action
Step 4
Result bands
& next action.
Match your total to a band and take the described next action. The bands are not verdicts on your idea — they are prescriptions for the smallest next move.
Strong candidate
Run a real validation test. Choose one cheap test that can produce evidence. Do not treat the score as proof of demand.
Promising but unclear
Circle the two lowest-scoring criteria. Narrow or simplify the idea, then score it again before building.
Too fuzzy or too heavy
Change the user, problem, or tool format. Your goal is not to rescue every idea; it is to make the useful job clearer and smaller.
Park it for now
Move the idea to an idea bank and look for a clearer repeated problem. Parking it protects your time.
The ScorecardThe Final Question
Step 5
The final question.
Whatever your total, the next step is the same shape: pick the cheapest useful test that could produce real evidence — a Pin, a landing page, an audience question, a manual version, a comparison post, a waitlist, or a clickable mockup.
Your Commitment
My next test.
What is the cheapest useful test you can run before building the full tool?
Write it here
Before you close the file. A strong score means “this idea is clear enough to deserve a real validation test.” It does not mean demand is proven. Clarity is a permission slip to test — not a shortcut past testing.
End of the Scorecard
Ask better. Build smaller.
Tiny Tools
Better questions before you build.