Webflow vs a custom build: where each one stops
A custom marketing site with a CMS costs EUR 1.500 to EUR 3.500 with us, which is step 03 on our price ladder, and a smaller custom site starts at EUR 600 to EUR 900 at step 01. Webflow competes hard at those steps, so the question worth asking is not which tool is better but whether the thing you are building stays a set of pages or turns into software.
Webflow is a good product. It also has a shape, and that shape decides where it stops being the cheaper option.
What Webflow is genuinely good at
Webflow puts a visual editor over real HTML and CSS. Someone with design sense and no code can move a section, restyle a heading and publish it, and hosting, certificates and the CDN come with the plan. For a brochure site with a contact form, that covers most of the job, and it stays easy after launch. If nobody at your company writes code and nobody is going to, that outweighs any technical argument against the platform.
So the uncomfortable part first. At step 01 and step 02, EUR 600 to EUR 900 for a single-page landing and EUR 900 to EUR 1.500 for a mini-site of two to three pages, a Webflow build is a fair alternative to ours. We win those on page weight and on owning the output, not by pretending Webflow could not have done it.
Where Webflow stops
Webflow is a publishing tool with a content database attached. As soon as the site needs logic, that shape starts working against you.
Accounts and permissions
A login, a dashboard, data belonging to one user, a role that sees what a visitor does not: that is step 04 at EUR 3.500 to EUR 7.500. Webflow memberships will put a page behind a gate. The distance between hiding a page and giving an account a state that changes what it sees is where you write around the platform instead of with it.
Payments
Payments are step 04 in a new build and an add-on, EUR 600 to EUR 1.500, on an existing custom build. A checkout has states: pending, failed, refunded, disputed, renewed, cancelled but valid until the period ends. Each one has to show the customer something true and reach your bookkeeping correctly. That is application work wherever the pages are hosted.
Work the site does while nobody is looking
Scheduled jobs, a sync with your CRM or stock system, a reminder the day before a booking, a reaction to a webhook. Webflow hands this to third-party automation services, and for light work that holds. When the automation becomes the product, you are paying a website builder to host the visible edge of a system living somewhere else.
The shape of your content
The Webflow CMS is at its best when content is a list of similar items. Relationships between collections, deep nesting and content that has to be queried rather than listed are where it gets awkward.
A straight comparison
| What you need | Webflow | Custom build |
|---|---|---|
| Edited by someone who does not code | Built in, and strong | A CMS from step 02, shaped to your content |
| Cost to start | Build cost plus a plan per site | EUR 600 to EUR 900 at step 01, EUR 1.500 to EUR 3.500 at step 03 |
| Cost after launch | A subscription for as long as it exists | Hosting, plus Care at EUR 100 to EUR 300 per month if you want it |
| Login, dashboard, user data | Thin past simple gating | Step 04, EUR 3.500 to EUR 7.500 |
| Payments and checkout | Only as the platform models it | Step 04, built around your cases |
| Talking to your other systems | Through third-party automation | Direct, in code you own |
| Ownership | Your content, on their platform | You own the code, the repository and the database |
| Leaving later | A rebuild | Move the repository |
What the switching cost looks like later
Nobody quotes for this, so here it is. Leaving Webflow is not an export. Text and images come out, and the design survives as a reference, but the site does not transfer. The layout is Webflow's, the CMS structure is Webflow's, the forms and everything submitted through them are Webflow's, and the interactions live in Webflow's own panel.
The move is a new build at whichever step the site has grown into. If it grew because you added accounts and a checkout, you are not rebuilding step 03 at EUR 1.500 to EUR 3.500, you are commissioning step 04 at EUR 3.500 to EUR 7.500. Then add a redirect map for every URL that changes, which is small work and expensive to skip.
That does not make Webflow a trap. It makes it a decision with a direction. You leave the platform when you need something it does not do, and nothing pulls you back the other way.
Which step fits, and how long it takes
Scoping comes first, a fixed quote follows it. Step 01, a single page with a form, analytics and a responsive layout, is 1 to 2 weeks. Step 02, a mini-site of two to three pages with a contact flow and a basic CMS, is 2 to 3 weeks. Step 03, four to seven pages with a CMS, service pages and booking or contact, is 3 to 6 weeks. Step 04, the first step with logins, dashboards, an API, CRM work, payments or a chatbot, is 6 to 12 weeks. Step 05, a custom SaaS platform from EUR 7.500, gets quoted after discovery, because scope, auth, billing, admin and deployment are the discovery.
What moves a quote is how much already exists and can be kept, whether the site needs accounts and payments, how many languages it runs in, and what happens to it after launch. Care is EUR 100 to EUR 300 per month for updates, monitoring, backups and small fixes, not redesign and not new features. SEO foundation is a one-off at EUR 450 to EUR 750 covering Console, analytics, indexation, technical hygiene, titles, internal links and a 3 to 6 month plan. Every step is listed on packages, and how we work is on design and engineering.
When to spend less
If you have not sold the thing yet, do not commission the platform for it. Step 01 at EUR 600 to EUR 900 puts one page, one form and honest analytics in front of real people, and what they do there tells you whether step 03 or step 04 deserves anybody's money.
Webflow is also the right answer when all of this holds at once: the site is pages, it will stay pages, somebody inside the company likes editing it, and the subscription sits comfortably next to what the site brings in. A custom build nobody maintains is a worse outcome than a Webflow site somebody looks after.
Common questions
Can you take over a Webflow site instead of rebuilding it?
Yes, and if the site is doing its job the cheapest advice is to leave it there and fix what is weak. What we cannot do inside Webflow is add real application behaviour. If that is what you need, the answer is a build, and we would rather say so before you pay us to try the other way.
Is a custom site harder to edit than Webflow?
It is different rather than harder. From step 02 a CMS is part of the build, shaped around your content instead of a general-purpose canvas. You edit the fields that are meant to change rather than dragging sections about, which is faster for whoever does the weekly edits and safer for the layout. What the build is made of is on our Next.js page.
What happens with hosting?
The client owns the code, the repository and the database, so where it runs is your call. We can host it, agreed per customer rather than as a standing arrangement.
Is Webflow bad for SEO?
No. It outputs clean markup and covers the technical basics. The limits show up in page weight and in control over how and when things load. If organic search is your main channel, that control is worth paying for.
If you want the number for your own case rather than a range, send us the brief. We scope it, place it at a step, and the quote after that is fixed.
Building something?
JP Studio designs and builds websites, storefronts and product interfaces.