For about fifteen years there were two ways to get a website. You could have a designer draw something beautiful in Photoshop and then watch a developer rebuild it in WordPress, losing a little of the intent at every step. Or you could pick a template, accept its opinions about how your business should present itself, and spend the next three years explaining to people why the site does not look like the brand.
Webflow removed the gap between those two. A designer works in a visual canvas, and what comes out the other side is production HTML, CSS and JavaScript rather than a picture of a website. There is no translation step, because the design is the build.
That is the whole idea, and it explains everything else about the platform. Webflow is hosted, so your subscription covers the design tool, the CMS, the hosting on a global CDN, SSL and the publishing pipeline. You design in the browser, you press publish, and the site is live in about twenty seconds.
Why the no-translation part matters commercially
The usual failure of a website project is small and cumulative. A layout is approved at 1440 pixels wide, then rebuilt by someone who was not in the room when the reasoning was agreed. Spacing drifts. A hover state that carried the whole feel of the brand becomes a colour change. Nobody signs off on the compromise because nobody notices it happening, and the site that launches is a slightly duller version of the one that was sold.
Webflow removes that decay by removing the handover. The person making the design decision is the person setting the value that ships. Motion speed, line weight, the exact spacing between a heading and the sentence under it: these survive to production because there is no second version of them.
Heritage Saunas is the clearest case of that mattering. The site had to launch before a single sauna had been completed, which meant no product photography and nothing concrete to show. The whole proposition rested on atmosphere: thin precise lines framing imagery, dotted accents threading through the layout like technical drawings, motion slow enough to feel like the room it was describing. That kind of build lives or dies on details that would not have survived a handover. It converts enquiries at 4.6% against a 2.7% industry benchmark.
What Webflow costs in 2026
Webflow restructured its pricing on 13 May 2026, and the change was the largest in the platform's history. The old CMS and Business site plans merged into a single Premium tier, a Team plan appeared between self-serve and Enterprise, and workspace plans dropped from five tiers to three. Anything you read about Webflow pricing written before that date is describing a structure that no longer exists.
Site plans, priced in USD and excluding GST:
- Starter, free. A webflow.io address, two static pages, 1GB of bandwidth and fifty form submissions. Fine for learning the tool. Not a business website.
- Basic, $15 a month billed yearly. Custom domain, 300 static pages, 10GB bandwidth, unlimited form submissions and password protection. No CMS, so every page is built by hand.
- Premium, $25 a month billed yearly. The CMS arrives here, along with site search, code components, form file uploads and bandwidth tiers that scale from 50GB upward. This is the plan almost every real business sits on.
- Team, $2,500 a month on an annual contract. Localisation, AEO agents, publishing workflows, single-page publishing, a site activity log and API, plus governance and priority support.
- Enterprise, negotiated. Granular permissions, custom roles, secure integrations, a dedicated account manager and enhanced SLAs.
Commerce is a separate add-on that sits on top of a site plan and did not change in the May restructure: Standard at $29 a month with a 2% transaction fee and a 500 item limit, Plus at $74 with no transaction fee and 5,000 items, Advanced at $212.
The jump from $25 to $2,500 looks brutal written down, and in practice most New Zealand and Australian businesses live at $25 a month very comfortably. Team exists for organisations with compliance requirements, multiple markets or a content team large enough to need approval workflows. If you are asking whether you need it, you do not.
The CMS is the part people underestimate
Webflow's Designer gets the attention. The CMS is what determines whether the site is still working for you in year three.
You define your own content structures rather than accepting a blog and a page type. A collection might be case studies, or team members, or locations, or product specifications, each with the fields you decide it needs: rich text, images, dates, switches, references to other collections. You design one template, and every item in the collection renders through it. Add the two hundredth case study and it arrives fully designed.
Your team edits through the Editor, which sits over the live site rather than behind a separate admin. A marketing manager clicks the paragraph they want to change and changes it. There is no staging environment to explain, no plugin update to fear, and no version of the site that only the agency knows how to touch.
That last point is the reason we hand sites over the way we do. Skyrocket is not a retainer business, so there is no commercial reason to keep a client's team dependent on us. They get trained properly on running the site before anything is handed across.
Where Webflow is the wrong answer
Webflow is a website platform with commerce bolted on. It is not a commerce platform.
Its ecommerce offering handles a short catalogue with straightforward fulfilment perfectly well. It does not carry multi-location inventory, wholesale catalogues with account-specific pricing, retail POS sharing stock with the website, or anything close to Shopify's payment infrastructure and checkout research. A business selling at volume across markets and locations belongs on Shopify, and pushing that operation into Webflow commerce creates work that never stops.
The productive answer, when a brand needs both, is to run both. Slight Twist uses a Webflow front end for the brand experience with Shopify handling commerce underneath, and it took three CSSDA awards including Special Kudos. That split costs more to set up and it buys you design control and commerce depth at the same time.
Webflow also rewards being used properly. The canvas gives you real control over the box model, which means it also gives you room to build something structurally messy that becomes expensive to maintain. Sites built without a class naming system, by someone learning the tool on your budget, tend to arrive looking fine and ageing badly.
Webflow against WordPress
WordPress still runs a large share of the web, and for a while it was the default answer for any business that wanted a site it could edit. The comparison is worth making honestly, because plenty of good sites run on it.
WordPress is free software you install somewhere. That word free is doing a lot of work. You need hosting, and the cheap hosting that makes the sums look good is the same hosting that makes the site slow. You need a theme, bought rather than made, carrying a pile of features you will never use. You need plugins for forms, for SEO, for caching, for security, for anything the theme does not do. Then you need somebody to keep all of it updated, because a plugin left unpatched is how a site gets compromised, and the plugins update on their own schedules rather than yours.
Webflow replaces that entire stack with a subscription. Hosting, security, SSL, the CMS, forms, the CDN and the design tool arrive as one thing that Webflow maintains. There is no plugin conflict, because there are no plugins. There is no update to schedule.
What you give up is the long tail. WordPress has a plugin for almost anything ever conceived, and if your requirement is unusual enough, somebody has built it. Webflow expects you to build what you need or connect it through an integration, and that is a real trade rather than a hidden one.
For an established business without a developer on staff, the maintenance question decides it more often than the design question does. A Webflow site does not accumulate technical debt while nobody is looking at it.
Who Webflow suits
Webflow earns its place when the website is the primary sales asset for a considered purchase. Professional services, manufacturers, property, hospitality groups, B2B businesses with long sales cycles, anyone whose customers research for weeks before making contact.
It suits businesses where the brand has to do heavy lifting, where the category is crowded and the site needs to look like the reference point rather than another entrant. It suits marketing teams that want to ship a landing page on Tuesday without booking developer time. And it suits companies with a real content strategy, because the CMS was built for content rather than adapted to it.
If revenue arrives through a cart at volume, that is a Shopify conversation. If it arrives through an enquiry after a long consideration, this is the platform.
What a Webflow build actually involves
Before anything is designed, we look hard at what your competitors are doing online: who is winning, and who is coasting on a good-looking template with nothing commercial behind it. The site gets built around the gap between those two, which is what gives you room to lead the category rather than compete politely inside it.
Then the structure. Content types, how they relate, what a page has to prove before someone will pick up the phone. Integration mapping happens here too, because most businesses already know their CRM and their booking system, and the real work is deciding exactly how each chosen system will behave inside the site and who owns each connection.
Design and build then happen in the same tool, which is the entire point of choosing Webflow. Then your team gets trained on running it themselves, properly, before handover.
Common questions
Is Webflow good for SEO?
Yes, and better than most platforms out of the box. You control page titles, meta descriptions, canonical tags, alt text, schema markup and the full URL structure, while hosting runs on a fast global CDN and pages are served as static files. The code Webflow generates is clean. Most SEO problems on Webflow sites trace back to how the site was built rather than to anything the platform imposed.
Do I need to know how to code to use Webflow?
To edit content, no. The Editor is designed for people who have never seen a line of HTML. To build a site properly in the Designer, you need to understand how HTML and CSS actually work, even though you never type them. That is precisely why most established businesses have a studio build it and then run it themselves afterwards.
Can Webflow handle a large site?
Comfortably. The Premium plan supports substantial CMS collections and the bandwidth tiers scale to multiple terabytes. Sites with tens of thousands of CMS items run on Webflow. The constraint tends to be how well the content model was designed rather than the platform's ceiling.
What does a Webflow site cost in New Zealand?
A template applied to your brand runs a few thousand dollars. A custom-designed site with a considered content model, mapped integrations and team training sits in the tens of thousands, and complex multi-market builds go further. The figure that matters is what the site returns against it, which is why a brief should open with a commercial target rather than a page count.
Can I move my existing site to Webflow?
Yes. Content, images and URL structure all migrate, and moves from WordPress, Squarespace and older custom builds are routine. The risk sits in redirect mapping rather than in the content, so the redirect plan should be finished before launch rather than after it.
Skyrocket builds Webflow and Shopify websites for established New Zealand and Australian businesses. If you are weighing a platform decision and want a straight read on which one fits your commercial model, get in touch.
