I start with how your business works
For years I built mostly on WordPress. Today I choose the technology for the goal, not out of habit. Before deciding, I ask three things: what the website has to do, who will edit it and how it should grow over the next few years.
A website that presents an offer and collects enquiries has different needs from a shop or a course platform with user accounts. A team that publishes one post a month also works differently from a marketing department that adds content every day.
01Choosing a platform
Start with how your business works.
- A company website, landing page or blog
- Astro + panel · Esumo
My default choice: a fast site with no plugins to update, with a Sanity, Payload or EmDash panel.
- A shop, online courses or user accounts
- WordPress · Esumo
A ready ecosystem: WooCommerce, LMS and integrations, with essential tool licences included.
- A portfolio or a new brand website
- Framer
Visual work on layouts and animation, with publishing in one platform.
- Marketing builds new pages on its own
- Webflow
A visual editor and content collections, in exchange for a recurring platform fee.
Compare costs after launch too: subscriptions, maintenance and future changes.
Astro: my default choice for company websites
Astro builds the site from ready-made HTML and sends JavaScript to the browser only where it is really needed. The site loads fast, on phones too, and there are no plugins and no admin panel exposed on the server. Most common vulnerabilities disappear, and the site does not need weekly updates.
For independent editing I connect a content panel chosen for your team: Sanity, Payload or EmDash. You change texts, images, posts and offers in the panel, and the site publishes itself. I set up the panel, so you don't need your own developer. I have demo versions of each of these panels and on a call I show you what everyday work looks like in them.
After launch, the care plan goes into development instead of updates: I analyse analytics data, recommend UX/UI changes and implement them. The site you are reading this on runs on Astro too.
WordPress: when the website needs its own rules
I see WordPress's biggest advantage where you need more than a presentation: sales, user accounts or ready-made extensions. A WooCommerce shop, a course platform on LearnDash or Tutor LMS, a client area or complex forms are areas where its ecosystem saves time and money.
An example: a company starts with its services and case studies. Later it adds a product catalogue, quote requests sent to a CRM and, for part of the offer, sales through WooCommerce. WordPress lets you plan that growth around one website. Each stage still needs design, a quote and testing — installing a plugin does not solve the whole process.
The price of that flexibility is upkeep. Plugins, the theme and WordPress itself need regular updates, backups and security checks. That is why ongoing care matters more on WordPress than on an Astro site. Essential tools such as WPML and ACF PRO are included in the build from my agency licences.
Compare costs and independent editing
With every technology you pay for building the website. The differences start after launch: Framer and Webflow add a recurring platform fee and extra charges, e.g. for more languages. On WordPress you pay for hosting and need regular updates. On Astro hosting is usually cheap, and there is little to update.
01bBudget and everyday work
The build price is only the beginning.
On Astro you pay no platform fee and update no plugins. On WordPress the essential tools are included in the build, but the site needs regular updates. Framer and Webflow mean a recurring subscription.
Scroll horizontally to compare all options →
| What we compare | Astro + CMSCompany websites | WordPressShops and courses | Framer | Webflow |
|---|---|---|---|---|
| Platform subscription | Free Panel: free plan or your own server | Free | 10 / 30 USD Basic / Pro | From USD 25 Premium · CMS |
| Hosting | Static, usually cheap | Your own hosting | Included | Included |
| Plugin updates | Not needed | Regularly as part of care | Handled by the platform | Handled by the platform |
| Another language | No extra licence fee | No extra licence fee | Paid add-on | Each additional language costs extra |
| Everyday editing without a developer | Yes | Yes | Yes | Yes |
| New section types without a developer | No | No | Yes | Yes |
| Ongoing care from your provider | Optional, mostly development | Optional, recommended | Separate service | Separate service |
Framer: when presentation comes first
I would consider Framer for a portfolio, a new brand website or a product presentation. Its strength is visual work on layout, animation and detail. It is a good direction when the person responsible for the design wants to make changes and publish them within one platform.
Framer also has a CMS, so it is not limited to a single landing page. You just need to check whether the editing workflow, the plan and the integrations fit the website, and add the platform fee to the running costs.
I would choose Astro over Framer when the site needs to be fast, easy to move and free of a recurring platform fee. WordPress — when, next to the presentation, you need a catalogue with its own filtering rules or sales.
Webflow: a convenient editor with recurring fees
Webflow is worth considering for a marketing website where the team builds new pages from ready-made elements on its own. CMS collections let you set fields for articles, case studies or job openings, and the designer keeps a lot of control over the look.
That convenience has an ongoing cost. After paying for the design and build, you still pay for the platform, and in Webflow every additional language costs extra.
Astro with a panel offers similar everyday editing without platform fees for more languages or editors. A new type of section then needs a developer, but you build further pages from the prepared sections yourself.
What do you pay for after an Esumo build?
With an Astro site you pay for the domain and hosting, which for a ready-made static site is usually cheap. The panel cost depends on the choice: Sanity has a free plan that is often enough for smaller teams, while Payload and EmDash run on your own server or Cloudflare account, so you mainly pay for hosting.
With WordPress you pay for hosting and the domain, and the essential tools for editing, languages, image optimisation and faster loading are included in the build.
In both cases ongoing care is optional and the plans cost the same. On WordPress the plan mostly covers updates, backups and security. On Astro it includes more hours for development and UX/UI audits. See the care plans.
My recommendation
For a company website, landing page or blog I usually recommend Astro with a content panel: the site is faster, more secure and cheaper to maintain, and your team still edits the content on its own.
For a shop, a course platform or a site with user accounts I recommend WordPress — its ecosystem gives a real edge there. If you already have a working WordPress site, you don't have to move it. We can start with a free review and consider moving to Astro when it pays off.
FAQ
Frequently asked questions
Which platform is best for SEO?
None of them guarantees good rankings. With every option you need to look after content, indexing, URLs, redirects and speed. Astro has an edge in speed, but “we will do SEO” alone is not an argument for one CMS.
Can we change platforms later?
Yes, but it is usually a separate project. You need to plan for rebuilding the design, forms and integrations, keeping URLs or redirects, and testing. A 1:1 migration from WordPress to Astro costs €750–1,290 net, depending on the size of the site.
Does AI change the decision?
AI can speed up writing, design and code. It does not replace decisions about where data is stored, how the team publishes content and who fixes errors. I assess a generated website against the same requirements as any other.
Will we be tied to Esumo?
No. With an Astro site the code and the panel account are yours, and another developer can continue the work. With WordPress you get access to the site and documentation, and at handover we also agree how plugin licences will be handled.