← All guides

Adding features to an existing website without a rebuild

Online booking, payments, a members area, a second language, a shop. Most of these can be added to a healthy site in days. Here is what each one needs underneath, and the three cases where adding it is the wrong move.

16 September 2026, 3 min read. From the "can you just add a booking system" messages, which are sometimes a day of work and sometimes a trap.

“Can you just add a booking system?” is a fair question and it deserves a straight answer, which is: usually yes, sometimes quickly, and occasionally it is the wrong thing to do. The difference is what the site is built on, and what the feature needs to do properly.

The features people ask for, and what they need

Online booking. For a single calendar (a clinic, a consultant, a salon with one book) this is a plugin or an embedded service, and a day of work including the styling and the email confirmations. For multiple staff, resources, deposits and rescheduling, it is a system, and the question becomes whether to embed a specialist service or build it in. Embedding is nearly always right.

Taking payments. A one-off payment or a deposit is an afternoon with Stripe or a similar provider. A shop with stock, shipping, tax and refunds is a shop, and it should be built as one, WooCommerce on WordPress or a dedicated platform. Do not bolt a shop onto a brochure site with a plugin that promises to make it easy.

A members area or client portal. Login, protected pages, files per client. The simple version is a week. The real version, where clients have accounts, see their own documents and get notified, is an application and should be planned as one, whether on WordPress or in a framework like Laravel or Next.js.

A second language. On WordPress this is a translation plugin plus, honestly, the translation itself, which is where the work is. It also changes your SEO setup: every page needs its language version linked properly. On a custom site it is a decision made at build time and expensive to retrofit.

Search on the site. Built into most platforms. Making it good, with filters and useful results, is a small project.

A blog or guides section. On WordPress, free, it is what the platform is for. On a site builder, usually fine. On a hand-built static site, this is the feature that most often triggers a rebuild, because you need an editing system you do not have.

Integrations. Connecting the form to your CRM, the bookings to your calendar, the shop to your accounting. Nearly always possible, usually through the tools’ own connections or a service like Make or Zapier, sometimes with a short piece of custom code.

The three cases where adding is wrong

  1. The site is on an old foundation. Adding a booking system to a site with an unsupported PHP version and a theme nobody can update means adding a thing that will break at the next update. Fix the foundation first, or rebuild, then add.
  2. The site builder does not really support it. Builders offer “apps” for most features. Some are good. Many are a widget in a box that does not talk to the rest of the site. If the feature matters to your business, the platform should support it natively.
  3. The feature is the business. If bookings, or the portal, or the shop is what the company does, it should be the centre of the site, not an addition. That is a rebuild with the feature at the heart, and it is a better outcome than a good brochure site with a bolted-on core.

How we approach it

We look at the foundation first, always. If it is healthy, most of the list above is days of work and we quote it as a fixed piece. If it is not, we say so and quote the fix and the feature together. Run the site through the scanner and you will see the foundation the way we see it: the platform, the versions and how old the tech underneath is.

See where your own site stands.

The scanner checks the things this guide talks about, in about ten seconds, no signup.

Tell us about the site.

A straight answer and a fixed quote, usually the same day.