Treat the score as a starting point
Understand the rubric and its assumptions. A high score is a reason to investigate, not proof of demand or an uncontested market.
Investigate the buyer’s work
Find the recurring task, its cost, and the person who can authorize a change. Use real evidence to challenge the candidate description.
Test the scenario
Vary price, delivery effort, recurring costs, and adoption. Label assumptions and estimates so an attractive spreadsheet does not become a promise.
Define the smallest proof
Choose an observable pilot outcome and a clear stopping condition. Preserve the evidence even if the candidate is rejected.
A concrete starting point.
A promising service candidate may be rejected after a pilot shows that delivery effort exceeds the assumed price. That is a useful result, not a failed scoring tool.
Your working checklist.
Mark what you have considered. This checklist stays on this page and is cleared when you reload.
Explore the related work.
General engineering guidance, not a certification, service agreement, or product-specific acceptance report.
Back to all field notes ↗