Engineering
Low-code or custom code? A decision guide for agencies
When a Power Platform or ServiceNow app is the right call, when it is not, and how to tell in advance.
Agencies ask this question constantly, and the honest answer is that it depends on the shape of the problem. Here is how we think about it.
Low-code fits when
- The process is a workflow: requests, approvals, assignments, status tracking
- Users are internal staff who already have licenses for the platform
- Data volumes are modest and the data model is simple
- The process changes often and business analysts should be able to adjust it
- Speed matters more than polish
Custom code fits when
- The application is public-facing and must be accessible, fast, and branded
- The data model is complex or the volumes are large
- Integrations are numerous or unusual
- Performance, offline use, or specialized user interfaces matter
- The agency needs to own and move the code without platform lock-in
Questions to ask before deciding
- Who are the users and what devices do they use?
- How many records, and how fast do they grow?
- What must it integrate with, and do those systems have APIs?
- What are the accessibility and privacy obligations?
- Who will maintain it in five years, and what will the licensing cost by then?
The hybrid answer
Many good solutions use both: a low-code workflow for internal processing with a custom, accessible front end for residents, connected through an API. Governance matters either way. Low-code platforms without rules produce hundreds of unmanaged apps holding records nobody tracks.
Our bias
We have built with both and we do not resell either. Our recommendation on any given project comes from the questions above, not from what we would rather build.