CREATE NEXT CAMPAIGNS WITH AI

Campaigns OS

Build and QA customized campaigns from proven templates.

Start in the Workspace, choose a funnel flow, wire in your products, preview every page, and ship with validation already baked in.

Open Workspace Browse templates
HOW A CAMPAIGN SHIPS
every step is verified before launch
PATTERN
PDP + checkout + upsell
proven
TEMPLATE
olympus
verified
CAMPAIGNSPEC
v4.3
valid
PREVIEW
3 pages render
no errors
QA
ready with exceptions
2 warnings
BUILD PACKET
ready for handoff
ready
HOW A CAMPAIGN SHIPS
every step is verified before launch
PATTERN
proven
PDP + checkout + upsell
TEMPLATE
verified
olympus
CAMPAIGNSPEC
valid
v4.3
PREVIEW
no errors
3 pages render
QA
2 warnings
ready with exceptions
BUILD PACKET
ready
ready for handoff
STARTER TEMPLATES

Start from a template that already converts.

Every template family is a runtime contract — pages, slots, and cart wiring the Campaigns SDK understands. Pick the one shaped like your offer.

olympus template checkout capture
olympus
Default pick. Single-step, single-product checkout — lowest-friction conversion.
presell · landing · checkout · upsell · receipt
SDK 0.4.25
olympus-mv-single-step template checkout capture
olympus-mv-single-step
Products with variants — color, size, flavor — on a single-step checkout.
landing · checkout · upsell-mv · receipt
SDK 0.4.25
shop-three-step template checkout capture
shop-three-step
Shopify-style split flow — information, shipping, and billing as separate steps.
information · shipping · billing · receipt
SDK 0.4.25
limos template checkout capture
limos
Quantity-tier campaigns — buy 1, 3, or 6 — with a bundle selector on checkout.
presell · landing · checkout · upsell · receipt
SDK 0.4.25
View all 7 template families
PATTERN LIBRARY

Bundle selectors

Bundle cards wired to cart state — pick a bundle, the SDK swaps the cart. You own the markup; the SDK owns the attributes.

pattern demo · SDK 0.4.25 cart $35.98
selection mode: swap · cart state owned by SDK
checkout.html
<div data-next-bundle-selector
     data-next-selection-mode="swap">

  <div data-next-bundle-card
       data-next-bundle-id="duo"
       data-next-bundle-items='[{"packageId":2,"quantity":2}]'
       data-next-selected="true"></div>

  <div data-next-bundle-card
       data-next-bundle-id="triple"
       data-next-bundle-items='[{"packageId":2,"quantity":3}]'></div>

</div>
no JS required · the SDK hydrates the attributes on load
Explore the pattern library
BUILT FOR AGENTS

The build is agentic.

The fastest way through the loop isn’t by hand. Campaigns OS ships agent skills and machine-readable contracts, so an AI agent can scaffold, build, and QA a campaign end to end — you review and launch.

AGENT SKILLS

Five lifecycle skills ship with the public toolkit for Claude and Codex — orchestration, setup, build, polish, and QA — plus agent context for Copilot and Cursor.

install-skills · 5 skills
CONTRACTS

Every artifact is machine-readable — CampaignSpec, Build Packet, QA verdict. Agents consume the same contracts you review.

JSON schemas · versioned
THIS SITE

llms.txt points your agent at the templates, patterns, and toolkit — it can learn the system without a walkthrough.

/llms.txt · published
PROOF

Verified before it takes an order.

SPEC

Every CampaignSpec is validated against the schema — products, prices, and page wiring.

schema v4.3 · valid
RUNTIME

Every page renders in a real browser before review. Broken markup never reaches QA.

3 pages render · no errors
TEST ORDERS

QA places real test orders through the checkout — card entry, upsells, receipt — using global test cards.

4 orders placed · verified

When a campaign passes, you get a handoff packet — not a promise.

START

You came here to ship.

Open the Workspace, load your campaign, and leave with a build that has already been verified.

Open Workspace Start from a template