What is visibility debt? When nobody can see how the work gets done
The process runs. Nobody can tell you where it stalls, or why.
Production
Questions this topic answers
- how much does it cost to build an internal tool
- how to keep a team using an internal tool after launch
- how to take an internal tool prototype to production
- how to use Supabase as the back end for a Retool app
- what is internal tools literacy
- what to decide before building an internal tool
- who maintains an internal tool after launch
- why do internal tools become production risks
- why do internal tools fail
- why is my Retool app slow
Explainer
13 articles
Why internal tools become production risks
A tool built as a side project ends up running a core process, with no access control, no audit log, and no owner.
A one-line change should not take three weeks
When a small change to an internal tool takes weeks, the cause is usually architecture: coupled queries, scattered logic, and no shared data model.
What it costs to build a production-ready internal tool
Screen count barely moves the price. Scope, integrations, access rules, and audit requirements do.
Four controls that make an internal tool safe to rely on
Access control, audit trails, separate environments, and change management, and what each one prevents.
The tool was free to build. Maintaining it is not.
Why internal tools built in-house get hard to change, and the design choices that keep them cheap to maintain.
How-to
5 articles
A pre-build checklist for internal tools that have to last
Six questions to answer before anyone opens the editor.
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.
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.
Cool demo. Now what? Building production-ready internal tools
From a prototype that works on your machine to a tool IT will sign off.
Comparison
2 articles
Which providers deliver maintained, production-ready internal tools?
Compare providers on what happens after launch: maintenance, ownership, and who answers when it breaks.
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.