Retool and similar platforms are useful because they reduce the cost of building internal software. That does not mean they remove the need for architecture.
The better pattern is to use low-code for the interface and workflow layer while keeping source-of-truth decisions, permissions, service boundaries, and data models explicit. A fast internal tool is only valuable if the team can trust what it reads, what it changes, and who is allowed to use it.
Use low-code where speed matters
Operational dashboards, admin portals, approval queues, CRM-adjacent workflows, exception management, and reporting utilities are often strong fits. These are places where teams need working software more than a heavily custom product surface.
Do not use low-code to hide unclear ownership
Low-code can make fragile systems look finished. If the underlying data is stale, duplicated, poorly permissioned, or unclear, the tool will simply make that confusion easier to access.
The SGS standard
Use the practical tool, but keep the architecture honest. The business should understand the sources, workflows, risks, and handoff points before the tool becomes part of daily operations.