Custom build or WordPress: how to choose

We do not build on WordPress, so you should read this knowing where we stand. That said, we have talked plenty of people out of a custom build, and the rule we use is simple enough to apply yourself: WordPress is good at publishing pages, and it is stretched the moment your site has to hold state — a room that is free, an order in progress, a balance owed.

Updated 19 September 2026

The short version

If your site is pages of information and a contact form, WordPress is probably the right answer and a custom build is overspending.
If your site takes money, holds availability or gives staff a place to work, plugins become the expensive option rather than the cheap one.
Compare the five-year cost, not the build price: licences, maintenance and the hours lost to updates are where the difference actually lives.
Ask who owns the result. A custom build should come with the source code.

When WordPress is the right answer

Genuinely, and we will tell you so:

The site is content

About us, services, news, contact. Nothing on it changes based on who is looking or what they have bought.

Somebody in-house will publish regularly

If you have a person who writes posts weekly, the editing experience matters and WordPress is built for exactly that.

The budget is genuinely small

A good theme, set up carefully, beats a badly scoped custom build every time. Spending your whole budget on a build and none on content is the more common mistake.

You need it next week

Speed to a first version is a real advantage and worth naming.

When it stops being the cheap option

You take money on the site

Payment is the part where correctness matters most and where plugin quality varies most, particularly for Bangladeshi gateways. A booking that takes payment but does not reliably confirm it is worse than no booking system at all.

Something has to be reserved

Rooms, tables, appointments, seats, stock. Anything where two customers must not be able to buy the same thing needs to be right at the moment of the transaction, and that is not what a content system is for.

Your staff need a place to work

Not an admin panel for editing pages — a screen your front desk actually uses, with the permissions and the daily views their job needs. Bending the WordPress admin into this shape is more work than building it.

The thing you need does not exist as a plugin

Once you are commissioning custom plugin development, you are paying custom build prices to work inside somebody else's constraints, which is the worst of both.

You cannot afford an outage

A stack of independently updated plugins has many ways to fail and no single owner. If a Friday evening outage costs you real bookings, that matters more than the licence saving.

The costs people forget on each side

On the WordPress side: premium plugin and theme licences renewing every year, a maintenance arrangement to apply updates safely, better-than-basic hosting once the plugin count climbs, and the hours somebody spends when an update breaks a page. None of these appear in the build quote, and together they are usually the larger number over five years.

On the custom side: it takes longer to reach a first version, you need a developer to change things a plugin would have configured, and if you choose badly you can end up dependent on the firm that built it. Ask for the source code in the contract and ask what the handover includes. We hand over the code, and that is the honest protection against being locked in — not a promise.

A test you can apply in one minute

Write down the three things you most want the site to do. Then, for each one, ask: does the site need to remember something about a specific person or a specific item in order to do it?

If the answer is no for all three, use WordPress and spend the difference on photography and words. If the answer is yes for even one — she has booked room 4 for those two nights, he has paid, that table is taken — you are building software, and it is worth being built as software.

Questions we get asked

Is WordPress insecure?+

WordPress itself is not the problem; the average WordPress installation is. A site running a supported version with few, well-maintained plugins and current PHP is fine. A site with thirty plugins, an abandoned theme and PHP that stopped receiving security fixes years ago is a different proposition, and that describes a great many business sites in Bangladesh.

Can a custom site be edited without a developer?+

The parts that should be editable, yes — we build an admin for the content that genuinely changes. What a custom site does not give you is the ability to restructure a page layout yourself, which is a real trade-off and worth being clear about before you decide.

What about Wix, Squarespace or Shopify?+

Same test. They are excellent at what they are for, and they hit the same wall for the same reason: your business logic has to fit inside their model. Shopify in particular is a strong answer for straightforward retail and a poor one for anything with unusual reservation rules.

How do I find out what my current site runs on?+

Our free website check reports the platform, the server software, the PHP version where it is visible, and whether that version still receives security fixes.

Want this looked at for your own business?

A short call, no charge, and a straight answer about what it would take.

Book a scoping call