How I Ship an Internal Tool in a Day With Replit AI (That Survives Week Two)

Internal tools have a brutal survival curve: the prototype dazzles on Friday, and by the second Monday it is a spreadsheet again, because the boring parts, who can edit what, what happens when two people save at once, were never built. My rule now is that anything meant to survive gets built in Replit with a real database from hour one, and a working day is enough if you spend it on the boring parts first.

Morning one, hour one: the schema, not the screens. Write down the entities and who touches them, then set up the database in Replit before generating any interface, because the agent builds dramatically better interfaces against a real schema than against vibes. For my leave-request tool this was twenty minutes: requests, employees, statuses, and the constraint that killed the previous spreadsheet version, one active request per person per date range.

Hours two through four belong to auth and permissions, in that order, because this is exactly where demo-grade tools die. Replit's built-in auth gets you sign-in fast, but the work that matters is the permission logic, who can approve, who can edit whose records, and testing it with a second account before building on top of it. The agent implements your rules fine; it cannot know that the intern should not see salary fields unless your schema and prompts say so out loud.

The afternoon is features, and the discipline is shipping the smallest version that removes the pain. List every feature the stakeholders mentioned, cross out all but the two that would cause someone to abandon the tool, and build those with the agent, testing each flow as it lands. Everything else goes on a list labeled version two, which is a gift to your future self, because a tool in use with a roadmap beats a complete tool nobody adopted.

Before five, the survival checklist: real data migrated or entering, a weekly backup of the database, error logging you actually check, and a single place where people report problems, even a channel in chat. Deploy it, walk one real user through their first task, and watch without helping. Whatever they stumble on is Monday's fix list, and the fact that there is a Monday, with the tool still running and logs to read, is the difference between building software and shipping a demo.