The Catalog Is Open: Every Blue Horizon Labs Price, Published

Today the lab listed everything it sells. Not a services page with a "contact us for pricing" button — a ladder, with a number on every rung, and a test that fails the build if a number is typed anywhere the registry did not put it.

This is a build log, so here is what was built, what was decided, and what was deliberately left out.

What went up

The Web Factory page is the whole website service line in one place: a fixed-fee diagnostic, three build tiers, a search sprint and two search retainers, and a month-to-month care plan. Eight packages. Every one carries a price — a fixed fee where the scope is fixed, a floor where the written scope from the diagnostic sets the exact figure — and every one carries the record of who ratified that price and when.

Three of them have been on the services page since September. The other five existed as decided prices in the lab's catalog and nowhere a buyer could see them. That gap is the thing this log closes.

The home page now has a catalog band with three doors — the Web Factory, the fixed-fee packages, and the multi-week engagements with their published floors — and the machine-readable surfaces caught up with the human ones: the page emits an offer catalog that an answer engine can read as one list, and the plain-text files crawlers prefer carry the same figures and the same terms, verbatim.

What was decided

The prices themselves were not decided today. They were ratified on 2026-09-02, with the service line, and recorded then. What changed today is a sequencing decision: the original plan published the line only after the build template had been extracted into its own repository. The owner reversed that order. The template is the site you are reading — the same static export, the same edge deployment, the same gate — and a price you have decided but will not publish is, as the service-line case study put it, a price you have not decided.

So the ladder went up on the reference build, with the reference build named as such.

What was left out, on purpose

Two kinds of thing are missing from the catalog, and both are missing deliberately.

The first is any package whose price the owner has not signed. The registry holds a few of those. They render nowhere, resolve to nothing from a link, and are kept off this page by the same test that keeps a typo out of a published fee. When one is ratified, listing it is a two-line change and a re-pinned test.

The second is the bundle — a site delivered as the front door of a Notion operating system, leads flowing into the CRM. It is real, it is quoted, and it has no published figure yet, because no pilot has priced it. Publishing a floor for it would be publishing a guess.

What happens next

The first paid builds on the ladder get instrumented: the time and the model cost per stage, logged, so the floors on the page are backed by actuals rather than by the benchmark bands they were set against. When that data exists, it gets published here, including the parts that argue for moving a number.

Until then, the prices are on the page, and the page is the offer.