30 ChatGPT Prompts That Build Pricing Pages

You are a usage-based pricing writer who makes one meter understandable on a /pricing page. <context> Build a complete usage-based /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. The meter is [METER]. Tiers if I gave them, comparison, FAQ, enterprise CTA. Not a homepage. Not a one-CTA landing page. </context> <inputs> - Product: [PRODUCT] - Meter name and unit: [METER] - Price per unit: [UNIT PRICE] - What counts as usage: [WHAT COUNTS] - What does not count: [EXCLUSIONS] - Worked example volume: [EXAMPLE VOLUME] - Enterprise path: [TALK TO SALES] </inputs> <task> Build the page: slim product nav; a hero that names [METER] and the unit price; a what counts / what does not pair; one worked bill using [EXAMPLE VOLUME] (math from constants, or [VERIFY] if a number is missing); a simple plan or credit pack band if I listed one; a short comparison table (self-serve vs enterprise); FAQ; and an enterprise CTA. Write finance-readable copy. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent unit prices or hidden fees. Mark gaps as [VERIFY]. - Mobile-first, semantic HTML, no lorem ipsum. - Keep this a pricing page. No product tour. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then show the bill formula and which example a first-time buyer should start on. </format>

You are a billing writer who explains included quota and overage on one pricing page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Each plan includes a [METER] quota, then an overage or hard stop. Comparison, FAQ, enterprise CTA. Not a landing page. </context> <inputs> - Product: [PRODUCT] - Meter: [METER] - Plans with included units and prices: [PLANS] - Overage price or hard-stop rule: [OVERAGE RULE] - Worked example: [EXAMPLE VOLUME] - Who should take enterprise: [ENTERPRISE RULE] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that states included units then overage; plan cards that print included [METER], overage rule, and CTA; a worked example that walks included units at $0 then overage; a comparison table; an honesty block on the cap; FAQ; and an enterprise CTA. If I did not give an overage number, write [VERIFY], do not guess. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Example math must match the constants on the cards. - Mobile-first, accessible table, no lorem ipsum. - Do not invent unlimited overage. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then restate the overage rule in one sentence a CFO can quote. </format>

You are a usage-pricing designer who puts a volume ladder on a public /pricing page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. [METER] gets cheaper in volume bands. Comparison, FAQ, enterprise CTA. Not a homepage and not a calculator-only widget page. </context> <inputs> - Product: [PRODUCT] - Meter: [METER] - Volume bands and unit prices: [TIER TABLE] - Base fee if any: [BASE FEE OR NONE] - Two worked volumes: [SMALL / BUSY] - Enterprise cutoff: [VOLUME OR [VERIFY]] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that says price falls as [METER] grows; an accessible volume-tier table; two worked bills (small, busy) that walk the bands; a plan or base-fee card if I gave a base; FAQ on unused units and true-up; a comparison strip (self-serve ladder vs enterprise); and an enterprise CTA. Walk tiers in copy the way the invoice would. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent bands. Mark missing prices as [VERIFY]. - Table stays scannable on a phone. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then explain how a busy-month bill walks the ladder. </format>

You are a pricing designer who teaches a meter with three worked bills plus a tiny estimator. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Usage-based. Three static example bills and one small calculator. Comparison, FAQ, enterprise CTA. Still a marketing /pricing page, not a web app. </context> <inputs> - Product: [PRODUCT] - Meter: [METER] - Unit price or tier table: [PRICING] - Three example volumes: [SMALL / MID / BUSY] - What does not count: [EXCLUSIONS] - Enterprise path: [CTA] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that names [METER]; three example-bill cards with volume, math, and total; a small estimator (number input, vanilla JS) that multiplies volume by the constants I gave; a what counts list; a comparison table vs enterprise; FAQ; and an enterprise CTA. Store prices in labeled JS constants. If a number is missing, show [VERIFY] instead of a fake total. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - Calculator math must match the example cards. - Accessible input and live total. Keyboard usable. - Mobile-first, no lorem ipsum. No invented fees. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then print the formula and which constants to edit. </format>

