Build and QA customized campaigns from proven templates.
Set up the campaign and its offers in the Campaigns App, then paste the start prompt from campaigns.nextcommerce.com/start into your coding agent.
Have a saved Map? Open it in the Workspace
Every template family is a runtime contract — pages, slots, and cart wiring the Campaigns SDK understands. Pick the one shaped like your offer.
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.
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.
Every artifact is machine-readable — CampaignSpec, Build Packet, QA verdict. Agents consume the same contracts you review.
llms.txt points your agent at the start path, templates, patterns, tracking path, and toolkit — it can learn the system without a walkthrough.
Every CampaignSpec is validated against the schema — products, prices, and page wiring.
Every page renders in a real browser, and SDK events carry campaign and session identity for attribution.
QA places one test order on every planned path — card entry, upsells, receipt — with a test card, up to six by default.
When a campaign passes, you get a handoff packet — not a promise.
Set up the campaign and its offers in the Campaigns App, then paste the start prompt from campaigns.nextcommerce.com/start into your coding agent.
Have a saved Map? Open it in the Workspace