Skip to article body
A young man seen from behind plugging cables into a server rack lit by small lights
A young man seen from behind plugging cables into a server rack lit by small lights

Process · Studio Notes

WordPress, Webflow, Framer or a Custom Build: Which Fits Your Company Website?

We build on more than one of them. How we choose for each client, and where each one starts to hurt.

By Shehab Waleed, Founder, Cairo Studio 3 min read

Clients often arrive with a platform already chosen, usually the one a friend used. We build custom sites on SvelteKit and Next.js with Prismic as the CMS, we build Shopify stores, and we have shipped Framer sites when they were the better fit. This is how we choose.

The question that decides it

Who will change the website after launch, how often, and how much will they need to change? A marketing team that edits pages every week needs a different tool from a company that updates a news section twice a month.

WordPress

WordPress runs a large share of the web, supports right to left Arabic in its core, and has a plugin for almost everything. That breadth is also its cost: every plugin needs updates, and a site with many of them gets slow and fragile. It suits content heavy sites with a team that already knows it.

Webflow and Framer

Both are hosted visual builders: design, CMS and hosting in one monthly plan per site. They are fast to launch and easy for marketing teams to edit. In our experience, right to left Arabic layouts need extra care on both, and complex logic or integrations hit limits quickly. They suit marketing sites in one language, or two with simple layouts.

A custom build

A custom site on SvelteKit, Next.js or Nuxt, with a headless CMS such as Prismic, gives full control over speed, layout and features, and Arabic is designed as Arabic rather than adapted. Editors work in the CMS; structural changes need a developer. Most of our bilingual corporate sites, like Buna Holding and MASAR, are built this way. More on the stack on our Next.js and SvelteKit page.

And for online stores

Stores are a separate decision. We compare Shopify with a custom store in When We Build the Shop, and When We Don’t.

Share
X LinkedIn Facebook WhatsApp Email
A hand rearranging four painted wooden blocks of different sizes on a table

Pick the tool for who runs the site.

WordPress
Content heavy sites, plugin needs
Webflow
Marketing sites edited visually
Framer
Fast marketing and launch sites
Custom build
Bilingual corporate sites, unusual features
WordPress
Editors in the WordPress admin
Webflow
Editors in the visual editor
Framer
Editors in the visual editor
Custom build
Editors in a headless CMS
WordPress
Supported in the core
Webflow
Needs extra care
Framer
Needs extra care
Custom build
Designed in from the start
WordPress
Depends on theme and plugins
Webflow
Good
Framer
Good
Custom build
Best, fully controlled
WordPress
Hosting and plugin licences
Webflow
Monthly plan per site
Framer
Monthly plan per site
Custom build
Hosting and maintenance
WordPress
Low, open source
Webflow
High
Framer
High
Custom build
Low, you own the code

Based on the sites Cairo Studio builds and maintains, October 2026. Platform features change; check current plans before deciding.

WordPress suits content heavy sites with plugin needs, Webflow and Framer suit marketing sites edited visually, and a custom build suits bilingual sites or sites with unusual features. Decide by who will run the site after launch.

It is faster and more flexible, and you are not tied to plugin updates, but structural changes need a developer. It pays off for bilingual sites, high traffic or unusual features.

WordPress handles right to left text in its core, and a custom build lets Arabic be designed as Arabic. Visual builders can do it, but need extra care on layouts.

Both are excellent. Next.js has the larger ecosystem; SvelteKit ships less JavaScript and tends to be faster by default. Cairo Studio uses both and picks per project.

Tell us who will edit the site and how often. We will recommend a platform and explain the trade off, before any quote.

See our development stack

More from the Journal

view all →