You are a packaging writer who explains a platform fee plus a usage meter on one page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Hybrid: base subscription plus [METER]. Comparison, FAQ, enterprise CTA. Not a landing page and not a full SaaS site. </context> <inputs> - Product: [PRODUCT] - Base plans and prices: [BASE PLANS] - Meter and unit price: [METER] - Included units inside the base if any: [INCLUDED] - Worked example: [EXAMPLE] - Enterprise includes: [ENTERPRISE NOTE OR [VERIFY]] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that says platform fee plus [METER]; base-plan cards that list included units; a usage band under the cards; one worked bill (base + usage); a comparison table; FAQ that separates the two charges; and an enterprise CTA. Keep both charges visible above the FAQ. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not hide the meter in a tooltip. Do not invent included units. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then show a one-line bill recipe a buyer can reuse. </format>

You are a PLG marketer who writes freemium /pricing pages that tell the truth about Free. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Free / Pro / Team. The free ceiling is unmissable. Comparison, FAQ, enterprise CTA. Not a homepage and not a one-CTA landing page. </context> <inputs> - Product: [PRODUCT] - Who Free is for: [FREE USER] - Free ceiling: [SEATS, PROJECTS, OR EXPORTS] - Pro and Team prices and limits: [PAID PLANS] - Why people upgrade: [PAID TRIGGER] - Enterprise path: [CTA] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that offers Free and names [FREE CEILING] in the first screen; three cards (Free, Pro, Team) with honest limits and CTAs; a when you will want paid band tied to [PAID TRIGGER]; a comparison table that marks Free versus paid; FAQ on export and downgrade; and an enterprise CTA. Write generous, specific copy. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Name the free ceiling in the hero or the very next block. No hidden limits. - Do not invent user counts. Mark gaps as [VERIFY]. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say where the upgrade story should sit so it does not kill free signups. </format>

You are a PLG writer who can stand behind a free-forever claim on a pricing page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Free stays useful. Paid unlocks are named. Comparison, FAQ, enterprise CTA. Not a landing page. </context> <inputs> - Product: [PRODUCT] - What stays free forever: [FREE FOREVER LIST] - Paid plan name and price: [PAID PLAN] - What unlocks on paid: [PAID UNLOCKS] - Team or extra paid tier if any: [TEAM OR NONE] - Enterprise path: [CTA] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that says Free forever and lists [FREE FOREVER LIST]; cards for Free and [PAID PLAN] (plus Team if I gave it); an unlocks grid; a comparison table; FAQ on whether Free will shrink (only claim what I said); and an enterprise CTA. Do not imply Free is a trial. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent a sunset date for Free. Mark unknown policy as [VERIFY]. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then list the three free lines a skeptic will test. </format>

You are a billing writer who puts a metered free cap on a public pricing page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Free includes a [METER] cap. Paid raises or removes it. Comparison, FAQ, enterprise CTA. Not a docs page and not a landing page. </context> <inputs> - Product: [PRODUCT] - Meter: [METER] - Free cap and reset: [CAP AND RESET] - Paid plans that raise the cap: [PAID PLANS] - What happens at the free cap: [HARD STOP / WAIT / UPGRADE] - Enterprise path: [CTA] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that names the free [METER] cap and the reset; plan cards with cap numbers on the face; a what happens at the cap block; a comparison table; FAQ; and an enterprise CTA. Keep the upgrade trigger honest and specific. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent cap numbers or a silent overage on Free. - Mobile-first, semantic HTML, no lorem ipsum. - Mark missing reset rules as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then write the one sentence you would put in the product when they hit the cap. </format>

You are a developer-tool marketer who prices a community or OSS free row beside paid plans. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Community / OSS / education free row plus paid tiers. Comparison, FAQ, enterprise CTA. Not a homepage. </context> <inputs> - Product: [PRODUCT] - Free row name and who qualifies: [ELIGIBILITY] - What the free row includes: [FREE SCOPE] - Paid plans and prices: [PAID PLANS] - What companies must buy: [COMPANY RULE] - Enterprise path: [CTA] - Proof I have: [NONE OR NOTE] </inputs> <task> Build the page: slim product nav; a hero that names the free row and [ELIGIBILITY]; a free-row card plus paid cards; a who must pay band for companies; a comparison table; FAQ on proof of eligibility; and an enterprise CTA. Write like a staff engineer, not a charity brochure. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent GitHub star counts or a fake nonprofit program. - Mobile-first, semantic HTML, no lorem ipsum. - Mark unknown legal terms as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then restate the eligibility rule in one line. </format>

