WordPress or custom software? Five questions to decide

We write this as an agency that builds custom software, and that is worth saying first. We do not build WordPress sites; all our work, brochure sites included, is custom software. Our answer is still not always "custom": for many businesses WordPress is the right and more economical choice. The table and questions below are there so you can see for yourself which one fits.

When we recommend WordPress

• The site's job is to present: services, about, contact, a blog.
• Content will be updated often and by different people; a familiar admin matters.
• Budget and time are limited; launching quickly is the priority.
• Your need is met by a single well-known, maintained plugin.

In these cases, paying for custom software means paying for flexibility you will not use.

Choosing WordPress does not mean taking the job lightly. A WordPress site built with a good theme, few and maintained plugins, regular updates and backups can serve a business well for years. The rest of this article also covers what such a good build pays attention to.

When custom software pulls ahead

At Demiralp Tur and Brayas Travel, the needs that took the work to custom software were these: the site had to run the business, not just present it.

• A booking flow and instant price calculation (Demiralp Tur).
• Agency commission and a sub-manager structure (Demiralp Tur).
• Membership, magic-link sign-in, coupons and loyalty (Brayas Travel).
• A six-step booking flow in three languages that shows the price inside the flow (Brayas Travel).

A WordPress plugin can be found for each of these. But if all of them have to work together on one site, each plugin brings its own logic, its own update schedule and its own security history. Our view: when the rules of the business live inside the site, writing those rules directly asks for fewer compromises over time.

Security and maintenance: what do the numbers say?

In WordPress, the security load is carried less by the core than by the plugins and themes around it. According to the 2026 report by Patchstack, a company that works on WordPress security, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025 — a 42% increase on the previous year. 91% of them were in plugins and 9% in themes; the WordPress core had only six, all of them low priority.

That does not mean WordPress is insecure. It means that the update and monitoring load grows with the number of plugins, so a site built with few plugins and updated regularly carries less risk. With custom software that load does not disappear; it moves: keeping the code and the libraries it uses up to date is the developer's job.

Speed: the build matters more than the platform

"WordPress is slow, custom software is fast" is not true; both are as fast as they are built. We learned this on our own site, which is custom software. In September 2026, in our mobile lab measurement that simulates a slow phone, the heading of our SEO service page took 5.8 seconds to appear. The cause was not the platform but a design decision: the heading's entrance animation did not start until the page's JavaScript had downloaded and run, and the heading stayed invisible until then. After a fix that moved the heading's animation into the browser's own CSS, the same measurement came down to 2.4 seconds. On WordPress, a heavy theme or an unnecessary plugin can cause the same delay.

Does it matter for AI search?

It does, but because of how the page is produced, not the platform. According to a measurement Vercel and MERJ published in December 2024, the crawlers of OpenAI, Anthropic and Perplexity did not execute JavaScript. WordPress produces pages on the server by default, so the text arrives in the first HTML. With custom software this is a choice: a site that builds its text later in the browser with JavaScript can show up in Google and still reach these crawlers incomplete or empty. If you commission custom software, ask whether the text is generated on the server. On our site it is.

Cost: which items are there?

We give no figures here; we will publish our price bands separately. But the two routes are made of different cost items, and the comparison has to be made on those items.

• WordPress: hosting, theme and paid plugin licences (many renew yearly), setup and design, updates and security monitoring.
• Custom software: design and development (the larger item up front), hosting, maintenance and development support.

Compare over three years, not on the first invoice: plugin licences and maintenance hours build up over time with WordPress, development support with custom software.

Moving from one to the other

The riskiest part of a move is search visibility. For a site move with URL changes, Google recommends server-side permanent redirects (301 or 308) and keeping them for as long as possible, generally at least a year. Redirecting every old address to its new one is the step a move cannot skip.

1. 1.List every address of the old site (the sitemap and the pages in Search Console).
2. 2.Write the new address for each old one; send those without a match to the closest page.
3. 3.Carry titles, descriptions and structured data over to the new site.
4. 4.After launch, try the old addresses one by one and confirm none returns a 404.
5. 5.In the following weeks, watch the pages report in Search Console; you will catch dropped or failing addresses early.

If you choose WordPress: picking plugins

Because most of the security load on the WordPress route sits in plugins, choosing them is one of the important decisions of a build. Before adding a plugin, check:

• The last-updated date on its WordPress.org page: a plugin not updated for a long time may no longer be maintained.
• Active installations and user reviews: not a guarantee on their own, but a signal.
• A second plugin that does the same job: do not install it; every plugin means another update and security check to follow.
• A plugin you no longer use: do not just deactivate it, delete it.

A middle way: content in WordPress, a custom site

The two routes can also be combined: content is managed in WordPress's familiar admin, while the site visitors see is written separately and custom; this is called a "headless" setup. The content team keeps the admin it knows, and the site escapes the plugin load. In return there are two systems to maintain. We do not recommend it for a small brochure site; it is worth considering for businesses with a lot of content and a team used to WordPress that want a custom flow on the site.

Ask when you get a quote

• Which theme and plugins will be used? Whose name are the paid licences in, and when do they renew?
• For custom software, which technology is the code written in, and where will the code repository live?
• After the first year, what does maintenance cover: updates, backups, small changes?
• If you are moving from an old site, are the address redirects included in the quote?
• Does the pages' text arrive in the first HTML?

Whichever you choose: at handover

• The domain is registered in your name.
• You have access to the hosting account, the admin and, for custom software, the code repository.
• You know where backups are kept and how they are restored.
• Who updates what, and how often, is written down.

On the sites we build, the domain, the content and the site belong to the client; any client who asks gets access to the domain, the content and the code at handover, so you are not locked in.

If you need a multilingual site

On WordPress a multilingual site is usually built with a translation plugin; with custom software the languages are designed into the code from the start. Our own site is bilingual: Turkish at the main address, English under /en, and every language version has its own address. Brayas Travel's booking flow works in three languages. On both routes the real work is the same: keeping translations complete and marking each language version correctly for search engines (hreflang).

Three examples

These are not our clients; they are examples of how the decision is made:

• A single-branch dental clinic: services, dentists, contact and a blog; appointments by phone or through a ready-made booking tool. WordPress is enough.
• A boutique hotel that takes bookings through a ready-made hotel booking system: the site's job is to present the hotel and send guests to that system. WordPress is enough; custom software would mean rewriting a system you already use.
• A transfer company that works with agencies and prices each trip instantly by its own rules: the rules are the business. Custom software is worth a conversation; that was the need we met at Demiralp Tur.

Five questions to decide

1. 1.What will the site do: present the business, or take business (bookings, sales, memberships)?
2. 2.Do your pricing or flow rules fit within the settings a plugin offers?
3. 3.Who will update the content, and how often?
4. 4.Who will maintain it: your team, or an agency?
5. 5.What will the site be doing in three years?

If the answers to the first two are "present" and "yes, they fit", start with WordPress. If not, custom software is worth a conversation.