The sample scored 5 out of 5 on the problem and 1 on who pays. When page three opens on Pro or Max, these five scores come first, each from what we read and each with what would move it.
Fig. 1 · What it looks like on the sample read
On the sample read the grid came back like this. Each score is the level that share reaches on the scale, from 0 to 5, and every row has one.
| Question | Share | Counted | Score |
|---|---|---|---|
| Problem | 47% | 101 of 212 posts on topic | 5 |
| Sufferer | 31% | 32 of 101 people found are toddler parents | 2 |
| Solution | 33% | 2 of 6 sellers' printed prices reach $5 | 3 |
| Buyer | 5.9% | 6 of 101 people found name a fix they pay for | 1 |
| Distribution | 16% | 1 of 6 builders' reports on the parent forums name a paying customer | 2 |
The section names who pays as the weakest of the five. Its reason is that 6 of the 101 people found name a fix they pay for, all of them food they buy, and none of them pays for a planning tool. The lines under the grid carry their sources. One of them, sourced from three posts on page two, reads "Parents describe repeating dinners and struggling to plan around accepted foods."
Under every row sits what would move it. For who pays, the sample says the row would rise with a customer focus on parents already using paid planning fixes, if those parents form a larger share of the people found.
Fig. 2 · How each question is scored
Each question is measured as a share, a count out of what we read. The section turns the share into a level on a scale written down before page three ran, and that step is plain arithmetic. When we read too little to measure a question, it gets no score, and the row says how many it needs. How we judge shows the scale, the two ends of each question and the least we need to read for each.
The counts come from the sections before this one. Problem and Sufferer are counted from the people on page two. Solution compares your price with the prices in who already sells it. Buyer counts who among those people already pays for a fix, and Distribution counts builders' reports from where those people are.
Fig. 3 · What would make us say no
When page three starts, we write one line from your confirmed story that says what would make us say no, and we freeze it before anything is scored. This section counts what we read against that line and says whether it was met, not met, or couldn't be counted from what we read. On the sample, the line couldn't be counted, so the sample doesn't enter how often we say no.
Fig. 4 · What "no score" and "would move it" mean here
A row with no score means we read too little to measure it. Every row on the sample has a score. Distribution is scored on the parent forums of What to Expect and BabyCenter, the third place in the ranking, because they're the first place in it the shared set of builders' reports can answer for. 1 of the 6 reports on them names a paying customer.
Each "would move it" carries a weight. A light one means we found too little, and reading more could settle it. A heavy one means what we found points the other way.
Fig. 5 · Which plan runs it, and what would change it
Pro and Max run it, once who pays, the other side and where they are have run. It runs again whenever any section before it runs again, and a change of price runs it directly (Iterating). Once it's done, the rehearsal of your price and the next steps build on it.