You are a PLG marketer who builds a /pricing page around one honest upgrade trigger. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Freemium. The story is [PAID TRIGGER]. Comparison, FAQ, enterprise CTA. Not a landing page and not a feature tour. </context> <inputs> - Product: [PRODUCT] - Free ceiling: [FREE CEILING] - The upgrade trigger: [PAID TRIGGER] - Paid plans and prices: [PAID PLANS] - Who should stay on Free: [STAY RULE] - Enterprise extras: [ENTERPRISE] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a hero that names [PAID TRIGGER] as the usual reason to pay; Free and paid cards; a stay on Free if band; a comparison table that highlights the trigger row; FAQ; and an enterprise CTA. Do not invent extra gates I did not list. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - One primary trigger. Other paid rows can exist but stay quieter. - Mobile-first, semantic HTML, no lorem ipsum. - Do not invent prices. Mark gaps as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say which row should be visually louder than the rest. </format>

You are a SaaS packaging writer who pairs plan cards with a full compare table on /pricing. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Cards first, full feature matrix second, FAQ, enterprise CTA. This is your plans versus your plans, not a competitor landing page and not a homepage. </context> <inputs> - Product: [PRODUCT] - Plans and prices: [PLANS] - Rows I care about: [SSO, SUPPORT, API, AUDIT LOG, LIMITS] - Recommended plan: [PLAN] - Enterprise column or band: [ENTERPRISE] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a short pricing hero; plan cards with price and CTA; an accessible matrix with plans as columns and capabilities as rows, seats near the top; check, dash, or a short limit (not a vague yes); a recommended-column highlight; FAQ on upgrades; and an enterprise CTA. If a cell is unknown, write [VERIFY]. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Table must scroll or stack on a phone without losing headers. - Do not invent unlimited rows or prices I did not give. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say which row will drive the most upgrades. </format>

You are a pricing-table designer who orders rows by buying friction, not by your settings menu. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Compare table is the star. Seats, SSO, and [HARD LIMIT] are the first rows. Cards can be compact. FAQ, enterprise CTA. Not a vs-competitor page. </context> <inputs> - Product: [PRODUCT] - Plans and prices: [PLANS] - Seat rules: [SEATS] - SSO availability: [SSO BY PLAN] - Hard limit: [HARD LIMIT] - Other rows: [LIST] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; a hero that says compare limits first; compact plan cards or a price row above the table; an accessible matrix that opens on seats, SSO, and [HARD LIMIT]; remaining rows after; CTAs under each column; FAQ; and an enterprise CTA. Use short limit text, not icon-only cells. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent SSO or seat rules. Mark gaps as [VERIFY]. - Mobile-first, sticky or repeated headers on small screens. - No lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then list the first five rows in order and why. </format>

You are a packaging writer who makes support and SLA the readable part of a pricing table. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Plans still show price. The compare table leads with support, SLA, and onboarding. FAQ, enterprise CTA. Not a status page and not a landing page. </context> <inputs> - Product: [PRODUCT] - Plans and prices: [PLANS] - Support channel and hours per plan: [SUPPORT] - SLA if any: [SLA OR [VERIFY]] - Onboarding: [DIY / ASSISTED / NAMED CSM] - Other feature rows: [SHORT LIST] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; a hero about picking a plan by how you get help; cards with price and a one-line support promise; a matrix that opens on support, hours, SLA, onboarding, then a few product rows; FAQ; and an enterprise CTA. Never invent a 99.99 percent SLA. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent response times or SLA percents. Use [VERIFY]. - Mobile-first, accessible table, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say which support cell a buyer will forward to their admin. </format>

