Growth & Digital/Offers — scope
EDIT VIA GITHUB · /content
Single page05 · Start

Offers

Chapter 05 anchor — offers worth asking for, replacing "book a meeting" with promises sales fulfills.

DESIGN v1.1 LANDED AUG 31 — this scope page was written against v1; verify against the new snapshot before relying on component details.
LAYOUT MOCK — STRUCTURE ONLY
Offers layout mock
Click the mock to open the live template in the design directory (new tab).
TEMPLATE SCOPE
edit content/templates/offers.md

What this page does

Anchors the offer motion. The hub presents four offers that are worth trading contact details for — a free corporate MCP (download it, use it in Claude Desktop/Cursor/LangGraph, all five platform products as tools), an AI architecture review by the people who build the layer, a tailored cloud migration plan (current vs proposed in numbers, migration order, cutover support), and a structured enterprise trial. Each card routes to an offer page whose spec lives in the website brief's Phase 02; each offer is a promise with a locked fulfillment owner before launch.

Components on it

  • Offer hub hero — the "offers worth asking for" frame.
  • Four offer cards — MCP · Advisory · Migration Plan · Enterprise Trial, each with the concrete deliverable named.
  • Per-offer pages — promise hero, show-it block, what-you-get list, intake, fulfillment strip (see the Phase 02 mocks in the brief).
  • Proof-of-usefulness blocks — example agent configs, recipes, deliverable samples — the offer shown, not described.
  • Fulfillment strip — who delivers, on what SLA (gates on Decision 03 owner lock).
  • Routing — intake feeds the scored-account motion, agentic offers gated on the product roadmap with Jon.

What this page does

Anchors the offer motion. The hub presents four offers that are worth trading contact details for — a free corporate MCP (download it, use it in Claude Desktop/Cursor/LangGraph, all five platform products as tools), an AI architecture review by the people who build the layer, a tailored cloud migration plan (current vs proposed in numbers, migration order, cutover support), and a structured enterprise trial. Each card routes to an offer page whose spec lives in the website brief's Phase 02; each offer is a promise with a locked fulfillment owner before launch.

Components on it

  • Offer hub hero — the "offers worth asking for" frame.
  • Four offer cards — MCP · Advisory · Migration Plan · Enterprise Trial, each with the concrete deliverable named.
  • Per-offer pages — promise hero, show-it block, what-you-get list, intake, fulfillment strip (see the Phase 02 mocks in the brief).
  • Proof-of-usefulness blocks — example agent configs, recipes, deliverable samples — the offer shown, not described.
  • Fulfillment strip — who delivers, on what SLA (gates on Decision 03 owner lock).
  • Routing — intake feeds the scored-account motion, agentic offers gated on the product roadmap with Jon.
CLASS
Single page
CHAPTER
05 · Start
RENDERS
5 pages — the offer hub + 4 offer pages (Phase 02 experiences)
PAGES ON THIS TEMPLATE
Offers hubFree Redis Corporate MCPAI Architecture AdvisoryCloud Migration PlanEnterprise Product Trial
SPEC OWNER
Website build program