A client would get their product live, and then ask, “Cool, but how do I see all the users? Or refund an order? Or fix this one record?” And suddenly we were building an admin panel nobody budgeted for.
Now we just use Retool.
Hook it up to Supabase or whatever API the project runs on, and in a day or two the client has a real back office. Tables, filters, buttons that actually do things. When something needs custom logic, we write a bit of JavaScript and move on.
We’ve also started using it for the boring-but-important parts of automation work. A simple screen where someone can see what an AI workflow did, approve it, or retry it when it breaks. Clients love this more than the fancy AI part, honestly.
It’s not magic, and it won’t replace a proper product. But for the stuff only your team will ever see, it’s hard to justify spending weeks on it.
If your ops still run on spreadsheets and “can you check that for me?” messages, that’s usually the sign.
How do you handle a component that needs an intentional exception? I'd want that exception scoped to the component, so the agent doesn't start using it across the app.
For those who haven't checked out the new Agent Templates yet, they come with dedicated AI skills, a Design System page, and video tutorials to help users customize and extend the template using the Framer Agent.
I do my best work when I'm excited about it. This took me under 2h from start to finish. Might have to get more selective about the projects I take on from now on.