Software's Front Door Is Shifting from Menus to Conversation

Recently, Business Insider reported that Meta is switching its internal communications tool from Google Chat to Slack.

Citing an internal memo from Meta's AI chief Alexandr Wang, the report says one important reason is that Slack is better suited to AI agents: it has a rich conversational interface, mature developer tooling, and a large number of third-party integrations.

Meta, Salesforce and Google have not publicly confirmed the specifics of the report. But it raises a genuinely interesting question:

In the AI era, will the main way people enter software gradually shift from clicking menus to simply starting a conversation?

News link: Business Insider: Meta is switching to Slack because it says it's better for AI agents

Software in the past was usually organised by function.

An accounting system has invoices, banking, transactions, reports and tax; a CRM has customers, leads, marketing and sales pipelines; project management software has tasks, members, timelines and statuses.

That design requires the user to first understand how the software organises its features — and only then find the right entry point to get work done.

If a user wants to know "why did cash go down this month", they must first know which report to open. If they want to confirm whether a payment has an invoice, they need to go into bank transactions, then search the document system. If they want to send a reminder to a customer who hasn't paid for a long time, they may have to switch to yet another system.

A large share of traditional SaaS's learning cost comes from the user having to understand the software's internal structure.

But what a business owner actually cares about is usually not the menu.

What they care about is:

"Help me see who this payment went to." "Find the invoices that haven't been paid yet." "How much VAT do I need to file this quarter?" "Remind this customer to pay." "Why did profit look good last month while the bank balance fell?"

When an AI agent can understand these goals and call the right tools in the background, the user doesn't necessarily need to know which menu each feature hides under.

Software's features won't disappear — but they will increasingly retreat behind the conversation.

This is also something we care deeply about in designing Snappy.

SnapLedger still needs ledgers, bank transactions, invoices, reports, tax tools and My Vault. For accountants and professional users, these structured interfaces remain very important.

But for many small business owners and freelancers, they shouldn't have to learn an entire complex accounting suite just to run their own business.

They can simply tell Snappy what they want to do.

Snappy then finds the right tools, organises the relevant information, and helps the user complete the next step — based on the business's identity, bank transactions, documents, ledger and history of operations.

And the conversation doesn't have to happen only inside SnapLedger's website or app.

For many small businesses, the work interface they actually open every day might be WhatsApp. Customer enquiries, supplier quotes, payment screenshots, invoices and business arrangements already live inside those conversations.

So in the future, Snappy can also show up where users are most comfortable.

A business owner doesn't need to set aside special time to "operate the accounting system". When they receive a payment, snap a receipt or talk to a customer, they can have Snappy save the record, match the transaction, generate the invoice or schedule the follow-up — right there.

This doesn't mean all software will become one giant chat box.

Some information is better shown in reports; some relationships need to be recorded precisely in ledgers; and some high-risk operations must be confirmed through structured interfaces.

The truly sensible design lets conversation handle understanding intent and coordinating work, while professional tools handle precise execution and presenting results.

In other words, conversation is not replacing every interface — it is becoming the new front door that connects them.

In the past, users had to learn the software's language.

In the future, software should learn more of the user's language.

I believe this is not only a change of user interface — it will also change how SaaS competes. Past advantage may have come from having more features and more elaborate menus. Future advantage may come from who can more accurately understand what the user wants to accomplish — and mobilise the tools behind the scenes to actually get it done.

The best software in the AI era may not be the one that shows users the most features — it's the one that lets users get the most work done in the most natural way.