Off-the-shelf, low-code or custom software: how to choose

Buy off-the-shelf software when a product already fits your process and your team can work its way. Use a low-code platform when the workflow is simple and someone on your team can own the app. Outside users, several editors or costly errors are reasons to test a product's permissions, client portal and audit trail first. Have software built when the process is your own and the products you tested don't fit. Often the answer is a mix: buy, then connect.

Three terms first. Off-the-shelf software is a finished product you sign up for and set up, rather than have made. When it runs online, it is called software as a service, or SaaS. In NIST's definition, you use the provider's applications without managing the systems they run on. A low-code platform lets you assemble an app from forms, tables and rules, with little or no programming. Custom software is written for your process, and the code can be yours.

We are a development partner that builds the third kind, internal tools and portals, as part of our custom software development work. So read this knowing which column we sit in.

Build or buy software: which fits your situation?

Find the row below that describes your work. Read them in order: each one assumes the rows above it didn't fit.

Most needs are common, so look at buying first

Check whether a product already does the job before you build anything. The UK Government Digital Service put it plainly in a 2021 post on build or buy: "Your project's needs are more likely to be common than unique".

The UK government's purchasing guidance, written for government teams and last updated on 3 Sep 2026, sets out both sides. Buying might be better when "there is a commercially available way to meet most of your user needs". Building might be better when "your user need is unique or rare", or when "you need to own your technology to keep the flexibility to modify it".

The same guidance draws a line worth knowing. Configuration means using the settings a product already offers. Customisation means changing the product itself, with code or workarounds. GOV.UK warns that "even small modifications to OTS software can remove most of the benefits of using it", where OTS means off-the-shelf. Its advice is to configure instead, "so there is still product support when suppliers release new versions".

So if you buy, buy something you can use as it is. If a product only fits after heavy changes, you are paying for it and building around it anyway.

How off-the-shelf, low-code and custom software compare

Judge all three on the same questions, using your real cases.

Low-code you may already pay for

If your business runs on Google Workspace or Microsoft 365, a low-code tool may already be part of what you pay for, with limits worth reading first.

Google's tool is AppSheet, which Google describes as no-code. On 25 Oct 2026, Google's Workspace admin help said AppSheet Core is included for each domain-verified user in most Workspace editions. Included Core rights cover users within the organisation. Check external-user licensing separately before inviting customers or suppliers. An AppSheet app can use a Google Sheet, an Excel file in Office 365 or SharePoint, or a database, among other sources, for its data.

Microsoft's tool is Power Apps, which Microsoft says lets people build business apps without writing code. Microsoft also says you need a licence to run the apps you make. On 25 Oct 2026, its licensing overview said some Microsoft 365 licences include limited Power Apps use rights. Those rights are meant for apps that use Microsoft 365 data and standard connectors. For people outside your organisation, Microsoft's Power Pages is a low-code platform for external-facing business websites, with its own licensing to check.

Before you build, check the current AppSheet plans and Power Apps plans against who will use the app. Other low-code platforms exist; we name these because they come with office suites, not as a recommendation.

Low-code has stopped fitting when only its builder understands it, when no sensible plan covers your users, or when every new rule needs a workaround.

Buying and connecting is often the answer

Often no single product covers the whole job, but two or three together do once they share data. A connector is a ready-made link between two products, such as a store and an accounting tool; where none fits, the connection can be built.

Connecting keeps each product doing what its supplier looks after, and you build only the thin part that is yours. The tools that run these connections are compared in n8n, Zapier or Make.

A built tool can also sit beside the products you keep, rather than replace them. For example, a client portal can read orders from your store and show each client only their own.

If you build, start with one tool

If you build, start with the one tool that removes the daily friction, not everything at once. Software projects go wrong when the scope is a wish list. So settle in writing who the users are, what they do today, what the first release must do, and what waits. A sample first release for a bakery shows what that looks like.

If software was already built for you, a review of the code and setup shows whether it's sound, fixable or better rebuilt. We build web applications that work through the browser, not native mobile apps; see website, web app or mobile app.

Whichever you choose, keep a way out

Whichever path you take, make sure you could leave it.

• Off-the-shelf. Export a full copy of your records now, and open it. You learn what leaving would involve before you need to know.
• Low-code. Keep the data in a sheet or database in the company's account, not in one person's. Write down what each screen and rule does, so someone else can pick it up.
• Custom. The repository, the hosting and the admin logins should be in your name, with credentials in a shared vault.
• Any of them. Put the admin account under a company email address, and give a second person access (which accounts to hold).

Before you commit to a product, also check permissions and connections. Our spreadsheet article has a short list of checks before you buy.

Data in the contract matters too. The UK government's purchasing guidance requires its contracts to be explicit about who owns government data, including data created by running the service. That is a fair question for any supplier. This is general information, not legal advice, so check contract wording with a lawyer.

Next step: tell us what your team does by hand today and which tools it already uses. We'll say whether we would buy, connect or build, and what a first release would hold.

Reviewed and edited by Online Scope before publishing. Something out of date? Tell us at info@onlinescope.in. How we write the Blog.