I found - the most effective way to get business and operations team use your application
As an engineer, it always hurts seeing teammates not use a product you built to make their lives easier.
But I started looking at it from their side.
UI, dashboards, tables, filters, workflows, interfaces — all of it can feel intimidating. Even if your product is objectively better, switching from a workflow they’re comfortable with feels like a drag.
And managers forcing them to use the product usually makes it worse.
Then something interesting happened.
They started asking for Excel exports instead.
They'd export the data → dump it into Claude → ask questions → get the work done.
That was the eye-opener.
They didn't hate the product.
They just preferred talking to an AI over learning another interface.
So I built an MCP.
And for the first time, I saw the same people become power users of the product — with Claude sitting on top as the intelligence layer.
That combination is honestly 🔥.
Maybe the future of internal tools isn't better UIs.
It's making your tools accessible through the AI interface people already love.
Replies
Are they mostly asking questions or also changing records through the MCP?
For writes I would show the exact records and proposed changes before approval so a misunderstood request is easy to catch
I caught myself doing the same thing with my own admin panel. I built pages for stats and support, and more and more I just ask the coding agent "how many songs failed yesterday and why" instead of opening the page I made for exactly that. The interface wasn't bad, a question is simply faster than three filters. Agree with Aleksandr on writes though. For anything that changes records I'd keep reads open and make every write show the exact change and wait for a yes. Which question do your ops people ask Claude most often?