FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

A seat-based pricing calculator in Webflow

Build a seat-based cost calculator in Webflow: seats per product, add-ons, annual billing and a free-seat rule, with a worked example and test cases.

By Abdul QuadirUpdated 2026-11-067 min read
TL;DR
  • Write the pricing rules down as a short list before anyone builds the calculator.
  • Keep rates in one place, so the price table and the calculator can never disagree.
  • Let visitors drag a slider or type a number, and keep both in sync.
  • Show the maths: each line, the rate, the billing period and the saving.
  • Test the edges, such as 0 seats and the seat counts either side of each rule.

The short answer

To build a seat-based pricing calculator in Webflow, list your pricing rules first, store the per-seat rates in one place, and add a small script that reads the seat inputs and updates a summary on every change. Show each product's line, add-ons, the billing period and any saving, so buyers can follow the maths. Then test the edges, because that is where calculators go wrong.

How CUBE's calculator works

CUBE's Webflow pricing page has a full cost calculator. Visitors set seats for each of four products. The summary updates live with per-seat rates for the chosen billing period, add-ons, and the saving on annual billing. It also handles a free-seat rule: every 10 paid seats include 10 free guest, field or operator seats, and the calculator tells visitors how many more seats bring the next free ten. Seats can be typed in as well as dragged.

The numbers below are samples, not CUBE's prices.

Write the rules down first

Most calculator bugs are pricing questions nobody answered. Before the build, write a short rules sheet:

  • The rate per seat for each product, monthly and annual.
  • Minimum and maximum seats, and whether 0 is allowed.
  • Add-ons: flat fee or per seat, and whether annual billing changes them.
  • Free or bundled seats: what triggers them and whether they count per product or in total.
  • Rounding, currency and whether tax is shown.
  • Where the estimate leads: a sign-up, a quote or a call.

Have the person who owns pricing sign the sheet off. It becomes your test plan too.

A worked example

Here is a sample rules sheet in action. Every number is made up.

Line (sample)SeatsRateMonthly
Product A12$20$240
Product B5$35$175
Add-on, flat$50$50
Total, monthly billing17$465

Say annual billing takes 20% off everything. The total becomes $372 a month, billed as $4,464 a year, a saving of $93 a month.

Now the free-seat rule: every 10 paid seats include 10 free guest seats, counted in total. 17 paid seats give 10 free seats. Three more paid seats reach 20 and bring 10 more, so the summary says: "Add 3 more seats to get 10 more free guest seats." That nudge is just the remainder to the next multiple of ten.

Work through three or four examples like this by hand, write the answers down and keep them. They become the expected results when you test the build, and they catch rules that read well but give odd totals.

Structure the page

  • Inputs. One row per product, with a range slider and a number field side by side, each with a visible label.
  • Rates. Read from data attributes on each row, such as data-rate-month and data-rate-year. If the price table on the page comes from a CMS Collection, bind both to the same fields.
  • Billing switch. One toggle for monthly or annual that the whole calculator reads.
  • Summary. Lines, total, saving and the free-seat message. Add aria-live="polite" so screen readers hear the new total.
  • Call to action. A button that carries the choices into the next step, for example as URL parameters.

Keep the slider and the number in sync

People drag to explore and type to be exact. Support both:

  • When the slider moves, write its value into the number field, and the other way round.
  • Round typed values to whole seats and clamp them between the minimum and maximum.
  • Treat an empty field as 0 while typing, but do not overwrite it until the field loses focus, or typing becomes a fight.
  • Decide what happens above the slider's top value. A common choice is to cap the slider and allow larger typed values, with a note to talk to sales.

Show the maths

A single big number invites doubt. Show each product line with its seats and rate, the add-ons, the billing period, the saving and the free seats. Say clearly that it is an estimate, and whether tax is included. Buyers then send the calculator to their finance team with fewer questions.

Keep the script small and the first paint stable. Render the summary in the HTML with default values, so nothing jumps when the script runs and the page still reads with JavaScript off. Our post on Webflow interactions that stay fast has more on keeping custom code light.

Keep prices in one place

The most common failure is a price table that says one thing and a calculator that says another. Pick one source and make everything read from it. On our own site, the cost calculator reads the same price file as the pricing page, so a change in one place updates both.

In Webflow, a CMS Collection of plans can be that source: the price table binds to it, and the calculator reads the same values from attributes on the page.

Pass the estimate on

An estimate is most useful when it travels with the buyer. When they press the button under the total, carry their choices to the next page: seats per product, add-ons and billing period, as URL parameters.

  • On a sign-up page, open the plan with the same seats already filled in.
  • On a contact or demo form, put a short summary into a field, so sales sees the estimate before the call. Our own contact page fills its details box this way when a link passes a brief.
  • Keep the parameters readable, such as ?a=12&b=5&billing=annual, so a person can check them.

Never trust those numbers for billing. The real price is worked out again by whatever system takes payment or writes the quote.

Test the edges

CaseCheck
All products at 0Total is 0 or the minimum, never an error
9, 10 and 11 paid seatsFree seats switch at exactly 10
Switch billing back and forthTotal, rates and saving all change together
Type 7.5 or a letterRounded or ignored, never NaN
Type above the slider topThe rule you chose applies
Keyboard onlyArrow keys move sliders and the total updates
Every result checked by handMatches the signed-off rules sheet

What to do next

Write your rules sheet and work three examples by hand. If the answers surprise anyone on your team, fix the pricing before the calculator. When you are ready to build, see Webflow development or send us your pricing rules.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Yes. The inputs and summary are built in the Designer, and a small custom script does the maths and updates the summary on each change.

In one place that both the price table and the calculator read, such as a CMS Collection bound to data attributes on the page.

Both. Dragging helps people explore and typing helps them be exact. Keep the two in sync.

Work out the free seats from the paid total, then show how many more paid seats reach the next step, as a short message under the total.

Say clearly whether tax is included. Most calculators show an estimate before tax and say so.

Yes. CUBE's pricing page has a seat calculator for four products, with add-ons, annual billing and a free-seat rule. We do not quote their prices.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.