(Biased due to me leading the DevRel team at Retool, that said...)
I've recently been a big fan of Claude Code for building lots of these kinds of tools, but then I always ran into the "what now" problem. Our IT team certainly wasn't going to just deploy my randomly-built tool and give it access to our systems, so there was a whole other process to go through to get the things I was building out to the team.
That's basically solved with Retool, because all the resources and data connections are already provisioned and can be centrally managed and governed. By the time I have an app built, it's already built on top of our existing permissioning structure and I can deploy it to the whole team.
With the tooling we launched today, I'll actually find myself starting in Claude Code, sketching out what we're going to be building and having CC go into my Retool account (via MCP) to find what data I actually have available, before deploying the whole thing onto Retool at the very end.
To me, that's still a flow that's going to work in 2027!
I've recently been a big fan of Claude Code for building lots of these kinds of tools, but then I always ran into the "what now" problem. Our IT team certainly wasn't going to just deploy my randomly-built tool and give it access to our systems, so there was a whole other process to go through to get the things I was building out to the team.
That's basically solved with Retool, because all the resources and data connections are already provisioned and can be centrally managed and governed. By the time I have an app built, it's already built on top of our existing permissioning structure and I can deploy it to the whole team.
With the tooling we launched today, I'll actually find myself starting in Claude Code, sketching out what we're going to be building and having CC go into my Retool account (via MCP) to find what data I actually have available, before deploying the whole thing onto Retool at the very end.
To me, that's still a flow that's going to work in 2027!