/ work / the-comparison-table
The comparison table
5 of 6 units done. Features down the left, five columns across — free, £10, £50, £500, £1,500. The page that makes the differences between the levels legible, and the one that finally explains the entry price, because a licence is only a difference next to a column that does not have it.
This workstream came out of a memo. One table, five columns, and the free one first, 2026-09-16 — kept verbatim, read into a brief, and broken into the units below.
Queued0
—
Up Next1
Deliberately kept off the comparison table until it is decided. Email support on the paid levels was floated in the memo and never scoped. What is true today and could be said instead: every purchase is managed directly by the person who does the work. That is stronger than a support tier and it is also a different promise, so it needs saying on purpose rather than by default.
The project lead, in conversation · memo 2026-09-16In Progress0
—
Done5
Answered by building it the other way round. A row goes on the table only when each of its five cells can be pointed at — a price in data/offers.yml, a gets sentence, a not-promised line, or a ruling. A row whose cells would be a promise is not on the table at all. Fourteen rows qualified.
The project lead, in conversation · memo 2026-09-16Shipped in v0.2.8 as data/comparison.yml. Fourteen rows in four groups, each carrying the sentence that says what the reader is actually buying.
memo 2026-09-16Settled by reading what the level already says. £10 is explicitly not a vault — its own page has said so since it was written — and £50 is where a vault starts. It was never a proposal; it was already true.
The project lead, in conversation · memo 2026-09-16Shipped in v0.2.8 at /compare/, free column first.
memo 2026-09-16Done. tools/make_pdfs.mjs renders the real page through the real print stylesheet, so nothing is retyped — a row added to data/comparison.yml is in the brochure on the next run. A4 landscape, because five columns and a wide row label do not fit portrait without shrinking the body copy past reading at arm's length. Six sheets: four of table, two of the explanation under it.
It is not in the gate, for the same reason as the walkthrough and the concept screenshots — it needs a browser, and the gate is Python and node --check with nothing installed. So the drift is checked instead: the file still has to hash to what the tool recorded, its version has to be one this site really released, and a copy that lags the current release is a note rather than a failure, with the page printing the version beside the link.