The pricing page, reborn inside the agent.
Your customers hit plan limits inside Claude and ChatGPT. The Agentic Revenue Card meets them there with the right plan, in your brand and on your own Stripe, and their agent is briefed on every number.
Three sizes. Three different questions.
The card grows with the decision. Each size answers a different question with different data — never the same information scaled up.
Your workspace is at its 5-seat cap.
“What do I do?”
Mid-task walls open small and resolve fast: the block in one line, the recommended plan, the price on the button, and a way to decline. Resolution, not reading.
“Is this right for me?”
The buyer’s own usage, the current→target plan, the reasons it helps, and the honest tradeoff — plus the controls to configure it. A generic pricing page can’t render this; it doesn’t know who’s reading.
Your workspace is at its 5-seat cap.
“What are all my options?”
Every plan and both intervals, side by side in the thread — their current plan marked and the right upgrade highlighted for how they actually use it.
The agent becomes your best sales engineer.
Everything the card is built from — the buyer’s usage, why they’re blocked, the recommendation and the honest tradeoff — flows to the agent, so it answers from their actual numbers instead of guessing. It recommends what unblocks the task, and says so when a bigger plan is overkill.
- Grounded in usage — the agent sees the same seat count, hit history, and entitlement the card does.
- Guides, doesn’t pitch — it recommends what unblocks the work, and flags overkill.
- One source, zero drift — every re-quote updates the card and the agent together.
- Where no card renders, the agent gets the same facts as text: the briefing, the recommended plan and your checkout link.
inside
Claude 
ChatGPT Every customer surface is yours. Now the card is too.
Your brand already runs every surface a customer touches. The Agentic Revenue Card extends it to the moment of highest intent — where your brand earns the most trust.
- Themed from your site — your own Claude reads your pricing page and proposes palette, logo, gradient, and button — nothing ships until you approve.
- Your typeface on the card — subsetted and fast; where a host won’t load it, a clean system face keeps everything else on brand.
- Light and dark, both complete — two full palettes, dark logo included — the card follows your customer’s theme. Flip it yourself.
From on-brand-ish to indistinguishable.
Six capabilities, live on your Agentic Revenue Cards today — preview on any plan, publish on Growth and above. Colours get you close; the typeface makes the card read like your own pricing page.
Themed from your site
Say “theme my card from acme.com.” Your own Claude reads your pricing page first, extracts palette, logo, button shape, gradient, and typeface, and proposes a theme — nothing publishes until you approve.
Edited in the session
Every change is a sentence to your own Claude, with a preview of the themed card on sample data right in the thread. Publish reaches your live cards without a release.
Your brand typeface
Upload a licensed webfont or have your own Claude pull the one on your site — subsetted to the card, regular and bold, tabular figures for prices. Where a host won’t load it, a clean system face steps in with everything else on brand.
A gradient on the button
The upgrade button carries the same two-colour gradient as the button on your own pricing page — while the rest of the card stays on your solid accent.
Light and dark, both complete
The card follows your customer’s host theme and flips live — two full palettes, including a dark logo lockup, not one palette dimmed.
Guardrails on every change
Every colour is contrast-checked before it publishes; a failing shade comes back with the measured contrast and the nearest passing one. Fonts publish only after you confirm the licence.
Themed by asking your own Claude.
One sentence to your own Claude, through the Inception Agents connector: it reads your pricing page, proposes the theme, and previews the card in the thread before anything ships. You approve, it publishes, and live cards update with no release.
- Preview works before you pay — see your brand on the card on any plan.
- A person approves every publish — your own Claude proposes, you decide.
- Seat bounds, legal links, and copy publish the same way, with no redeploy.
Interactive where it helps, rigid where it matters.
The card is built like a payment surface: playful in the controls, uncompromising where money moves.
- Server-signed quotes Amounts come from Stripe’s own invoice preview; any drift refuses the charge before money moves.
- Exact-echo confirmation The charge must match the displayed quote to the cent — zero tolerance.
- Trust chrome always renders The lock, “Secure checkout via Stripe”, the price on the button, and a decline can be recoloured, never removed.
- Terms & Privacy in the chrome Fixed link text, HTTPS-only destinations — the compliance line counsel looks for.
- No dark patterns No fabricated urgency, no hidden tradeoffs. Honesty is the conversion strategy agents reward.
- No personal data in the card Pseudonymous references only; payment details live with Stripe.
- Accessibility built in WCAG-checked theming, keyboard and screen-reader support on every control.
- Interaction analytics included Expand rates, seat changes, interval flips — the funnel data to optimise every card.
Quoted, confirmed, charged — to the cent.
Tap +/− on seats, flip monthly to annual, pick a different plan — the card re-quotes your Stripe on every change, and the button re-labels only from that signed quote. The client never computes a price. The amount the buyer confirms is the amount charged.
Quantity is signed into the quote — an unsigned amount cannot be charged. Re-quotes are free price updates: browsing and reconfiguring never bills anyone. By default the button opens your hosted Stripe checkout. Where a host supports native confirmation, a customer with a saved card can confirm the exact amount in the thread instead, and you choose per host, with one switch that turns it off.
The buyer-facing side of MCP Revenue Orchestration.
The card is where orchestration meets the buyer. Behind it: moment detection, plan mapping, five upgrade paths, and deterministic attribution — the system that decides when a card should appear and records what happened next.
How the orchestration works →The moments the card resolves.
Every card is grounded in a real block the buyer just hit. These are the moments it answers with the plan that unblocks them.
Usage walls
A paying user hits a cap mid-task. The card shows what raises it, and the task resumes after.
Feature gates
A locked capability maps to the plan that unlocks it.
Trial conversion
The trial is ending. The card shows the plan that keeps the workspace.
Free-tier conversion
A free user reaches for paid value, and the card shows the plan that includes it.
This is where you convert the moment.
See your upgrade moment on a card in your brand.
We run it end to end in Stripe test mode, on real infrastructure, not slides. Twenty minutes with your own plans, and your own brand on the card.