Skip to main content
株式会社オブライト
Business DX2026-11-0914 min read

How to Choose a Website CMS

WordPress, STUDIO, Wix and Headless CMS Compared (for Small Businesses)

Website CMS choice depends on update frequency and who maintains it. We compare WordPress, STUDIO, Wix, headless and agency CMSs on cost, upkeep, switching.


Choosing a CMS for your website comes down to two questions: how often you will update it yourself, and who will handle maintenance. WordPress suits companies that update often and want room to grow. No-code builders such as STUDIO and Wix suit small, design-focused sites where you want to minimize upkeep. A headless CMS with a static site suits companies that value speed and security and can support a more custom setup. A CMS built by your web agency carries a separate risk of lock-in, so it needs careful checking before you sign. This article covers CMS basics, a comparison of four types, easily overlooked costs, contract checkpoints, and a pre-order checklist, without favoring any one product.

Bottom line: which CMS suits which company

When an agency says "let's build it on WordPress" or "STUDIO is enough," it is hard for a business owner to judge whether that is right. Here is a rough guide by situation. The reasons follow in later sections.

- You update news or blog posts often and may later add booking, membership, or multiple languages: WordPress is a strong candidate. Plugins are plentiful and many agencies can support it, but it requires ongoing maintenance
- Your site has few pages, design matters, and you want as little upkeep as possible: a no-code builder such as STUDIO or Wix is a strong candidate. No server management is needed, and editing is usually done on screen
- You prioritize speed and security and can build a custom editing setup: a headless CMS with a static site is an option, though build costs are higher and fewer agencies can do it
- You were offered "our own CMS, cheap and easy": check carefully. There is a risk of lock-in that makes switching providers hard later

No single option is best. The right type depends on update frequency, budget, whether you have an in-house owner, and where the business is heading. The sections below help you decide on that basis.

What a CMS is, in plain terms

A CMS (content management system) lets people without technical skills add and edit the text and images on a website. To post a news item, you type it into a screen much like writing a blog post, with no need to touch code.

Without a CMS, every change goes through the agency, which often means a separate quote each time and a wait of days to weeks. With one, the range of changes you can make yourself widens. But how wide that range is depends heavily on the CMS and on how it was set up. Can you change only text, or also add pages, or even reorder the price table and staff profiles? Confirm this before signing.

Choosing a CMS effectively means deciding three things at once.

- Who updates the site: your staff or the agency
- Who keeps it safe: who handles software updates and fixes problems
- How free you are later: whether you can hand it to another agency or move to another CMS

Comparing the four main types

Here are four typical options for a small or midsize company website. Costs are rough guides that vary widely with scale, features, and who you hire. Service prices can change, so check each provider's official site for current pricing when you evaluate.

ItemWordPressNo-code (STUDIO, Wix, etc.)Headless CMS + static siteAgency-built CMS
Initial cost (rough)About 300K-1.5M JPYAbout 100K-800K JPY (from 0 if self-built)About 800K-3M JPYAbout 300K-2M JPY
Monthly cost (rough)Server and maintenance, a few thousand to tens of thousands of JPYPlan fee, from a few thousand JPYA few thousand to tens of thousands of JPY (CMS and hosting)A few thousand to tens of thousands of JPY, billed as maintenance
Ease of updatingEasy once learned; the screen can feel crowdedWhat-you-see-is-what-you-get editing, easy to followFriendly if the input fields are well designedDepends on design; features often limited
ExtensibilityVery high (plugins and themes)Within the service's featuresHigh (custom design)Depends on the vendor's development
Security upkeep effortHigh (core and plugin updates are mandatory)Low (the provider manages it)Low (small attack surface on the public side)Depends on the vendor; often opaque
Ease of switching awayRelatively easy (data can be exported)Harder (moving the same look usually means a rebuild)Moderate (content data moves easily)Hard (prone to lock-in)

The initial costs assume anything from a few-page company profile site to roughly a dozen pages; adding booking or membership features raises them. Our overview of total build costs is in homepage production cost guide.

WordPress: very flexible, but it needs upkeep

WordPress is an open-source CMS used widely around the world. The software itself is free, but you also need a server, a design theme, and plugins that add features, which are typically separate.

