Webflow UX Teardown: $15, $25, $2,500, and a Footnote That Changes All Three

Open Webflow's pricing page and you get one continuous row of cards. Starter, free. Basic, $15 a month. Premium, $25 a month. Then, in the very next column, Team at $2,500 a month, annual contract required.

Adjacent cards. A hundredfold jump. The only thing marking the border is a small heading above the row and a slightly greyer card fill.

The gap itself is honest. Plenty of products have a self-serve tier and an enterprise tier with a chasm between them. What's harder to forgive is the line of grey type under the cards: All prices in USD, per site.

Per site. The $15 is the price of one site on Webflow. By the time the buyer reads that preposition, they have already anchored on the number.

The three pages a buyer actually reads

The platform overview, the template marketplace, and pricing. That's the order an evaluator hits them: what is this, what can I start from, what does it cost.

A 404 that kept the old company

The route needed one correction. Webflow's /product URL now returns a 404, and the error page is a fossil. Its footer still lists Designer, CMS, Hosting, Editor, Interactions and "Webflow vs. WordPress" — the navigation of a company that sold a design tool. The live site retired every one of those labels. Nobody redeployed the 404.

One button, fifteen tabs

Read the hero against the header directly above it. They disagree.

The header offers three doors: Log in, Contact Sales, and a blue Start for free. The hero offers one, and it says Contact sales. On the page whose whole job is explaining the product, the self-serve path lives only in the persistent chrome. It never appears in the content.

That's a decision about who arrives here, and it's probably right. Nobody lands on /platform mid-task. They land there building a comparison for someone else.

What follows is shaped the same way. A five-item nav sits under the hero: Site builder, Composable CMS, Optimization tools, Management at scale, Ecosystems and API. Each of those is a tab set. Site builder splits into Visual development and Custom code. The CMS into Visual content management and Headless APIs. Optimization into four tabs. Management into four more. Four of the five sections close on an ebook card.

The page runs 8,562 pixels, and seeing all of it means operating roughly fifteen controls. That's a table of contents, which is a fair shape for what Webflow now is. It also explains the single button: nothing on this page can state the product's scope in one scroll.

The marketplace shows everything except the price

The header changes completely. The wordmark drops to the bare W, the nav becomes Dashboard, Marketplace, Learn, Resources, and Log in and Contact Sales vanish, replaced by one blue Get started — it's free. You have crossed into a different property. Only the logo tells you it's still the same company.

The hero recentres and makes a different promise: Launch a high-performing site without starting from scratch. Then check the browser tab: 7000+ Free & Premium HTML Website Templates. The screen sells an outcome, the title tag counts inventory. Both are reasonable, aimed at different readers. The tab is the one Google shows.

Now look for a price. Framer's marketplace puts the commerce state in the button verb, Remix for free and Buy for paid, so a visitor reads the whole grid's pricing by scanning one column. Webflow's browse layer has no equivalent. There is no price anywhere on this page: not on the category cards, not on the Featured, New or Free rails, not even a from-figure. Four screens down, the FAQ concedes that paid templates exist and carry "a separate one-time purchase fee that is independent from your Webflow hosting plan." That is the first mention of money.

"All prices in USD, per site"

Everything the page struggles with is visible in one screen: the Monthly/Yearly toggle already flipped to Yearly, Site plans over three cards, Platform plans over the fourth, and Free / $15 / $25 / $2,500 reading straight across.

Then the variables start.

Premium's $25 sits above a dropdown running 50 GB to 2.5 TB of bandwidth, so it prices the cheapest configuration rather than the plan. Below the fold, four add-ons arrive with meters of their own. Optimize at $299/mo by page views. Analyze at $9/mo by sessions. Localize Essential at $9/mo and Localize Advanced at $29/mo, both by locale count. Then a separate section for Ecommerce plans, and another for Workspace plans, a parallel subscription that never appears in the top row.

