Because "a Webflow site" describes two completely different bills. One is what you pay Webflow to host and run the site, which is published and predictable. The other is what you pay someone to design and build it, which depends entirely on scope. Most articles blur the two, so the numbers never add up.
We are going to separate them here. The platform costs are public, and we checked them against Webflow's own pricing page while writing this. The build costs are not public anywhere, and we will be honest about why.
One warning before the numbers. Webflow restructured its plans, so a lot of advice still online describes tiers that no longer exist. If you read a guide comparing the old CMS and Business plans, it is out of date, and the prices in it are not the prices you will pay.
Webflow's site plans now run Starter, Basic, and Premium. Starter is free. Basic is $15 a month billed yearly. Premium, which is the first plan that includes the Webflow CMS, is $25 a month billed yearly. All prices are in US dollars, per site, with tax added at checkout.
Starter is for experimenting rather than launching. Webflow's pricing page lists it with a webflow.io domain, limited CMS access, two static pages, 1 GB of bandwidth, and 50 form submissions. You cannot connect your own domain, which rules it out for a real business site.
Basic is the plan for a site that genuinely does not need a CMS. It adds a custom domain, 300 static pages, 10 GB of bandwidth, unlimited form submissions, and password protection. If your site is a handful of pages that rarely change, this is enough.
Premium is where most business sites land, and Webflow marks it as new. It adds the Webflow CMS, bandwidth options that scale from 50 GB up to 2.5 TB, code components, site search, form file upload, and well-known files. The moment you want a blog, a careers page, or any list of things you edit without a developer, you are on this plan.
The blog you are reading exists because of that CMS layer, and choosing the right tier is mostly about traffic and content volume rather than features. We went through the ceilings in detail in our guide to Webflow's plan limits and whether your site will hit them.
Ecommerce is a separate site plan, not an upgrade to the ones above. Webflow lists three: Standard at $29 a month, Plus at $74 a month, and Advanced at $212 a month, all billed yearly, per site, in US dollars with tax added at checkout.
The differences are item limits and transaction fees. Standard covers 500 ecommerce items and charges a 2% transaction fee. Plus raises that to 5,000 items with a 0% transaction fee and unbranded emails. Advanced goes to 15,000 items, also with no transaction fee.
That 2% is the number to watch, because it is the only cost here that grows with your success. A store doing meaningful volume will save more by moving off Standard than the plan upgrade costs, so the cheapest plan stops being the cheapest option fairly quickly.
Whether Webflow is the right home for a store at all is a separate question from price, and the answer is not always yes. We laid out where it works and where it does not in our piece on using Webflow for ecommerce.
Most small businesses do not. Webflow's site plans include a free Starter Workspace, which is enough for an owner and a small team. The paid platform tier is aimed at organisations, not at a founder running one site.
That tier is called Team, and Webflow prices it at $2,500 a month with an annual contract required. It includes five full seats and five limited seats, up to 100 free stakeholder seats, and a guest role covering ten partner teams. Enterprise sits above it with custom pricing.
The jump from $25 to $2,500 looks alarming until you read what is in it. Team adds Webflow Localize, publishing workflows, single-page publishing, an activity log and API, governance controls, enhanced security and compliance, and priority support. Those are procurement requirements at a larger company, not niceties.
Webflow also lists optional add-ons including Optimize for A/B testing and Analyze for site analytics, the latter described as covering AEO insights like LLM visibility and AI agent traffic. Those are priced separately, so treat them as line items rather than assumptions.
Scope drives cost, and scope is mostly four things: how many unique page layouts you need, how complex the CMS structure is, how much custom motion and interaction you want, and how many outside systems the site has to talk to. Everything else is detail.
Unique layouts matter more than page count. Twenty pages built from four templates is a much smaller job than eight pages that are each designed from scratch. When someone asks us to price "a ten page website", the first thing we need to know is how many of those ten are genuinely different.
CMS structure is the cost nobody expects. A blog is simple. A blog plus case studies plus team members plus a resource library, with references between them so a case study can pull in its own team and related articles, is a data modelling job. Getting it wrong is expensive to fix later, which is why we spend real time on it before anyone designs anything.
Integrations are the other multiplier. A contact form is nearly free. A form that writes to a CRM, triggers a sequence, and posts to an internal channel is three connections that each need building and testing. Content is the quiet one too, since somebody has to write it, and projects stall on missing copy more often than on anything technical.
Because the quotes are not for the same project, even when the brief is identical. One includes strategy, copywriting, custom design, and testing. Another includes fitting your content into a template. Both are honest quotes for very different work, and the brief rarely says which one you want.
We will not publish a rate card, and we would be sceptical of anyone who does. A fixed number attached to a project nobody has scoped is either padded to cover the worst case or set low enough that the real cost arrives later as change requests. Our approach is to scope the work first and then give one fixed price for it.
What you can do is make quotes comparable. Give every studio the same written brief, with the same page list, the same integrations, and the same content situation. Differences in the numbers you get back then mean something, because they reflect approach rather than assumption.
Ask what happens when scope changes, because it will. A studio that has thought about this will have a clear answer. A studio that has not will tell you it never happens, which is the least believable sentence in this industry.
A cheap site costs you the rebuild. We are called in to fix these regularly, and the pattern is consistent: a template stretched past what it was designed for, class names nobody can follow, a CMS structure that cannot hold the content the business now has, and a load time nobody measured.
The expensive part is not the original fee. It is that the site cannot be extended, so every change is a fight, and eventually somebody decides it is easier to start again. You end up paying twice, and the second build starts from a worse position because there is now live traffic and existing URLs to protect.
Performance is where the shortcuts show up first. Sites arrive with uncompressed hero images, a dozen third-party scripts, and fonts loading from three places. The work to undo that is real work, and it is work the original budget skipped rather than avoided.
This is not an argument that expensive is automatically better. It is an argument that price should map to scope. A genuinely simple site built well by someone competent is a good buy. A complicated site built cheaply is the thing to avoid.
A good quote names what you get, not just what it costs. It should list the page layouts, the CMS collections and their fields, the integrations, who writes the content, what performance target the site is held to, and what happens after launch. Anything missing from that list is a gap you will pay for later.
Performance deserves to be written down. "Fast" is not a specification. A number is. We build to measurable targets because a site that looks beautiful and loads in four seconds has failed at the only job that happens before anyone sees the design.
Handover matters as much as the build. Ask who owns the Webflow project, whether you get the account or the studio keeps it, and what happens if you want to work with someone else in a year. The answer tells you a lot about how the relationship is designed.
Finally, ask whether the quote covers a template or a custom build, because that single choice moves the number more than anything else. We compared the two paths honestly in our guide on using a Webflow template versus building from scratch.
Budget for the site plan, the domain, and a small amount of ongoing work. The platform cost is the easy part, since a Premium plan at $25 a month billed yearly is a known number. What people forget is that a website is not furniture. It needs attention or it decays.
The realistic ongoing costs are content, small design changes as the business shifts, and periodic technical maintenance. Any third-party tools you connected also bill separately, and those add up faster than the Webflow plan does.
We would rather see a client spend less on the initial build and keep budget for the first year than spend everything on launch day. The version of the site that performs is almost never the version that shipped. It is the version that got adjusted once real visitors showed up.
This is where results actually come from. The gains published on our work page, like the move from 3.4 seconds to 0.8 seconds on ION Clean Energy or the 190% lift in organic traffic for Offbeat Travel, come from building carefully and then continuing to work on the site, not from one big launch.
Write down your page list, your content situation, and the three things the site must do for the business. That single page of writing will get you better quotes than any amount of back and forth, because it lets a studio price the actual job instead of guessing at it.
Then decide honestly whether you need a custom build. If your business is straightforward and your content is standard, a well-chosen template on a Basic or Premium plan may genuinely be enough, and we would rather tell you that than sell you something larger.
If you do need custom work, compare studios on how they think rather than on the number alone. Ask what they would cut from your brief and why. The answer to that question tells you more than a portfolio does.
If you want help figuring out which of these you actually need, we are happy to talk it through with no obligation. Send us your page list at phoenix.studio and we will tell you honestly what we think the job is, including if the answer is smaller than you expected.
Tell us where you want to go. We'll tell you how we'd get you there.