The decision
A demand scorecard is a way to compare evidence, not a machine that predicts revenue. Use a small scale with explicit meanings: zero for an assumption, one for a concrete example, and two for repeated evidence. The weakest criterion often tells you what to test next more clearly than the total score does.
A worked example
The agency-update idea scores strongly on frequency and existing effort, but weakly on purchasing and data permission. A total of ten out of fourteen can look encouraging while the two most important uncertainties remain unresolved. The next step is a permissioned manual result and a specific payment conversation, not a wider feature set.
How to put it into practice
- Score recurring problem, workaround, reachable buyers, budget owner, small deliverable, data permission, and measurable result.
- Attach a note or artifact to each score. If you cannot explain the score, lower it.
- Keep dates with evidence. A workaround observed last year may no longer describe the current workflow.
- Use low scores to select one experiment with an observable outcome.
A failure to plan for
Adding weights can create false precision. Unless you have historical results that justify the weights, keep the score transparent and discuss the evidence directly. Two independent risks are not made safe by averaging them.
Try it on your project
Use the free scorecard on this site. Identify your lowest two scores and write one action for each. After the experiment, update only the scores supported by new evidence; leave the others unchanged.
Keep the next step small
Use the free demand scorecard or planning tools to make your assumptions explicit. The $19 launch kit brings the blueprint and seven editable worksheets together.