Who it suits: companies that keep updating blogs, news, or case studies; those expecting to add features later, such as expanded inquiry fields, multiple languages, booking, or membership; and those who value having many local agencies able to support it. Because so many people use it, finding information and vendors when something breaks is easy.

What to watch: security maintenance. The WordPress core, themes, and plugins are updated regularly, and those updates include fixes for vulnerabilities. Neglecting them can lead to unauthorized access or tampering, and WordPress's popularity makes it a frequent target. The classic failure pattern is launching without deciding who will do maintenance, how often, and at what cost. We cover specific risks and countermeasures in risks of neglecting WordPress maintenance.

Installing too many plugins can also slow the site and cause conflicts during updates. Being able to add features does not mean you should add everything; keeping the set minimal is part of good design.

No-code builders (STUDIO, Wix, etc.): easy, but you depend on the service

No-code services such as STUDIO, Wix, and Jimdo let you go from design to publishing on screen. The provider handles servers and software updates, so operations are light. Many offer high design freedom and suit small company profile sites and landing pages (single-page ad pages).

Who it suits: companies with few pages, those who want design to make the impression, those without an in-house engineer who want minimal upkeep, and those who want to start small and see how it goes. You can build it yourself or have an agency do only the build, which keeps initial costs low.

What to watch: you can only build within the service's features, and switching later is hard. Text and images can usually be exported, but the design and structure rarely carry over to another CMS, so a move tends to mean a rebuild. Plan fees can also be revised by the provider, and using your own domain or adding features may require a higher plan. Before signing, check domain conditions, form and search-optimization features, and monthly or annual plan fees on the official site.

Headless CMS + static site: fast and safe, but it takes engineering

A headless CMS (such as microCMS) provides only the part where you enter and manage text and images. The visible website is built separately and pulls content from the CMS when needed. It is often paired with a static site, pre-generated as HTML, which loads quickly and has fewer server-side weak points, making it easier to keep secure.

Who it suits: companies that value speed and security, those running large volumes of content such as columns or case studies, and those who want to grow the site as a long-term asset. Because the editing screen can be designed freely, it fits workflows like "we only need to update this one field on this page."

What to watch: build costs tend to be higher and fewer agencies can do the work. The front end requires development, so there is no quick "pick a theme and finish" path like WordPress. The CMS service also has pricing tiers, and larger data volumes or more users may require a higher plan. Decide up front who handles problems.

Agency-built CMS: the type that most needs checking

Some agencies develop their own CMS and offer it to clients. Done well, it can be pared down to the needed features, inexpensive, and easy to understand. The biggest risk, however, is that the CMS works only with that one company. When you want to cancel, you may find you cannot take the site with you, cannot export the data, or are quoted a high migration fee.

An agency CMS is not automatically bad. If you adopt one, make sure the checkpoints in a later section are confirmed in writing before you sign.

Costs that are easy to overlook

People tend to focus on initial cost, but over several years these items add up. When comparing quotes, check whether each is included.

- Server and domain fees: typically a few thousand to tens of thousands of JPY per year for WordPress and agency CMSs. No-code services usually include them in the plan fee
- Theme and plugin licenses: paid themes and plugins may be one-time purchases or annual renewals. If you stop renewing, updates and support may end
- Maintenance: core and plugin updates, backups, and fixes. Especially important for WordPress, ranging from a few thousand to tens of thousands of JPY a month. See homepage maintenance cost guide
- Plan fee changes: no-code and headless services may revise pricing at the provider's discretion, so future costs may differ from today's
- Feature additions and design changes: changes beyond what you can edit yourself require a separate quote
- Migration and renewal: rebuild costs, data migration, and URL carry-over (redirect setup) if you later move to another CMS

A plan that looks cheap monthly can diverge over 5 or 10 years. Comparing "initial cost + five years of monthly fees + expected update and migration costs" makes the decision easier.

Agency CMS and lock-in: risks and what to check in the contract

It is not rare for a company to hand everything to an agency and discover only at cancellation or switching time that the data cannot be taken out. Pitfalls of monthly-fee contracts are covered in pitfalls of subscription website contracts, and the practical steps for switching are in guide to switching web agencies. Before signing, confirm at least the following.

