When should a business use low-code instead of custom development?
Use low-code for stable workflows when supported connectors, data volume, permissions, performance, release governance, and exit can all be proven. Prefer custom development for differentiated transactions, complex tenants and access, real-time device control, or strict portability. Many systems are best as a hybrid. Wavesteam should test the alternatives on real client work and deliver a recommendation and exit conditions rather than asking the client to compare feature lists.
| Route | Best conditions | Benefit | Accepted trade-off | Exit trigger |
|---|---|---|---|---|
| Low/no-code | Stable rules, supported connectors, tested queries and access | Fast forms and prototypes; operators can configure | Recurring licenses, quotas, expression limits, vendor roadmap | A critical task fails, TCO grows beyond value, or complete export is impossible |
| Custom | Differentiated core workflow, deep integration, devices, or granular control | Designed behavior, model, experience, and evolution | Greater engineering, test, security, and operating cost | Differentiation no longer repays maintenance |
| Hybrid | Stable core transactions with fast-changing approvals and operations | Controlled system of record plus rapid peripheral change | More identity, synchronization, ownership, and API complexity | Duplicate sources and integration cost erase savings |
When comparing platform capabilities, constraints, and switching costs, also compare What should be assessed before rebuilding a slow, insecure on-premises system in the cloud? and How can a project control cost across iOS, Android, and a WeChat mini-program?; the linked guidance adds context that should be considered in the same decision.
Internal does not mean simple, and customer-facing does not mean custom. Wavesteam extracts critical tasks covering the main journey, hardest permissions, largest data shape, and costly failures. Each is classified as native configuration, formula, connector, external service, or not reliable. Completion of many trivial screens cannot offset one wrong order amount.
Tests use production-like data and identities. Microsoft documents that a non-delegable Power Apps query processes only the first 500 records locally by default, configurable to 2,000, potentially returning incomplete but plausible results in a larger dataset; see its delegation guidance. Other platforms have different boundaries, which is precisely why a demo is not sufficient.
Measure critical-task success, P50/P95 latency and errors at agreed load and network, administrator effort, release and rollback, and time to export users, master data, files, workflows, and audit. Manual workarounds enter lifecycle cost. Compare licenses, connectors, storage, API/automation quotas, environments, identity, backup, monitoring, administration, external development, and migration against custom engineering, infrastructure, upgrades, support, and handover under the same growth and service assumptions.
Perform an exit exercise: export structured data and attachments, rebuild one key workflow independently, and record missing metadata, access history, and formulas. CSV export alone does not make pages, identity, and workflows portable. Contract for export format, frequency, post-termination retention, owner account, and transition fees.
Low-code still requires development/test/production separation, versioning, release approval, rollback, audit, and least privilege. Microsoft's Power Platform ALM guidance covers requirements through CI/CD, deployment, governance, and maintenance. Wavesteam recommends low-code when all critical tasks pass at production scale, lifecycle cost is acceptable, and exit succeeds. If a core task reaches a hard limit, move it to a controlled API, hybrid, or custom design rather than hiding it behind permanent manual work.