Sub-grade spoke

Pricing Clarity — can agents compare your price against alternatives?

Agents compare options on the user's behalf. A hidden price is a skipped option — for SaaS sites with contact-sales pricing, for e-commerce sites with JS-rendered prices, for any product that depends on a sales call to surface a number. The fix is publishing pricing in extractable form: a public price on the page, ideally inside structured data, with enough scope (per seat, per month, per unit) that agents can reason about value.

By Chris Mühlnickel · 2026-05-16

What is Pricing Clarity?

Pricing Clarity is whether your product prices are exposed on a public page in plain text and (for transactional commerce) in Schema.org Offer markup — extractable by AI agents performing comparison or shopping queries on a user's behalf.

By the numbers

Why it matters

Pricing transparency is now an agent-conversion signal. A hidden price is a skipped option. Agents make comparisons before they make recommendations, and a page that hides the number is a page that can't be compared — which means the agent surfaces alternatives that publish their prices and skips yours, every time. The 87% of B2B buyers who want to self-serve their buying journey are exactly the cohort agents serve, and the self-serve discovery → self-serve evaluation path breaks the moment pricing requires a sales motion. The OpenView data on successful B2B SaaS converges on the same shape: 58% adopt hybrid pricing because the fully-hidden model leaves money on the table at the comparison step.

The structured-pricing gap in e-commerce is the bigger opportunity. Only 19% of e-commerce sites with Product schema include the Offer object — the block that exposes price, priceCurrency, and availability. Four out of five Product-schema implementations stop short of the data that makes the markup useful for comparison. Adding Offer to an existing Product block is hours of work; the leverage is being citable in every agent shopping query rather than being routed around for missing the canonical price field.

SaaS hidden pricing is a deliberate trade, but it's increasingly the wrong one. Contact sales for pricing worked when buyers expected a high-touch enterprise motion as default. In 2026 the default is self-serve discovery, and 87% of B2B buyers want at least part of their journey to stay self-serve. Published pricing on the lower tiers — even with a contact-sales path for enterprise — is the hybrid pattern the successful 58% adopted. Sites that hide every tier are filtering themselves out of agent comparisons at the top of the funnel.

Hidden pricing compounds with poor [Content Extractability](/learn/clarity/content-extractability). A site that hides pricing on a contact-sales page is one failure mode; a site that appears to publish pricing but loads it via JavaScript is the same failure mode in disguise. Agents see the empty shell, not the price. Pricing Clarity and Content Extractability fail together more often than they fail separately — the audit catches both, but the fix usually starts upstream with server-side rendering.

Where it's heading

Agent-mediated price comparison becomes a primary discovery channel. ChatGPT, Claude, and Perplexity already surface pricing comparisons for consumer products; the B2B SaaS surface is catching up fast. Vendors that publish per-seat, per-month pricing in extractable form are positioned for the channel; vendors that don't are betting the channel won't matter, which is an aging bet.

Structured pricing fields expand beyond Offer. Schema.org's current Offer model captures simple price plus availability. Expect richer extensions — usage-based tiers, volume discounts, contract-length pricing — that let agents reason about what would this cost at my scale directly from the markup. Sites with basic Offer today are positioned to adopt the extensions cheaply.

The contact-sales motion gets agent-native. Today, contact sales is a form submission and a human follow-up. Tomorrow it's an agent-to-agent handoff: the buyer's agent talks to the vendor's agent to negotiate pricing at scale. The vendors that publish enough pricing structure to support the handoff (price ranges, configuration options, package definitions) participate in the channel; the vendors that don't get filtered before the handoff happens."

Common mistakes

  • *Hiding all pricing behind contact sales.* Even a starting-at number unlocks comparability — fully opaque pricing filters you out of every agent comparison at the top of the funnel.
  • Publishing pricing in plain text but skipping the Offer schema. The visible price helps; the structured price is what gets cited preferentially. Adding Offer to an existing Product block is hours of work for a disproportionate return.
  • Loading pricing via JavaScript. The page looks priced to a human; agents see an empty container. Pricing Clarity collapses if SSR isn't shipping the number in initial HTML.
  • Quoting pricing without scope. $99 without per seat or per month is ambiguous — agents extract the number but can't reason about value. Always pair price with unit.
  • *Treating freemium tiers as not real pricing.* A free tier with price: 0 in Offer markup is a real option agents route users to. Omitting the tier entirely makes the free path invisible.

Frequently asked

What's wrong with *contact sales* pricing?

Nothing, if your sales motion genuinely requires it — but accept the cost. A page that hides price is a page that can't be compared, which means an agent surfacing options for a user routes around it. The 58% of successful B2B SaaS using hybrid pricing — public tiers plus contact-sales enterprise — split the difference: published price for the comparison-critical tiers, sales motion for the rest.

How do agents read pricing?

Three layers, in order of preference. First, Schema.org/Product with an Offer block (price, priceCurrency, availability, priceValidUntil) — fully machine-readable, unambiguous. Second, visible plain text on the page in initial server-rendered HTML — readable but requires natural-language extraction. Third, gated pricing (login required, demo required) — not readable. The first option ranks dramatically higher in agent confidence.

Should I expose enterprise pricing too?

Depends on your model. Most successful B2B SaaS publish a starting at price for enterprise (e.g. enterprise plans start at $50K/year) plus the contact-sales motion for the negotiation. That single number unlocks comparability without removing the sales conversation. Fully opaque enterprise pricing is a deliberate trade — be deliberate about it.

What goes in Schema.org Offer for SaaS?

price, priceCurrency, priceSpecification with unitText (per seat, per month), and availability set to InStock for available tiers. For freemium, ship an Offer with price: 0 rather than omitting the tier — agents reading the free option as a real option route to it correctly.

What about variable pricing — usage-based, tiered, custom quotes?

Publish the per-unit price plus a representative example: $0.001 per API call; typical mid-market customer spends $2-5K/month. Agents can extract both numbers and reason about value at the user's specified scale. A pure contact us for pricing page can't be reasoned about at all.

Why is hidden pricing especially costly for AI agents?

Agents make comparisons before they make recommendations. A user asks what's the best CRM under $200/month — the agent surfaces the options whose prices are visible and skips the ones that hide them. The 87% of B2B buyers who want to self-serve their buying journey are exactly the cohort agents serve, and hidden pricing breaks the self-serve discovery → self-serve evaluation path.

Does this matter for e-commerce too?

Critically. Only 19% of e-commerce sites with Product schema include the Offer object that exposes price and availability — meaning four out of five Product-schema implementations stop short of the data that lets agents actually compare against alternatives. Pricing Clarity for e-commerce is mostly about completing the Offer block, not adding it from scratch.