The project was an internal operations tool with forms, filters, team-only actions, and a few admin automations. It looked like a straightforward CRUD build until edge cases, permission scope, and deployment friction started showing up.
Report signals
Quick Answer
Built the same internal ops tool in Cursor, Lovable, Bolt, and Replit. The winner changed once the workflow got ugly.
For internal tooling, the right stack depends less on polish and more on how quickly the workflow becomes exception-heavy. The workflow got ugly in exactly the way internal tools usually do: exceptions, permissions, stale states, and operations logic that nobody thinks about in the first sprint. The tool that felt fastest in hour one was not always the one I wanted after the third edge case and fifth partial workaround.
What shipped fast
Replit was more useful than expected because internal tools often live in a messy middle: more code than a pure builder wants, less polish pressure than a public product, and a team that still values browser convenience. Cursor was better when the logic stopped being lightweight.
What broke
The workflow got ugly in exactly the way internal tools usually do: exceptions, permissions, stale states, and operations logic that nobody thinks about in the first sprint. The tool that felt fastest in hour one was not always the one I wanted after the third edge case and fifth partial workaround.
What they would do differently
I would choose the tool based on how messy the ops logic is likely to get, not how good the first generated table or form looks. Internal tooling punishes shallow architecture more slowly, but just as reliably.
Related failure modes
Why builders get stuck at auth and databases
The real reasons auth, RLS, schema design, and database assumptions stall AI-built products.
Read the failure mode ->
Why Stripe, subscriptions, and webhooks break so many AI-built apps
The core failure modes around checkout, webhook drift, stale access state, and subscription logic.
Read the failure mode ->
Why builders get stuck at deployment
Why apps that work locally fall apart at domains, env vars, hosting, and production setup.
Read the failure mode ->
Learn the workflow
With Supabase
The hard part is not connecting Supabase. It is designing the schema, RLS, and auth behavior so the app is safe and understandable under real usage.
Read the workflow ->
An Api
The hard part is not creating endpoints. It is designing the contract, validation, auth, and error handling so the API can survive real usage.
Read the workflow ->
More real builds
The brief was simple: invite clients, show project updates, protect internal notes, and make the product look polished enough to hand off. The real question was which tool kept working once roles, private data, and admin surfaces showed up.
What shipped fast
Lovable was the best first step because the portal needed data, auth, and a client-facing shell immediately. Cursor beca...
What broke
The hard part was never the dashboard UI. It was making sure clients could only see their data, internal notes stayed private, and...
Verdict: Client portals expose the same truth repeatedly: private data and permission logic decide whether the app is real, not the UI.
Read the full build report ->
The test project was the same every time: waitlist, auth, paid plan, gated dashboard, and a small admin surface. The goal was to see which tool stayed useful once money, access, and state drift entered the build.
What shipped fast
Lovable was strongest when the job was full-stack momentum without owning every engineering detail yet. Bolt was useful ...
What broke
Every version looked closer to done than it really was until Stripe and access state got involved. The same project exposed the re...
Verdict: The same app test made the tradeoff obvious: Lovable for fastest credible MVP, Cursor for the version I would trust with money.
Read the full build report ->
An operations team wanted to replace a shared spreadsheet and Slack approvals with a lightweight internal dashboard that handled requests, status changes, and exports.
What shipped fast
Replit made the "single tab, build and host it" workflow simple enough that the team could iterate without extra setup o...
What broke
Permissions, messy edge cases, and data quality were the real problems. The app was useful, but the underlying workflow was uglier...
Verdict: Very good for getting an internal tool into people's hands. Much less convincing as the place you stop thinking.
Read the full build report ->