What if your team never logged in?

Count the systems your ops team logs into before lunch: the custodian portal, the CRM, planning software, DocuSign. Each has its own navigation and its own way of doing things.

My bet is that within 24 months, every software company will need to make its own interface optional. Three shifts make that realistic.

The task comes to you

A Prodos user recently texted our agent asking it to start an account-opening form for a new client. That's how people already delegate: say what you need, then expect progress, a question or something to review. Every, our banking and back-office platform, already works this way: card transactions arrive as a message with suggested expense memos, and I reply in one click.

Voice works the same way. Saying next steps out loud on the way out of a client meeting is easier than typing them into three systems later. The channel only helps if something capable is behind it, though.

Existing software gets a new front door

Through MCP, vendors can expose features they spent years building so an AI assistant like ChatGPT or Claude can use them on someone's behalf. The data and functionality still matter. People just stop having to learn another set of menus.

The screen fits the task

Some work still needs a screen: comparing account-opening packets, reviewing activity history, approving a form. Those screens can be assembled around the question instead of designed as one path everyone has to follow.

You don't need a team of power users

At J.P. Morgan I worked with people who couldn't write a VLOOKUP and were excellent at their jobs. AI will be similar. Some people will build workflows. Others should be able to send a text, get the work done and be brought back in when their judgment is needed. If they rarely need to log in, that's a good outcome.

This is a short version of an issue of The Prodocol, our newsletter on LinkedIn. Read the full issue or subscribe to The Prodocol.