Where no-code stops and custom development starts

What no-code gets right

No-code platforms let non-developers build working internal tools in days, not months. For approval workflows, simple databases, internal forms and dashboards over existing data, this is often faster and cheaper than any custom build, and it puts the tool in the hands of the people who actually understand the process - no translation through a developer required.

The five real ceilings

1. Data model complexity

No-code platforms are built around a relatively flat, table-based data model. Once your business logic involves genuinely complex relationships - multi-level approvals, conditional logic that varies by dozens of product types, or a data structure that doesn't map cleanly to rows and columns - you'll spend more effort working around the platform's model than it would take to build the right one from scratch.

2. Performance at volume

No-code tools are generally built for moderate data volumes and user counts. Once you're processing large datasets, running complex queries, or supporting hundreds of concurrent users with real-time requirements, performance tends to degrade in ways the platform gives you little control to fix - you're limited to the optimisations the vendor has chosen to expose.

3. Per-seat cost at scale

Almost every no-code platform prices per user. This is fine at ten users and becomes a serious ongoing cost at two hundred. Run the comparison properly - see the five-year cost of per-seat SaaS vs owning your software - before assuming the platform stays the cheap option as headcount grows.

4. Vendor lock-in

Your business logic, built inside a no-code platform's proprietary configuration, generally can't be exported and rebuilt elsewhere. If the vendor raises prices sharply, changes direction, or is acquired and the product is sunset, migrating away means rebuilding, not just moving files. This risk is worth weighing honestly against how central the tool has become to your operation.

5. Auditability

For processes with a genuine compliance or audit requirement - regulated record-keeping, traceability, formal approval trails - no-code platforms vary enormously in what they can prove happened and when. Check specifically, rather than assuming, whether the platform's audit log meets what your regulator or auditor actually expects.

The honest migration path

Businesses that have outgrown no-code rarely need to rebuild everything at once. The usual pattern is identifying the one process hitting a genuine ceiling, scoping that specifically, and leaving the rest of the no-code estate in place where it still works well. See business process mapping for how to identify which process is actually the one worth rebuilding first.

It's also worth reading custom software vs off-the-shelf for the wider framing - no-code is really a third category between the two, with its own trade-offs rather than being strictly better or worse than either.

If you think you've hit one of these ceilings and want a second opinion before committing to a rebuild, get in touch - we'll tell you honestly if the platform still has room left in it.

ISO/IEC 25010, the software quality standard, covers performance efficiency and maintainability as formal quality characteristics - useful background if you want a more rigorous way to assess whether a platform is genuinely at its limit.