Component gallery

Reusable marketing primitives for consistent buyer pages.

A noindex review surface for the compact primitives used across prospect-facing marketing pages. It stays out of the public buyer path.

Section header

Keep page sections compact, specific, and tied to a buyer question.

Use this header pattern when a section needs context plus one clear action.

Review examples
Owner confidenceOwner-safe decisions, selected proof, and status without operational clutter.Open path

Proof card

Every claim has a reviewed source.

Objection answered: Can buyers trust the claim without seeing private records?

Proof cards combine safe wording, redaction state, permission state, and a route back to the workflow.

public readyredaction completeowner view
See proof
available

Capability tile

Use for compact product capabilities that need status and a short outcome.

Best for platform, pricing, and module routes
Homepage

Hero, who-this-is-for strip, route rail, proof path, and one primary demo CTA.

Examples

Buyer-path filters, result count, reset link, objection groups, proof anchors, and persona-aware booking links.

Demo

Persona-first selection, risk/workflow/proof comparison, and workflow-specific signup handoff.

Solution detail

Buyer question, pain, workflow, proof, and CTA stay in the same order for every persona page.

Signup

Success links reflect persona and intent while restating that production access is not created by the form.

Proof matrix

Use compact persona x workflow x evidence rows when `/examples` needs more orientation without another long card set.

Launch module

Persona detail pages should name the first workflow to launch, proof to inspect, and what not to expect.

Walkthrough helper

Demo pages should help buyers choose by risk, check proof first, and book the path with context preserved.