Bespoke or an existing system: where the line runs

Well-known content systems are designed for the most common case: pages, news items, forms, possibly products. That part already exists, has been tested thousands of times, and there are people around who can work with it. Anyone who needs an ordinary company site gets years of development work for free.

The price you pay is maintenance and excess weight. A system that wants to do everything for everyone drags along features you never use, and every extension you install is a piece of third-party software that has to be kept up to date. Letting that slide is the biggest risk in this field: an outdated installation that gets found automatically.

There is also a limit to what such a system does comfortably. As soon as you want something it does not know — your own price calculation, an integration that works differently, a screen that deviates — you start building exceptions on top of something not meant for them. That works, until the next update.

Bespoke is worth it as soon as the process itself is the product. A configurator that calculates price from dimensions and materials, a schedule that accounts for who drives where, a portal where clients see their own file: those are things you do not ask an existing system for, you build them.

The second reason is speed and manageability. Without dozens of extensions there is less to keep up to date, less that can break and less that gets loaded needlessly. For sites where speed directly costs or earns money, that weighs heavily.

The third is ownership. With bespoke work the code is yours and another developer can take it over, provided documentation comes with it. That is exactly why the question 'can somebody else continue with this?' matters more than the name of the tool.

Between those two sits a third route: the content in a system meant only for that, and the site itself built bespoke on top. You keep a comfortable admin environment, but the pages are exactly what you want and can be pre-rendered.

That setup has another advantage that only shows later: the same content can also feed an app, a screen in the shop or an export to a marketplace. You maintain it once.

Which of the three routes is right depends on how much you want to be able to do yourself, how much deviates from the ordinary, and how long the site or app has to last. That is a judgement per project — not a fixed preference.