How to build an internal tool without a dev team

The mistake with internal tools is trying to replace every spreadsheet at once. Pick one repeated workflow with clear inputs, decisions, and outcomes, then generate around that path.

Describe the business process in plain language first. The schema, pages, and roles should follow the work, not the other way around.

Internal apps often fail because everyone sees everything. Before generating, decide who creates records, who approves them, who can edit, and who only needs reporting.

• Give each role a small home view.
• Make status changes visible and reversible.
• Keep audit language simple enough for non-technical operators.

Use explicit tables, readable field names, and predictable status values. The goal is not to impress the database; it is to make the business workflow durable.

Generated code becomes easier to own when the data contract looks like the words your team already uses.

Internal tools improve fastest with real users and short feedback loops. Ship to one small team, watch the stuck points, then ask for precise revisions instead of rebuilding the whole tool.