Try the sum for an ordinary case. A marketing team with three sites, two locales and basic analytics: three Premium site plans at $25 is $75, Localize Advanced is $29, Analyze at its smallest tier is $9. That comes to $113 a month, assuming all three sites fit the lowest bandwidth step, and it still omits the Workspace line, which this row never quotes. Six controls and a jump to a different section, to reach a figure the page could have printed.

The FAQ closing the page opens with exactly the question it has earned:

What's the difference between a Workspace and a Site plan?

When a pricing page's first FAQ is a request to define its own units, the units are the design problem. The numbers are fine. The tiering is defensible. What's missing is the sentence that lets a buyer add them up.

The homepage knows exactly who it's for

7,526 pixels, and the discipline that goes missing on pricing is completely intact here.

Every proof on this page is denominated in money or time. $200M in new pipeline. $6M in annual cost savings. A 67% drop in dev ticketing. 1,170% traffic growth. Thirty-two sites launched in ten days. Sixteen customer logos, four of them carrying a stat and a Read story link, then six full-bleed video cards, each a face and a figure.

There is no craft proof in that stack at all. No awards, no community, no gallery until you are 5,000 pixels down, where the sites-built-in-Webflow slider finally arrives carrying no number. For the company that spent a decade being the designer's tool, that is a complete inversion of who the front door is written for, executed without a trace of nostalgia.

Two details here are worth stealing and one is worth fixing.

The audience switcher is genuinely good. Instead of a persona tab row, Webflow sets a sentence, What marketing teams love about Webflow, with a dropdown embedded mid-sentence, and swaps the card marquee beneath it when you change the noun. It is segmentation disguised as prose. It keeps the page from opening on a wall of personas, and it forces the copy to read naturally in every state.

The Source section is the other. It takes more vertical space than anything else on the page and spends it on a dark product film: an agent session panel, jobs reading Update pricing FAQ for the Enterprise…, Localize the pricing page into German…, Draft a five-email onboarding nurture…, docked beside a real browser at localhost:3000. Every job on that list is a marketing chore. Same argument as the numbers, made in pictures.

The fix: directly under that film sit four supporting bullets, and the fourth repeats the third word for word. Customize workspaces for every team member, printed twice, with two different icons, on the busiest page the company owns.

What this means for your product

Pricing pages fail on arithmetic long before they fail on price.

The test is whether a buyer can produce one number for their own situation without opening a spreadsheet or a chat window. The three-site, two-locale sum above took six controls and a jump to a different section, and came out incomplete anyway.

Put the unit beside the number. $15/mo per site costs four words in the card and removes the largest misread on the page.

Calibrate every configurator. Bandwidth, page views, sessions, locales: each control should carry one line like a 20-page marketing site typically runs 50–100 GB. Buyers cannot estimate in a unit they have never measured, and the estimate they invent is always wrong in the direction that loses the sale.

Show one total. This is the fix that matters, and almost nobody ships it. A three-field estimator — sites, locales, add-ons — resolving to a monthly figure would answer the page's own opening FAQ better than the FAQ does, and it costs a form and a lookup table. Webflow already holds every input: the plan prices are static, the meters are enumerated in the selects, and the add-ons are independent. Nothing about the arithmetic is hard. The reason it doesn't exist is that no single team owns the sum, which is the same reason the units diverged in the first place.

Underneath all three sits the general rule. Webflow's homepage teaches an evaluator to think in revenue and headcount. Its pricing page bills in sites, workspaces, seats, gigabytes, sessions, page views and locales. Somewhere between those two pages, somebody has to publish the exchange rate.

Take it further

The lens behind this teardown — can a visitor tell what a control does and what it will cost them — is the UX Clarity framework, the same one we apply in a Full UX Audit. For how that scoring becomes a prioritized fix list, read what a real UX audit looks like.

Sources: NN/g — Match Between System and the Real World · NN/g — Recognition Rather Than Recall.

Can a buyer add up your pricing page without asking you? Apply for a Full UX Audit →