You are a packaging strategist who puts core plans and paid add-ons in one comparison table. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Core plan cards, then a matrix that includes [ADD-ON] as priced rows. FAQ, enterprise CTA. Not a homepage. </context> <inputs> - Product: [PRODUCT] - Core plans and prices: [PLANS] - Add-ons with price and who they are for: [ADD-ON] - What is included in core: [INCLUDED] - Who should skip add-ons: [SKIP RULE] - Cadence: [MONTHLY / ANNUAL] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; a hero that says plans plus optional add-ons; core cards; a matrix with core features then add-on rows (price, availability by plan, skip rule); a sample stack using only numbers I gave or [VERIFY]; FAQ; and an enterprise CTA. Keep add-on cadence aligned with the plan cadence I stated. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent add-on prices. Mark gaps as [VERIFY]. - Mobile-first, accessible table, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say which add-on belongs next to checkout versus talk-to-sales. </format>

You are a front-end pricing designer who makes a comparison table work on a phone. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. The compare table is usable at 360px: sticky first column, plan names that stay readable, CTAs that do not vanish. FAQ, enterprise CTA. Not a landing page. </context> <inputs> - Product: [PRODUCT] - Plans and prices: [PLANS] - Rows: [8-12 INCLUDING SEATS AND LIMITS] - Recommended plan: [PLAN] - Enterprise path: [CTA] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; a short hero; compact cards for desktop and the same prices above the table on mobile; an accessible matrix with a sticky feature column and horizontal scroll for plan columns; a recommended highlight; CTA buttons under each plan that repeat after the table; FAQ; and an enterprise CTA. Prefer short cell text over icons-only. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Table remains usable on a phone. Do not hide the matrix on small screens. - Do not invent cells. Mark gaps as [VERIFY]. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then describe the mobile table behavior in three bullets. </format>

You are a SaaS pricing designer who writes monthly / annual toggles without fake discounts. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Prices switch in place. Comparison table price row updates. FAQ, enterprise CTA. Not a homepage. Not a landing page. </context> <inputs> - Product: [PRODUCT] - Plans with monthly and annual prices: [PLANS] - Seats included per plan: [SEATS] - Recommended plan: [PLAN] - How annual is billed: [PREPAY YEAR / MONTHLY AT ANNUAL RATE] - Savings I can claim: [PERCENT OR DOLLAR, OR [VERIFY]] </inputs> <task> Build the page: slim product nav; pricing hero; an accessible monthly / annual toggle that updates every card price and the savings line; three plan cards with seats and CTAs; a comparison table whose price row updates with the toggle; FAQ on proration, refunds, and unused seats; and an enterprise CTA. Store prices in labeled JS constants. Compute savings from those constants, never a hardcoded 20 percent. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - Toggle is a button pair or switch with aria-pressed. Keyboard operable. - Do not invent an annual discount I did not give. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then show the savings math and what to test on the default period. </format>

You are a billing-clarity writer who will not hide how annual is collected. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Toggle monthly / annual. The page states [PREPAY YEAR / MONTHLY AT ANNUAL RATE] in plain words near the toggle. Comparison, FAQ, enterprise CTA. </context> <inputs> - Product: [PRODUCT] - Plans with both prices: [PLANS] - Annual collection: [PREPAY YEAR / MONTHLY AT ANNUAL RATE] - Refund or unused-month rule: [REFUND OR [VERIFY]] - Recommended plan: [PLAN] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; hero; toggle with a one-sentence collection note that changes with the mode; cards whose total due today versus per month label matches the collection rule; comparison table; FAQ that repeats the prepaid versus monthly-at-annual distinction; and an enterprise CTA. JS constants drive prices. No fake due today number. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - Labels must match the collection rule I gave. - Do not invent refund math. Mark it [VERIFY] if missing. - Mobile-first, accessible toggle, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then quote the one sentence that prevents a billing surprise. </format>

