Slow tools are an architecture problem: keeping internal tools fast as they grow
Multipage design, query optimization, and caching for internal tools that slow down as the team grows. Pillar 3 of internal tools literacy.
Production
All articles, newest first. Page 2
Why your internal tools behave the way they do
Map the workflow logic before you build, or debug it in production. Pillar 1 of internal tools literacy.
Internal tools literacy: what every team should understand about its own tools
Systems logic, integration, performance, and adoption: the four things that decide whether an internal tool keeps working.
Giving a low-code app a real back end with Supabase
Auth, storage, and database logic for a Retool or FlutterFlow app, without writing a custom API.
How to build internal software that still works as the business grows
Architecture choices that keep a Retool app from needing a rebuild every two years.
Why agile works on low-code internal tool builds
Clinic staff asked to see client records across locations. The feature was designed and tested in days.
Low-code or traditional development: which fits your stack?
Total cost, security, lock-in, and a selection matrix you can use on your next build.
Cool demo. Now what? Building production-ready internal tools
From a prototype that works on your machine to a tool IT will sign off.