Book a scoping call
Home / Work / This Site and Its Quoting Engine
Business software Betr internalIn production

This Site and Its Quoting Engine

842 pages, a plain-English quoting engine, and a validator that fails the build on thin content.

What we set out to build

A sales surface that closes before the call: publish the prices, publish the licences, argue the other side of every comparison, and let anyone price their own job without talking to us.

What was built

  • 198 productised builds, each with a solution page and a long-form write-up
  • 9,594 community workflows grounded into the quoting engine, with 95 integration guides and 180 connection pages generated from live data
  • A plain-English engine where a language model selects the builds and deterministic code produces every number
  • An instant scope builder, a free compliance self-check tool, and honest comparison pages
  • A validator that fails the build on broken links, duplicate metadata, missing schema or thin pages

What it achieves

  • 842 pages with zero validation errors and zero warnings
  • 73 engine tests, including one that fails the build if the response schema ever asks the model for a price
  • Unknown scope is quoted as a labelled allowance plus a discovery fee, so a client budgets for what nobody costed
The hard part: Making an AI quoting engine that cannot invent a price. The model reasons about which builds fit; the code does every calculation. That separation is enforced by a test, not by convention.

The stack

Python, no framework, Claude, static generation.

Common questions

How was this built?

This one is ours: internal tooling built for the studio itself rather than a venture with a founder. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.

What state is it in?

In production. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.

Can you build something like this for us?

That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.

Where to next

If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.

[ // / BUSINESS SOFTWARE ]

Other business software work

Built with the same discipline, in the same domain.

Want something like this built?

The catalogue prices the patterns behind this work. Describe your version and the engine will scope it, including an allowance for anything nobody has costed.