WordPress, a Builder or Custom Code: How to Choose

Short answer: you are not choosing a platform, you are choosing a model. One charges a monthly subscription and keeps the code away from you. One buys a system full of plugins and depends on updates. One hires a person cheaply and leaves you to verify the result. One builds the site for your task and hands over the code and the access. Dearer is not always better; cheaper is not always riskier. Count three years: start, changes, exit. Our registry prices: from $506 (₴21,000) for a ready build, from $699 (₴29,000) for a card with a custom layout, from $1,325 (₴55,000) for a corporate site, from $241 (₴10,000) for targeted fixes to what you already have.

Four models, and how they really differ

Attribute	Builder	Templated CMS	Freelancer	Studio, custom code
Start	weeks	weeks to a month	weeks	2–10 weeks
You pay monthly	platform subscription	hosting, updates, plugins	usually nothing	support under a plan
Who edits content	you	you, if the admin panel is set up	you or the author	you, in the admin panel
Code and structure	yours on their platform, exit limited	third-party theme and plugins	depends on the author	yours, handed over with access
A non-standard feature	hits the builder’s ceiling	a queue of plugins	one person and their time	development inside the project
Speed and search	average, platform-dependent	often lower because of excess	as learned	targeted: LCP, CLS, index

Two questions settle the choice faster than any technology list:

1. How often will you change the site? Once a quarter — a builder or a ready build. Weekly, with prices and stock — you need an admin panel and a sane structure.
2. Do you have logic that is not standard? Booking against a real schedule, staged payments, a client area, 1C sync — none of that is a template job.

Price: count three years, not the first invoice

Builder and platform tariffs change, so we do not quote them here: current figures live on the platforms’ own sites. The difference in cost model is visible without them.

Model	First payment	What you keep paying	Cost of a change
Builder	subscription	monthly, rising with features and traffic	self-service inside the templates
Studio ready build	from $506 (₴21,000), or from $70 (₴2,890)/mo monthly	hosting and support	edits under a plan at from $72 (₴3,000)/mo
Templated CMS	setup work	hosting, updates, plugins, security	depends on who maintains it
Freelancer	the lowest start price	often nothing, until something breaks	one-off, by agreement
Custom code	$699–3,494 (₴29,000–145,000)	support under a plan	inside your own code, no new licences

Worked example with hypothetical figures, to compare models rather than advertise: a site at from $1,325 (₴55,000) with from $72 (₴3,000)/mo monthly support for three years costs about what a “free” builder subscription grows into once you add paid modules for payments, mailings and a real domain. The difference is that in the first case you hold the code and the access; in the second you hold a service that can be switched off.

What stays with you: access, code, domain, content

The real difference between models is ownership, not technology.

• Domain. Registered in your name, with your details. If it sits on the studio’s or the author’s data, a split costs you the address and every backlink behind it.
• Hosting. Your account with the provider, access to the control panel. Someone else’s account is someone else’s infrastructure.
• Admin access. CMS login, roles, integration keys, analytics, the Google profile.
• Code and design. From a builder you take text and images; from a CMS the same plus a licensed theme; from custom code, a repository.
• URL structure. If it changes with the platform, search rankings have to be rebuilt: a 301 map is separate work.

Vendor lock is rarely malice. It is a model: the site lives on someone else’s subscription, the access sits in someone else’s hands, and one person makes every change. Ask one question before paying: “what can I do with this site myself if you disappear”.

When a builder is the right call

A builder fits when it closes the job:

• testing an idea or a direction where a custom layout is not yet worth the money;
• one service with a price, contacts and an enquiry form;
• a two- or three-week campaign where publishing fast is the point;
• no need for booking against a real schedule, payments or a client area.

The limits people discover late: complex URL structures, mobile speed, any logic built into the product, and the fact that exporting a site off the platform does not exist in a usable form.

When a templated CMS: what to check before you buy

WordPress and its relatives give freedom and three accumulating debts at the same time:

1. Updates. Core, theme, plugins — every updatable part can break something. The question is who updates and who fixes it afterwards.
2. Plugins. Ten plugins are ten third-party authors inside your site: speed, security, conflicts.
3. Security. Popular CMS platforms get attacked more often precisely because they are popular: weak passwords, an open admin URL, outdated plugins.

If you choose a CMS deliberately, check: backups with a tested restore, whether the login is closed to extra IPs, whether someone is responsible for updates, and whether anyone measured speed after the plugins went in.

When custom code earns its price

Four situations where writing your own is justified:

Situation	Why a template fails	Our guide
Booking against a real master schedule	you need slot logic and a waiting list	$940–1,181 (₴39,000–49,000)
Staged payments, certificates, a cart	payment flows sit outside widgets	from $1,446 (₴60,000)
CRM, client area, roles, reporting	this is a product, not a visit card	from $3,614 (₴150,000)
Speed and search as a requirement	templates carry excess, edits are expensive	$241–723 (₴10,000–30,000)

Custom code makes sense when the site takes over part of the process: it calculates a price, accepts an enquiry, routes it to an owner, reminds the customer. If the site is a card with a phone number, custom code is not needed.

AI builders: what they speed up and what they do not

Layout and copy generators already save a week of work, and that is real. What they do not do:

• they do not know your prices, services or constraints, so the text needs checking and rewriting;
• they do not integrate with a CRM, payments, 1C or a master’s calendar;
• they do not answer for speed: generated code usually carries excess;
• they do not build for search: headings, URLs, hreflang, sections.

Practical conclusion: AI is a drafting assistant and an idea source for layouts, not a substitute for a project. We use it in our work and in our own tools, but the numbers in the contract and the access at handover remain our responsibility.

How to find out what your site is built on

Five minutes, no specialist needed:

Questions owners ask

If a site already exists and the question is whether to fix it or rebuild, the two routes are compared in the fix-or-rebuild guide, and the difference between a headless CMS and WordPress is in a separate breakdown. Budget your own task in the brief builder; scopes and prices are laid out on the pricing page.