You are a pricing engineer who only prints savings the constants can prove. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Monthly / annual toggle. Savings come from the prices I gave. Comparison, FAQ, enterprise CTA. Not a promo landing page. </context> <inputs> - Product: [PRODUCT] - Each plan monthly price and annual price: [MONTHLY AND ANNUAL PRICES] - Seats or limits: [LIMITS] - Recommended plan: [PLAN] - Currency: [CURRENCY] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; hero; toggle; cards that show the active price and a savings line computed as (monthly * 12) minus annual, or the equivalent percent, from labeled constants; if I did not give annual, show [VERIFY] rather than a guessed discount; comparison table that updates; FAQ; enterprise CTA. Comment the savings function. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - Never hardcode Save 20%. Never invent annual from monthly unless I asked and then label it sample. - Accessible toggle. Mobile-first. No lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then print the savings function and a worked example for one plan. </format>

You are a pricing designer who defaults the toggle to annual without hiding monthly. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Default state is annual. Monthly is one click. Comparison, FAQ, enterprise CTA. Not a landing page. </context> <inputs> - Product: [PRODUCT] - Plans with monthly and annual prices: [PLANS] - Savings I can show: [SAVINGS OR COMPUTE] - Recommended plan: [PLAN] - How to label monthly: [MONTHLY ESCAPE COPY] - Enterprise path: [CTA] </inputs> <task> Build the page: slim product nav; hero that can mention yearly billing without shaming monthly buyers; toggle defaulting to annual (aria-pressed on Annual); cards in annual state on first paint; monthly prices ready in JS so the switch is instant; comparison table; FAQ; enterprise CTA. Monthly control is visible, not buried in a footnote. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - First paint must match the default (annual). No flash of monthly. - Do not invent savings. Mark [VERIFY] if needed. - Mobile-first, accessible contrast, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say how you avoided a dark-pattern default. </format>

You are a monetization designer who combines a billing-period toggle with a live seat total. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS and vanilla JS, returned as a working page I can open in the chat. Toggle monthly / annual. A seat stepper updates a total. Comparison, FAQ, enterprise CTA. Still a /pricing page, not a full billing app. </context> <inputs> - Product: [PRODUCT] - What a seat is: [SEAT] - Per-seat monthly and annual prices or plan prices that scale: [PRICES] - Minimum seats: [MIN] - Recommended plan: [PLAN] - Enterprise seat threshold: [THRESHOLD OR [VERIFY]] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; hero that defines [SEAT]; monthly / annual toggle; seat number input or stepper; plan cards whose totals recompute (period × seats) from labeled constants; a your total summary; comparison table; FAQ on unused seats; enterprise CTA when seats cross [THRESHOLD] or a [VERIFY] note. Guard seats below [MIN]. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only plus vanilla JS. - Seat math and period math stay consistent. No hardcoded totals. - Accessible stepper and toggle. Mobile-first. No lorem ipsum. - Do not invent volume breaks I did not give. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then show the total formula and where to paste real prices. </format>

You are a B2B pricing designer who keeps self-serve cards and a Talk to sales band on one /pricing page. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Self-serve tiers stay priced. Enterprise is a band or fourth path, not a takeover. Comparison, FAQ, enterprise CTA. Not a book-a-demo landing page with no prices. </context> <inputs> - Product: [PRODUCT] - Self-serve plans and prices: [PLANS] - Why someone talks to sales: [SSO, INVOICE, VOLUME, SECURITY] - What sales can offer: [CUSTOM TERMS OR [VERIFY]] - Demo or form note: [BOOK DEMO / CONTACT] - Recommended self-serve plan: [PLAN] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; hero for buyers who will self-serve; priced plan cards; comparison table; a Talk to sales band that names [SSO, INVOICE, VOLUME, SECURITY] and one CTA; FAQ that says when not to book sales; repeat the enterprise CTA at the bottom. Write low-hype copy. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not remove self-serve prices. Do not invent custom discounts. - Mobile-first, semantic HTML, no lorem ipsum. - Mark unknown security claims as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say whether the band should sit after the cards or after the table. </format>

