A separate content type from features. Each system has a one-line promise, the thing it replaces, and an ordered set of beats — each with a kicker, a headline, the body, the alternative it beats, a named scene to draw, and the feature pages it links to. Systems appear in the sitemap and llms.txt above individual features.
Also called: how it all fits together · end to end · system pages · workflow story
- 1Each system defines its beats in order; the page tells them as a scroll.
- 2Every beat names the alternative it improves on, which is the contrast the page is built around.
- 3Beats link out to the feature pages for detail — platform, then system, then feature.
- 4A feature page only offers a system link when a narrative actually exists for it.
- 5Systems are given higher sitemap priority than individual features.
The reasoning is stated in the systems module: "Some of what this platform does cannot be explained one feature at a time. The live estimate is not a feature; it is a single link that becomes four different documents over the life of a job, and the value is in the becoming. Listed as parts — '3D viewer', 'colour picker', 'intake form', 'e-signature' — it reads like a checklist any competitor could match. Told as a sequence, it is the thing nobody else does." And the truth constraint: "The beats below follow the REAL section list… Nothing here describes a screen that does not exist."
- Sequenced value reads as a commodity checklist when listed as parts.
- There was no page explaining how the pieces connect end to end.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →