No-code or custom software: which should you choose?

Start with no-code or ready-made tools if…

• The process is standard. Bookings, sign-up forms, simple lists and contact databases are well served by existing products.
• Only a handful of people use it. Per-user pricing stays low, and training is easy.
• You're still working out how it should work. No-code is quick to change. It's a good way to test an idea before spending more.

Consider custom when…

• You're paying for several tools and gluing them together by hand. A form in one, a spreadsheet in another, emails sent from a third, with someone copying between them.
• Per-user fees keep climbing. Every new volunteer or member of staff adds to the monthly bill.
• Your rules don't fit any template. Different rates for different hirers, approval steps, or eligibility checks that you currently handle by hand.
• You want it to feel like yours. Your name, your look, one place for people to go.

A worked example: per-user fees

An illustrative example with made-up prices. A charity uses a no-code tool at £10 per user per month. With 4 staff, that's £40 a month, or £480 a year. Very reasonable.

Then it adds 12 volunteer co-ordinators who need access. Now it's 16 users: £160 a month, or £1,920 a year, and it rises again with every new person.

Add a second tool for rota reminders at a similar per-user price and the total can easily double again.

At that point it's worth comparing against a one-off build plus hosting and support over, say, three years. Sometimes the no-code tool still wins. Sometimes it doesn't. The point is to do the sum rather than assume.

Questions to ask about any tool

1. What will it cost with twice as many users as today?
2. Can we export all our data in a standard format, like CSV?
3. Where is the data stored, and is there a data processing agreement? UK GDPR requires a contract with anyone who processes personal data on your behalf.
4. Can we turn on two-step verification for every login? The NCSC calls it one of the most effective ways to protect online accounts.
5. Who in our organisation knows how it's set up?

The common path

Plenty of good systems start as a spreadsheet, move to a no-code tool, and only later become custom. That's not wasted effort. Each stage teaches you what you actually need, and by the time you build something, you can describe it precisely.

Common mistakes to avoid:

• Building custom before you know how the process should work.
• Staying on no-code long after the workarounds take more time than the tool saves.
• Letting one enthusiastic volunteer build something nobody else understands.

If you're at the point of weighing up a build, our app cost calculator gives a rough figure to compare against your current subscriptions.

Sources

• ICO: when is a controller-processor contract needed
• NCSC: turn on 2-step verification

Related

• App cost calculator
• MVP development
• How much does an app cost in the UK

← Who owns your app's code? It isn't always youGDPR for online bookings: the basics for small organisations →