You are a trust-center-aware pricing writer who puts SSO and compliance on the enterprise path. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Self-serve plans plus an Enterprise column or card that lists SSO, roles, and [CERT] only if I named them. Comparison, FAQ, custom-quote CTA. Not a /security page dump and not a landing page. </context> <inputs> - Product: [PRODUCT] - Self-serve plans and prices: [PLANS] - Enterprise features I have: [SSO, ROLES, AUDIT LOG, SLA] - Certificates I can name: [CERT] - What I do not claim yet: [OFF-LIMITS] - Quote CTA: [CONTACT / BOOK SECURITY REVIEW] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; hero; priced self-serve cards; an Enterprise card or column with SSO, roles, and [CERT] (or a [VERIFY] slot); a comparison table that includes those rows; FAQ for procurement; and a custom-quote CTA. Never imply a cert I put in [OFF-LIMITS]. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent SOC 2, ISO, HIPAA, or pentest dates. - Mobile-first, semantic HTML, no lorem ipsum. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then list every claim a reviewer will ask to see evidence for. </format>

You are a B2B demand marketer who puts a short enterprise form on the pricing page without killing self-serve. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Priced tiers stay. Procurement FAQ and a short form for invoice / security buyers. Not a standalone demo landing page. </context> <inputs> - Product: [PRODUCT] - Self-serve plans and prices: [PLANS] - Form fields I truly need: [NAME, WORK EMAIL, COMPANY, SEATS, SECURITY NEED] - Invoice or PO notes I can state: [INVOICE NOTES OR [VERIFY]] - Response time I can keep: [TIME] - Recommended self-serve plan: [PLAN] </inputs> <task> Build the page: slim product nav; priced cards; comparison table; a procurement FAQ (PO, net terms, DPA, seats); a short accessible enterprise form with a benefit-led button, not Submit; a privacy and response-time line; self-serve CTAs still visible. Keep fields to what I listed. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Accessible labels, required markers, sensible field types. - Do not invent net-30 or legal terms. Mark [VERIFY]. - Mobile-first, no lorem ipsum. Form is not the only CTA on the page. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then explain how to point the form at a CRM or inbox. </format>

You are a packaging designer who adds a custom Enterprise column beside three priced plans. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Four columns on desktop: three self-serve, one Enterprise with no invented price. Comparison is the same table. FAQ, enterprise CTA. Not a homepage. </context> <inputs> - Product: [PRODUCT] - Three self-serve plans and prices: [PLANS] - Enterprise includes: [SSO, SLA, CSM, OR LIST] - Enterprise price treatment: [TALK TO US / FLOOR PRICE IF I GAVE ONE] - Recommended self-serve plan: [PLAN] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; hero; four cards (three priced, Enterprise custom); a comparison table with four columns; FAQ; and a closing enterprise CTA plus self-serve CTAs on the first three cards. Stack to a readable layout on mobile (cards first, table scrolls). </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent an Enterprise dollar amount I did not give. - Mobile-first, accessible table, no lorem ipsum. - Mark unknown Enterprise cells as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then say how the fourth column should behave on a phone. </format>

You are a monetization writer who routes high-volume buyers off self-serve without hiding the public prices. <context> Build a complete /pricing page as one self-contained HTML file with inline CSS, returned as a working page I can open in the chat. Public tiers stay. A clear [VOLUME THRESHOLD] sends people to an enterprise CTA. Comparison, FAQ. Not a landing page. </context> <inputs> - Product: [PRODUCT] - Self-serve plans and prices: [PLANS] - Threshold unit and number: [VOLUME THRESHOLD] - What they get on enterprise: [ENTERPRISE INCLUDES OR [VERIFY]] - Meter or seat note: [UNIT] - Recommended plan under the threshold: [PLAN] - Currency: [CURRENCY] </inputs> <task> Build the page: slim product nav; hero that can mention self-serve up to [VOLUME THRESHOLD]; priced cards for buyers under the line; a crossing this volume band with the enterprise CTA; comparison table; FAQ on what happens if they grow past the threshold; repeat CTA. Keep self-serve checkout obvious for everyone under the line. </task> <constraints> - One self-contained, responsive HTML file; no dependencies except Google Fonts. - Do not invent the threshold. Do not invent volume discounts above it. - Mobile-first, semantic HTML, no lorem ipsum. - Mark missing enterprise inclusions as [VERIFY]. </constraints> <format> Return the full HTML as a working page you can open in the chat. If Canvas is available, put the file there. Then write the one sentence that sits on the volume band. </format>