From Backoffice Clicks to Conversational Admin

A Slack message from sales: "Can we convert Greg's individual trial into an organization trial?"

Okaya helps people in high-stress roles build mental awareness and readiness through guided conversations. Someone signs up individually. Their department gets interested. Now we need to move them into an organization account.

The steps aren't hard. Sign into the backoffice. Create a new organization. Search for the user. Add them to the org. Upgrade their role to admin. Transfer any existing data. Maybe five minutes of clicking through screens you built but rarely use.

Do it once, no big deal. Do it three times a week, and you start thinking about it differently.

The question becomes — how do you fix this?

You could add a new API endpoint and build a screen for it in the backoffice. A "Convert to Organization" button. That's clean, but it's real development time for an internal tool. Hard to prioritize when there are customer features to build.

In the past, I'd write a CLI script. Hit the DB directly, chain the steps together, run it from my terminal. I've done this dozens of times across different companies for exactly these kinds of requests.

Today I'm thinking about this differently. What if I gave an agent access to the API and the data model — and just asked it to do the conversion?

No script to create or maintain. Just: "Convert greg@company.com to an org account for Acme Corp."

The tradeoff shifts. Instead of maintaining code, you're maintaining trust boundaries. What can the agent access? What requires confirmation before it acts?

It's a different kind of effort — but it scales differently when the next request from sales is something you've never scripted before.

What repetitive admin tasks are you still clicking through — and would you trust an agent to handle them?

Originally published on LinkedIn — view the original post for comments and reactions.