- Domain registrant: is it registered and managed in your company's name? If it is the agency's, you will need a procedure to take it back at cancellation
- Ownership and export of site data: can you receive text, images, and page structure when you cancel? In what format (CSV, XML, HTML) and at what cost?
- Copyright: who owns the design and text, and is it stated in the contract?
- Admin account: can your company hold administrator rights?
- Minimum term and cancellation terms: notice deadlines, penalties, remaining balances
- Breakdown of monthly fees: which of server, maintenance, CMS usage, and update work are included?
- If the CMS ends: what happens if the provider stops business or the service is discontinued?

Do not rely on verbal explanations. Have them written into the quote, contract, or specification. Anything that cannot be put in writing is safer treated as not promised.

Key points of the decision flow

Here is the order to follow when you are unsure.

1. Set update frequency: several times a month or only a few fixes a year? If often, prioritize ease of editing and extensibility
2. Decide who updates: your staff or the agency? If you, try the screen yourself first
3. Decide who maintains: you, the agency, or the provider? WordPress requires a clear owner
4. Anticipate future features: will you need booking, membership, multiple languages, or e-commerce within 1-3 years? If so, consider WordPress or a headless CMS
5. Compare total cost: line up initial cost, five years of monthly fees, update costs, and migration costs
6. Check the exit: confirm before signing that you can take your data out when you cancel or switch

Pre-order checklist

Items to confirm before commissioning, or when you receive a proposal. If you can answer all of them, you can judge the proposal on its merits.

- [ ] I listed what I want to update (news, case studies, staff profiles, price tables, etc.)
- [ ] I decided who updates and how often
- [ ] I had the proposed CMS and the reason for choosing it explained
- [ ] I asked why this CMS and not the alternatives
- [ ] I checked the breakdown of monthly and annual fees, not just the initial cost
- [ ] I compared quotes on a five-year total
- [ ] For WordPress, I decided who does core and plugin updates and backups
- [ ] I confirmed the domain and server are registered in our company's name
- [ ] I confirmed whether site data can be taken out at cancellation, and at what cost
- [ ] Copyright ownership is stated in the contract
- [ ] Our company can hold the admin account
- [ ] I checked the minimum term, cancellation terms, and penalties
- [ ] I checked the latest plan fees on the service's official site

FAQ

WordPress or STUDIO: which should I choose?

It depends on update frequency and who handles maintenance. If you update a blog or news often and expect to add features, WordPress fits. If you have few pages, value design, and want less upkeep, a no-code builder like STUDIO fits. Each has a trade-off: WordPress needs maintenance, while no-code builders mean dependence on the service and harder migration. If unsure, compare the five-year total and how easily you could switch later.

Is WordPress dangerous and best avoided?

No need to avoid it, but it assumes you can keep up with updates to the core, themes, and plugins, plus backups. Its popularity makes it a frequent target, and neglecting updates raises the risk of tampering. If you decide who handles maintenance first, it remains a strong option.

Can I move a no-code site to WordPress later?

Text and images can usually be exported, but the design and structure rarely move as is, so it often means a rebuild. If you expect to move, doing so before the page count grows keeps costs lower. Whether and how you can migrate depends on the service's specifications.

Is a headless CMS suitable for small and midsize companies?

Some companies fit, but overall they are a minority. It is strong for those who value speed and security, run columns or case studies continuously, or want a long-term asset. Because build costs are higher and fewer agencies can do it, WordPress or a no-code builder often gives better value for a small company profile site.

Should I refuse an agency's own CMS?

Not necessarily, but pre-contract checks are essential. Confirm in writing the domain registrant, whether and at what cost data can be exported, copyright ownership, and the minimum term and cancellation terms. If the agency cannot answer these clearly, think twice.

How much should I budget for plugins and themes?

It varies widely: some sites get by with free ones, others use several paid ones. Since some are one-time purchases and others renew annually, ask the agency for a list of paid components, their prices, and whether renewal is required.

Should I be able to update the website myself?

For frequent changes such as text swaps and news posts, doing it in-house saves cost and time. You need not do everything yourself, though. Decide at the start which work stays with you and which goes to the agency.

Feel free to contact us

Contact Us