Per-Site Pricing: Examples & Companies

What is it

Per-site pricing is a billing unit where each website, store, or licensed facility is billed as a separate unit, so spend scales with the number of sites rather than the number of users.

This corpus uses “site” in two ways, and they should stay separate. On website and commerce platforms, a site is one published website or store with its own plan. On Webflow, the “Add plan” button attaches a plan to one specific site, so an agency with ten client sites buys ten Site plans. That is also why Webflow’s Workspace tiers can offer “unlimited paid hosted sites”: the hosting is already paid for, site by site. The unit follows the deliverable. A freelancer shipping ten client sites pays more than a ten-person team maintaining one, which suits builders whose output is counted in sites and not in headcount. For how a unit like this compares with other options, see choosing the right usage metric.

In clinical AI, the site is a hospital. Viz.ai licenses its care-coordination platform per facility, has no /pricing page, and routes every buyer to “Request a demo.” Hospital count shapes the contract the same way site count shapes a website builder’s bill. But the price is negotiated, not posted, so a Viz.ai facility price can’t be compared with a website plan.

How it works

The companies in this set count sites in four ways:

For the included-sites structure, the formula is:

Monthly cost = account plan + max(0, sites − included sites) × per-site rate

Worked example (Duda, annual billing): a freelancer running 3 sites pays $19 + 2 × $19 = $57 on Basic, $29 + 2 × $17 = $63 on Team, or a flat $52 on Agency, which includes four sites. At 5 sites the gap grows: Basic reaches $95, while Agency is $52 + 1 × $17 = $69. The tier built for agencies becomes the cheapest option from the third site. This is why buyers with many sites should check where tiers cross over, not the entry price.

Companies using this

Seven of the eight companies below sell websites or online stores, where “site” means a published property. The one clinical AI vendor uses “site” to mean a licensed hospital, so read its row as a different unit.

Patterns observed

• The site pays for publishing. People are billed separately, or not at all. Webflow bills collaboration on its own Workspace ladder (Core $19, Growth $49, extra Full seats $39). The two ladders confuse enough buyers that Webflow’s own FAQ opens with “What’s the difference between a Workspace and a Site plan?” Wix goes the other way and includes collaborators in the site plan: 2 on Light, rising to 100 on Business Elite. Either way, the site stays the main billing unit and seats are secondary.
• AI credits are pooled above the site. Framer shares its monthly credits (1,000 on Basic, 3,000 on Pro) across every site and editor in a workspace. Duda gives each paid account 150 AI credits a month, however many sites it runs. Pooling means an agency with 20 client sites gets one AI balance instead of 20 separate ones. That mixes a per-site subscription with account-level credit-based billing.
• Agencies are the main buyers, but they rarely get a lower price per site. Wix has no agency price list. Wix Studio gives agencies a free workspace, and each client site buys the same consumer plan an individual would. Automattic rewards volume through a partner channel instead of a lower sticker price: accounts with 5+ sites get up to 60% off Jetpack and up to 50% revenue share on WordPress.com.

Counterexamples & variants

Shopify: the store is the unit, but a percentage is the real bill. Each Shopify plan covers one store, and Plus adds up to 9 expansion stores. But the Basic plan’s card rate of 2.9% + 30¢ per sale soon outweighs the subscription, and the extra fee for using a third-party payment gateway falls from 2% to 0.2% as merchants move up tiers. Shopify also has a second, physical site meter: POS Pro costs $89/mo for each retail location.

Automattic: a flat site plan with no traffic meter. Every paid WordPress.com plan promises “no traffic limits, no overage fees,” so a site’s cost stays the same however much traffic it gets. Plan tiers differ on storage, plugins, and support instead. Several other builders here sell bandwidth in tiers or charge for going over a cap. On WordPress.com, the site fee is the whole hosting bill.

Elementor: dropped per-site pricing, then brought it back. In 2022, Elementor’s Pro Agency license was $999/yr for up to 1,000 sites, so sites were the value metric. The 2026 Elementor One bundle removed that ladder. One Agency now allows unlimited sites and meters a 350,000-credit monthly pool instead. In August 2026, Elementor added a 25-site Expert tier back to the plugin ladder, matching the site count of a tier it had retired. Sites and credits now run side by side, and buyers choose which to be billed on.

Viz.ai: the facility price is offset by reimbursement. Viz LVO was the first AI software to receive a Medicare New Technology Add-on Payment of up to $1,040 per eligible use. That offsets part of a subscription that third-party analysis puts at about $25,000/yr for the stroke module alone (not an official price). The same contract works out very differently by facility type. A primary stroke center may need the add-on payment to break even. A comprehensive center gains from the extra thrombectomy volume and relies less on it. No website builder has a comparable offset.

What this means for buyers vs vendors

For buyers

• Count every site, including client sites, staging sites that later go live, and additional storefronts. Then price your count 12 months from now, not just today. The unit only works in your favor if you know how many sites you will run.
• Ask whether each plan belongs to the site or to the account, and whether it can move with the site if a client leaves. A plan tied to the site suits handing sites over. A license on the account suits a portfolio.
• Add up all the billing axes. The site fee is usually the smallest line once seats, the AI pool, and add-ons are included. Model them together with the pricing calculators instead of comparing headline plan prices.
• For stores, estimate transaction fees from your sales volume before comparing plans. For clinical software, get the facility definition in writing (one campus or a whole health system). Model the contract with any reimbursement offset set to zero, because offsets are reviewed and can lapse.

For vendors

• Choose the site when the customer’s own output is sites. Per-site pricing tracks an agency’s revenue better than seats do. Also publish the site count at which an included-sites tier becomes cheaper, because that is what gets buyers to upgrade.
• Keep AI and other pooled resources at the account level. Charging an AI allowance per site gives an agency one AI bill for every client, which is hard to forecast. Treat the pool as an entitlement and usage grant and say plainly what happens when it runs out.
• State whether traffic is included in the site plan or metered. Buyers accept either, but they don’t accept surprises. If the site is only the entry fee and a transaction or bandwidth meter is the real bill, show that on the pricing page. See the introduction to usage-based pricing for the trade-offs.

Explore this theme in the knowledge graph →