Price testing for agencies: run price tests on up to 20 client sites from one plan

Price testing for agencies: test prices on up to 20 client sites with one Pro plan, on any stack and provider, without holding a client's payment API keys.

Short answer

One Leverprice Pro plan covers up to 20 sites, so an agency can run price tests for each client on that client's own stack and payment provider. Each site gets its own keys and webhook connection, Leverprice never needs a client's payment API key, and any failure falls back to the client's normal price.

  • Pro covers up to 20 sites for $29 a month or $199 a year, which is $9.95 per site per year at full use.
  • Each client connects their provider with a webhook signing secret, which can confirm events but cannot move money.
  • Server SDKs for TypeScript, Python, PHP, Ruby and Go, plus checkout links for Webflow, Framer and Carrd sites, cover most client stacks.
  • Leverprice tests prices on software products sold through Stripe, Polar, Lemon Squeezy or Dodo Payments; it doesn't support Shopify.

Clients ask their agency what to charge, and the usual answer is a slide of competitor pricing and a recommendation. A price test puts the client's own visitors behind the answer: each one sees one price from a range the client approves, and the price that earns the most per visitor wins.

Leverprice runs those tests across client sites from one account. Pro covers up to 20 sites, and each site has its own keys and its own payment connection.

Why is price testing hard for agencies?

Because every client brings its own stack and its own payment account, and a pricing bug on a client's checkout is the worst kind of bug an agency can ship.

Stacks vary from client to client: Next.js for one, Laravel or Rails for another, a Webflow site for a third. Leverprice has server SDKs for TypeScript, Python, PHP, Ruby and Go that pass the same conformance vectors, with framework guides for the common ones, and a no-code mode for sites without a backend.

Payment keys are a liability. Holding a client's secret key means owning the risk if it leaks. Leverprice never asks for one: the client's server creates the checkout with its own keys, and each site connects its provider with a webhook signing secret, which can confirm events but cannot move money. Verified revenue through webhooks explains the model.

Mistakes have to stay contained. The SDK checks every price against the minPrice and maxPrice in the client's own code, returns the client's normal price if it gets no signed config within 500 ms, and stops entirely with LEVERPRICE_DISABLED=1. Test and live keys are separate, so QA on staging never touches live results. The security page has the details.

What should an agency price test first for a client?

The client's highest-traffic paid product, with a range the client signs off on before launch. Put the agreed minimum and maximum in the product config, and the SDK won't serve anything outside them.

1. The main plan on a client's SaaS

Example: a B2B client charging $49 a month. Test $49, $59 and $79 within the $49 to $79 range they approved. Each price is judged on its first payment: Polar verifies a subscription's first payment by webhook, and with Stripe subscriptions the client's server reports it with trackPurchase(), which shows as unverified. Set the project's Learn from setting to Reported so the engine learns from it. Dodo Payments verifies one-time payments only.

2. The launch price of a product you built for them

A product with no sales yet has no anchor and no customers to grandfather. Example: a one-time license at $99, $129 or $149 from the first day it's on sale.

3. A Webflow or Framer client site

For clients without a backend, create one hosted checkout link per price and put one Leverprice link behind the Buy button. Example: $29, $39 and $49. The page can't show the tested price, so take the number off it; the visitor sees the price at checkout. Price testing for no-code sites covers the setup.

How does Leverprice fit an agency workflow?

Each client site is its own project, with its own test and live keys and its own connection to Stripe, Polar, Lemon Squeezy or Dodo Payments. For clients that sell worldwide, the SDK also serves regional prices per country, set by hand or from 5 tiers by World Bank price level. Lemon Squeezy clients need a new provider before it stops processing payments on March 31, 2027 (announcement); after the move, connect the new one.

Your developers can install it with their coding agents. The dashboard's Install page has a ready prompt for Claude Code, Codex or Cursor that refers to the key by its environment variable name, and npx leverprice setup adds Leverprice's MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and Windsurf. An agent acts as the person who connected it, so it can read results and lock in winners on the sites that person manages, and every change lands in the audit log under the agent's name.

Leverprice is for software products sold through those four providers. It doesn't support Shopify stores or mobile in-app purchases.

How do you set up price tests for a client?

  1. Create a project for the client's site and keep its keys in the client's server environment.
  2. Agree on the range with the client: the current price as the fallback, plus a minimum and a maximum.
  3. Install the SDK in the client's stack, or set up checkout links for a no-code site. Call getPrice() where the price is shown and again at checkout, charge quote.price in quote.currency, append every quote.setCookie value and pass quote.metadata whole (docs).
  4. Have the client add the Leverprice webhook URL in their provider account and paste back the signing secret. You never need their API key.
  5. QA on staging with the test key, switch to the live key, start the test and lock in the winner when the engine calls it.

Which Leverprice plan fits an agency?

PlanPriceWhat you get
Free$0Manual A/B split, 1 product, 1 experiment, up to $500/month in tested revenue
Pro$29/month, or $199/year (about $17/month)Automatic optimization, unlimited tested revenue, up to 20 sites
Lifetime$299 once, 50 spotsEverything in Pro, forever

Free fits a pilot with one client. Pro is the agency plan: at full use, yearly billing works out to $9.95 per site per year ($199 / 20) and monthly to $1.45 per site per month ($29 / 20). Paid periods are non-refundable, so start with a Free pilot or a monthly plan. The pricing page has the details.

Frequently asked questions

Do we need our clients' payment API keys?

No. The client's server keeps its own provider keys and creates the checkout. Leverprice gets a webhook signing secret for each site, which can confirm events but cannot move money, and it never sees card data.

Can we run price tests on client Shopify stores?

No. Leverprice tests prices on software products sold through Stripe, Polar, Lemon Squeezy or Dodo Payments. It doesn't support Shopify or mobile in-app purchases.

What happens to a client's checkout if Leverprice goes down?

It keeps selling at the client's normal price. If the SDK gets no signed config within 500 ms, getPrice() returns the fallback price and doesn't throw, and LEVERPRICE_DISABLED=1 turns tests off for that site.

How do we report results to clients?

Each site's results are in the dashboard. For a recurring report, give a script or agent a read-only token and pull results through the MCP server or CLI; it can read everything and change nothing.