method candidate goes to: this-edition V villager
Count what matters: created, customised, used, and the minutes it cost the other side; set the stop rule first
For an early access programme the numbers are: how many were created, how many customised, how many used, how many runs; a thing created and never customised is a download, customised and never used is a document, and the commercial value is in the third number. Add corrections received, the strongest sign someone read it, and the minutes each step cost the person on the other side and where they stopped. Every stop is a product change to make, not a reason the customer gave. Set the stop rule before the first message goes out: if, after the first twenty, fewer than a handful ran it and sent a correction, the programme stops and the drawing board starts.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Note. In the article the counts are RiskMandate's (Agent Behaviour Policies created, customised, used, scenarios run); the book generalises the shape. The programme records timestamps and steps only, no message content.
Where it comes from
- Price it, then give it away What we count; For the agents running this, steps 3 to 6 (newsroom)
What it answers in the 2018 book
- Facts answered outline, Concepts
Where it goes
Chapter Your first price and your first ten customers, part Hands on, 2026 (drafting); topic Be a founder (or a one-person service).
Other ideas proposed for the same chapter: Do not make them apply: 'we have twenty, would you like one, or shall I give it to someone else'.
Node idea:count-created-customised-used in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.