Skip to content

Custom software vs off-the-shelf: what building our own website taught us

13 Nov 2026

·

7 minute read

Buy off-the-shelf software when your process is the same as everyone else's. Build custom software when the process is part of what makes you different, when your integrations or data rules are unusual, or when owning the change cycle matters more than starting fast. We build custom software for a living, so it would be easy to tell you to always build. Instead, here is what happened when we built our own website and CMS from scratch, including the parts that cost us, and the test we would use if we were deciding again.

What we built, and what it cost

This site is not a website-builder template. It is a server-rendered application with its own content management system, and both went live on the same day, 15 August 2026. Since then it has taken around ninety commits over ten working days.

The first cost arrived within two days. Our host treats a project as a static website unless it is told otherwise, and served the build as plain files, which returned a 403 error on every page. Running it as a live Node application meant learning three rules the hard way: an entry file has to be configured, it has to be in the older CommonJS module format because the host loads it in a way the modern format breaks, and it has to sit in the root folder or the host reports a failed build with a log that looks perfectly clean. Those three facts now sit in our README under a heading about the settings that actually work. A website builder would have spared us all of it.

The second cost is quieter and more instructive. Our CMS stores edited content separately from the code, and saved content wins. That is the right design for people editing the site, but it means a change to an existing page made in code may never reach the live site, because an older saved copy overrides it. We now carry migration code that recognises old titles and descriptions and swaps in new ones, and we add new blog posts by appending them rather than replacing the list. Every custom system has a few rules like this, and someone has to remember them.

The third cost is maintenance. In September our host's security scan flagged vulnerable dependencies, and patching them was our job. With a hosted product, the vendor does that.

What it bought us

The same decision gave us things a template would not.

Our blog runs through a publishing pipeline that lives in the same repository as the site. Topics wait in a backlog until we approve them, every draft passes an automated quality check before it can be merged, and merging is the publish button. Search and AI engines read structured data generated from the same content the reader sees, so the two never drift apart. When we want to change how a page works, we change it, without waiting for a vendor's roadmap.

Whether that was worth the cost depends on what you value. For a company whose work is building software, a site that doubles as a working example of how we build is worth a few lost days. For a bakery, it would not be.

When is off-the-shelf software the better choice?

Buy when the process is standard and a product already does it well. Accounting, payroll, email, document storage and video calls are solved problems. Building your own means paying to recreate them and then maintaining them indefinitely, which is the third cost above, repeated every month.

The UK government's Technology Code of Practice, written for public bodies, makes a good checklist for anyone. It asks teams to "find out whether government has already solved this problem" before building something new, which for a business means checking for an existing product, an open-source project or a shared service first. It also asks teams to "consider using public cloud solutions first" and to prefer open source and open standards, which keeps the cost of switching later low.

When should you build custom software?

Build when at least one of these is true:

  • The process is your advantage, and a product would make you work like your competitors.
  • You must connect to systems no product supports: a legacy database, a government portal, specialised equipment.
  • Your data rules are strict about where data lives, who can see it, or how it behaves without a connection.
  • You will change the software often, and waiting on a vendor would cost more than maintaining it yourself.

If you build, make sure you own what you pay for. In India, a software company owns the code it writes unless the contract assigns it to you in writing; our guide on who owns the code covers the clauses.

The middle option most comparisons skip

Many organisations do best with a product that covers most of the work, configured for their needs, plus custom integrations around it. You start faster than a full build and fit better than an unmodified product. The custom part stays small enough to maintain.

The costs that hit both options

On the projects we take on, four things move the cost more than anything else, and they apply to bought software as much as to built software:

  1. Integrations with the systems you already run, such as payment gateways, existing records systems or government portals
  2. Compliance: data protection obligations, where data must be stored, and audit requirements
  3. Data migration, moving years of records out of the old system, which usually need cleaning first
  4. The number of people who must approve each decision

A product that needs heavy integration and a large migration can cost more in its first year than a focused custom build. Price both options with these four included. The code of practice puts it plainly for public bodies: a purchasing strategy "must show you've considered commercial and technology aspects, and contractual limitations."

A test for your own decision

Answer yes or no:

  1. Does a product already do most of what you need, the way you want to do it?
  2. Is the process standard across your industry?
  3. Can the product connect to every system you need, with features it already has?
  4. Do its data storage and access rules meet your obligations?
  5. Can you export all your data if you leave?
  6. Do you have someone who will own a custom system's quirks and maintenance for years?

Mostly yes to the first five points to buying. Mostly no, with a yes to the sixth, points to building. A yes to the first and a no to the third points to the middle option. If you build, match the contract to how clear the scope is; our guide to fixed price vs time and materials covers that choice.

Frequently asked questions

What is off-the-shelf software?

Off-the-shelf software is a ready-made product sold to many organisations, such as an accounting package, a CRM or a website builder, which you set up and configure rather than build. It is also called packaged or commercial off-the-shelf (COTS) software. You can start using it quickly, and in exchange you share its roadmap and its limits with every other customer. Custom software is built for one organisation's process and is owned by that organisation.

Is custom software more expensive than off-the-shelf?

Upfront, usually. Over several years it depends on subscription fees, integration work, data migration and maintenance. Compare the total over the period you expect to use the system.

What is the biggest hidden cost of custom software?

Maintenance and the system's own rules: hosting quirks, security patches and behaviour that someone has to remember. Plan who owns them before you build.

Can I start with off-the-shelf software and build later?

Yes, if the product lets you export all your data in a standard format. Check that before you sign.

If you are weighing a product against a custom build, send us your requirements and we will tell you which route we would take, including when the answer is to buy.

AI tools

Ask ChatGPTAsk Claude

Start with the problem that matters