Launch pages in hours, not sprints

A partner signs on Thursday. The joint announcement goes out Tuesday morning, and it needs a landing page: logo lockup, what the partnership means for customers, a proof point, a form. On most startup marketing sites, this is where the trouble starts. The page is a dev ticket, the ticket goes into a sprint, and the sprint ends after the news cycle does. Or it's an agency request, which in the quotes our clients show us means a kickoff and two to three weeks. The announcement ships as a blog post with no call to action, and everyone quietly agrees the website is a bottleneck.

We think marketing velocity is a property of the website. Heroics and headcount don't produce it; the way the site is built does. Built one way, a landing page is an afternoon. Built the other way, it's a project.

Pages as composition, not construction

The architecture that makes the difference: every page is a typed document, an ordered list of sections drawn from a library the site already has. Hero, feature grid, pricing table, FAQ, testimonial and proof blocks, call-to-action band. Each section has a schema: these fields, these shapes, these constraints. Building the partnership page means choosing six sections and writing the copy that fills them. No new components, no new CSS, no deploy.

This is the same idea Nielsen Norman Group describes in Design Systems 101: a set of standards for managing design at scale with reusable components and patterns. Applied to a marketing site, it changes what a landing page is. With no code in it, it stops being engineering work and becomes an editorial act. The marketer who knows what the page should say is the person who ships it. On the sites we run, the realistic time from “we need a page” to “the page is live” is two to four hours, and most of that is writing copy, which you'd have to do anyway.

Why fast doesn't mean sloppy

Speed without guardrails just produces broken pages faster. Three properties make composition safe at speed:

• Schema validation. Every page is checked against the section schemas before it ships, the same way a JSON Schema validator checks a document against declared structure and constraints. A pricing table missing a tier name, a hero pointing at a dead image, a FAQ item with no answer: rejected at save time, not discovered by a prospect. A malformed page structurally cannot go live.
• Versioning. Every publish is an immutable revision. That removes the QA paralysis that makes teams slow: you don't need a three-person review to ship a page when reverting it is one click. The cost of a mistake drops from “incident” to “undo,” and shipping speed follows the cost of mistakes.
• Design tokens. Sections consume the brand's colors, type scale and spacing from one source. Tokens are mature enough to have a stable shared format: the W3C Design Tokens Community Group published its Design Tokens Format Module in October 2025. Because the section library carries the brand, there is no way to compose an off-brand page, and nobody has to review each page for visual consistency.

The pages you'd actually ship this quarter

Concretely, the pages this makes cheap are the ones growth teams keep not shipping:

• The partnership announcement that has to be live while the news is news. The window is measured in days; a sprint doesn't fit inside it.
• The pricing experiment. One campaign's traffic goes to a variant page with different packaging or an annual-only offer. It runs for three weeks and disappears. Nobody builds this if the page costs $5,000, because the experiment isn't worth that. At two hours, it obviously is.
• Vertical and localized variants. The services page recomposed for dentists, then for law firms; the same page in German for the DACH campaign. Same sections, different copy and proof, so ten variants become an editorial batch job instead of ten tickets. For the language versions, add hreflang annotations so Google treats them as localized variations of one page.

Why the agency quote runs to thousands, and when you don't need this

The typical quote for “one landing page” (several thousand dollars, two to three weeks) isn't gouging. On a site built from page builders, hand-built templates or WordPress plus plugins, every new page really is bespoke: custom markup, custom responsive behavior, a real chance of breaking something adjacent, a round of cross-browser QA. The price reflects genuine risk. Composition doesn't make agencies cheaper; it removes the reason the work was expensive.

The honest caveat: this only pays if you actually run campaigns. If your site changes quarterly (a copy tweak, a new team member, an annual pricing update) you need reliable maintenance more than composition speed, and investing in a section library would be over-engineering. The test is a number: count the pages marketing wanted in the last six months against the pages that shipped. If the gap is zero, keep what you have. If marketing has stopped asking because they already know the answer, the architecture is the bottleneck, and process changes won't fix it.

The sites we build and manage work this way, with a typed section library, validated pages and one-click reverts, and the retainer is what keeps a two-hour landing page an actual two hours, month after month.

Sources

• Design Systems 101, Nielsen Norman Group
• Design Tokens Format Module 2025.10, W3C Design Tokens Community Group
• What is JSON Schema?, JSON Schema
• Localized versions of your pages, Google Search Central