Wix, Webflow or custom code: how to choose for a 10-page business site
8 November 2026 / 3 min read
The honest answer to "which platform should we use?" starts with a different question: what does this site need to do, and who is going to change it?
We build on all three levels. We have built sites in the Wix editor, our own site runs on Wix headless, and our software product Kriya Core is custom code. We have also done a couple of projects on Webflow, though we lean towards Wix because of the kind of clients we work with. So we have no platform to sell you. Here is how we decide.
What we do for a 10-page business site
We start by understanding the client: what they aspire to, what they actually need, where they are coming from, and which stack will make their life easier afterwards. Then we generally suggest a Wix-only site first.
If it turns out there is a lot more that the site has to do, we move up to Wix headless, or to custom code. We move up only when a requirement forces us to, not because the technology is more exciting.
Where each one fits
Wix editor. The right starting point for most business sites. A non-technical person can edit it themselves. We have built business sites this way, including one for a logistics company. Its limit is speed: there is not much you can do inside the editor to make a site faster. You cannot compress every image the way you would like, or strip back animations, so performance has a ceiling.
Wix headless. The middle path, and what we use for our own site. The front end is written in code, with Wix underneath it. You get custom animation, custom libraries and much better performance. You lose drag-and-drop editing, so changes need a developer. We explain what that was like in our rebuild story.
Webflow. We have shipped a couple of projects on it. We prefer Wix for most of the clients we work with, so it is not our default.
Custom code. The right choice when a site is really a product. Custom code gives you many more ways to optimise speed, and it is what we used for Kriya Core, a SaaS platform for gyms. We reserve it for when a project needs it.
When to leave Wix
The clearest signal is logins. Wix does not handle authorisation well. If your site needs many kinds of users, with a structured set of permissions behind each, we would recommend moving off Wix. It is easier to manage that through a purpose-built platform such as Supabase or AWS.
The second signal is speed. If your business depends on a site that loads faster than the editor can deliver, headless or custom code gives you tools that the editor does not.
Five questions before you choose
Who edits content, and how technical are they?
What must the site do beyond showing pages: logins, payments, calculators, integrations?
How custom does the design need to be, and how fast must it load?
How will the site change over the next two years?
Who will look after it once it has been handed over?
If your answers are "a non-technical person, nothing beyond pages and forms, and not very custom", a Wix site is very likely right. If you have logins, structured roles or serious performance goals, start talking about headless or custom code early.
Not sure which side of the line your project sits on? Our web design and digital platforms and custom development pages show how we scope each.
Related services: mobile app and product design, brand strategy and identity.
