There’s something a little ridiculous about modern business software.
We have CRMs, ERPs, inventory systems, accounting tools, order management platforms, and dozens of other applications designed to make work easier. Yet, when someone needs a simple answer or wants to complete a routine task, they often have to open an application, navigate several screens, apply filters, fill out forms, and click through multiple menus.
Sometimes, they even have to ask a developer for help.
Think about that for a moment. You already have the software. Your data is already there. The functionality probably exists somewhere inside the system. So why does using it still feel like so much work?
I think one of the most interesting opportunities in AI isn't building another application. It's making the software businesses already use much easier to operate.
Imagine sending a WhatsApp message that says:
“Create an invoice for Acme Corp for 12 units of SKU-220.”
A few moments later, you receive a confirmation that the invoice has been created in your ERP, along with the invoice number and total amount.
No dashboard. No switching between tabs. No searching for the right form.
Just a conversation.
That idea is becoming a practical way to think about the future of business software.
The Problem Isn't Always the Software
Most businesses don't suffer from a complete lack of tools. They suffer from the friction involved in using them.
A company might have a perfectly functional CRM, but finding customers who match a specific combination of conditions can still take several minutes. An inventory manager might have access to an ERP, but checking stock levels across multiple products could involve navigating several screens. A support agent might know that an order exists, yet still need to ask someone else to look it up.
And then there are those familiar messages:
“Can you check this order for me?”
“Can you pull the customer report?”
“Do we have this item in stock?”
“Can you tell me how many leads came in this week?”
Individually, these requests seem harmless. Collectively, they consume a surprising amount of time.
Consider a small e-commerce business with five support agents. If each agent spends just 15 minutes a day navigating administrative tools or waiting for someone to retrieve information, that's 75 minutes of team time every day.
Over a 22-day working month, that's 27.5 hours.
Almost four working days spent on small tasks that could potentially be handled much more directly.
And that's before counting interruptions to developers, delayed customer responses, or the frustration of constantly switching between applications.
The bigger problem is that these little inefficiencies become part of the company's normal routine. People stop questioning them because that's simply how the work gets done.
But what if it didn't have to work that way?
What If Your Software Could Answer You?
Imagine opening WhatsApp and asking your CRM:
“Show me the leads whose birthdays are this month, and include their contact details.”
Instead of opening the CRM, searching for the right filter, selecting a date range, and exporting the results, you simply ask the question.
The system retrieves the relevant information and returns the answer in the conversation.
Now imagine asking a few more questions:
- “Which leads haven't been contacted in the last seven days?”
- “Show me customers who purchased more than twice this month.”
- “Which deals are still waiting for a follow-up?”
- “Create a follow-up task for every high-priority lead.”
- “Summarize this week's sales activity.”
These are not necessarily new capabilities for the underlying CRM. Some may already be supported by its database, API, or existing business logic.
The difference is how people access those capabilities.
Instead of learning every menu, filter, and workflow, employees can describe what they need in everyday language.
That's the part I find particularly exciting. AI can become an interface between people and the systems they already depend on.
And if you're exploring how to make existing business software easier to use, this is exactly the kind of opportunity worth considering.
A Real-World Scenario: The Customer Support Team
Let's imagine a support agent named Sarah working for an online store.
A customer messages her asking whether an order has shipped. Sarah opens the support dashboard, searches for the customer's email address, opens the order record, checks the shipping status, and returns to the conversation.
The whole process takes perhaps two minutes.
That doesn't sound terrible.
But now multiply it by 40 or 50 customer inquiries every day. Add questions about refunds, payment status, product availability, delivery estimates, and previous purchases.
Suddenly, Sarah spends a substantial portion of her working day looking for information rather than helping customers.
Now imagine a different workflow.
Sarah asks the company's AI assistant:
“Check order ORD-1048 and tell me its current delivery status.”
The assistant retrieves the order information from the connected system and responds with the latest available details.
Sarah can answer the customer without opening another dashboard.
If the customer requests a change, the assistant might also help initiate the appropriate workflow, provided the necessary permissions and business rules allow it.
Of course, this doesn't mean every action should happen automatically. Issuing a refund, changing a shipping address, or cancelling an order may require additional verification or approval.
The point isn't to remove people from the process. It's to stop making them perform unnecessary administrative work.
For a small team, that distinction matters. You may not need more employees or another expensive application. You may simply need a better way to use the systems you already have.
Your Next Business Interface Might Be WhatsApp
Here's another interesting thing about chat-based interfaces: people already know how to use them.
You don't need to train an employee to understand how to send a message. You don't need to explain where the navigation menu is or how to locate a particular dashboard.
Most people already communicate through messaging applications every day.
That makes chat an appealing interface for business operations, especially for teams that work away from their desks.
Consider a business owner who is travelling and wants to know today's sales.
Instead of logging into an analytics dashboard, they could ask:
“How much revenue have we generated today?”
A warehouse manager could ask:
“Which products are running low on stock?”
A sales manager could ask:
“How many deals moved to the negotiation stage this week?”
An operations manager could request a summary of outstanding orders.
The answers would depend on the data and capabilities available to the connected systems, but the interaction could be as simple as sending a message.
This is where platforms like Caterfli become interesting. The idea is to connect AI agents to existing business systems and make their available capabilities accessible through conversational interfaces, including WhatsApp, Telegram, and web chat.
Instead of treating chat as another place to display notifications, you can make it a place where authorised people actually get work done.
And that is a meaningful difference.
The Best Part? You May Not Need to Replace Anything
Whenever businesses consider introducing a new technology, one concern usually comes up quickly: how much will we have to rebuild?
A company might have spent years developing its internal CRM. Another might rely on a customised ERP that handles complicated workflows. A third might have several internal APIs that connect its ordering, inventory, and accounting systems.
Replacing those systems just to introduce an AI interface would be a difficult proposition.
There would be migration costs, training requirements, integration work, potential downtime, and the risk of disrupting processes that already work.
But what if the existing software could remain exactly where it is?
The CRM continues managing customer relationships. The ERP continues processing invoices. The database continues storing records. The APIs continue exposing the operations they were designed to perform.
An AI layer simply gives people another way to interact with those systems.
This approach is appealing because it builds on existing investments rather than throwing them away.
For example, a business could connect an existing database or API to a platform such as Caterfli's AI integration layer. The platform can discover supported capabilities and make them available to an AI agent, depending on the integration and configuration.
An employee could then request information or initiate an operation through a supported chat channel.
No need to start by building an entirely new CRM. No need to migrate every customer record to another platform.
Of course, connecting a system still requires appropriate configuration, credentials, and testing. Not every legacy application will expose everything an AI agent needs. But the general principle is simple: improve access to the software you already have before assuming you need to replace it.
I think more businesses should explore this option before committing to another major software project.
But Wait. Should an AI Agent Really Be Allowed to Change Business Data?
This is where the conversation gets serious.
Reading information from a database is one thing. Creating invoices, updating customer records, changing order statuses, or deleting data is something else entirely.
If an AI agent misunderstands a request and executes the wrong operation, the consequences can be real.
Imagine asking an assistant to cancel a duplicate order, only for it to cancel the wrong one. Or imagine a poorly configured agent modifying customer records without checking whether the person making the request is authorised to do so.
Convenience is not worth sacrificing control.
That's why I believe the future of AI-powered business software depends on something more important than impressive demonstrations: trustworthy execution.
A responsible implementation should consider several safeguards.
1. Respect existing permissions.
An AI assistant shouldn't automatically receive unrestricted access just because it can communicate with a database. The actions available to each person should reflect their actual permissions.
2. Validate every operation.
The system should check the requested tool, its arguments, and the applicable rules before executing an action. A natural-language request should never become an unchecked database operation.
3. Require approval for sensitive changes.
Depending on the risk, actions such as issuing refunds, deleting records, or modifying important business data may require explicit human approval.
4. Keep a record of what happened.
Businesses need to understand which operation was requested, who initiated it, what was executed, and whether it succeeded.
5. Test before trusting.
An agent should be tested against realistic scenarios, including ambiguous instructions, missing information, unauthorised requests, and unexpected tool responses.
These aren't optional extras. They're part of building a system that people can responsibly use in their everyday work.
For teams evaluating AI agents for business operations, security and permission enforcement deserve as much attention as the conversational experience.
An assistant that can do everything but cannot be trusted to do the right thing isn't particularly useful.
From Asking Questions to Getting Things Done
The most valuable shift happens when AI moves beyond answering questions and starts helping people complete actual workflows.
Let's say a sales manager wants a list of overdue deals. An assistant could retrieve the relevant records and summarise them.
That's useful.
But imagine the manager can then say:
“Create follow-up tasks for these five deals and assign them to their respective sales representatives.”
The assistant could prepare the actions, validate the requested changes, and execute them if the manager has the necessary permissions.
Or consider an inventory manager who asks for products below their minimum stock levels. After reviewing the results, they might request draft purchase orders for the affected products.
The assistant could prepare those orders, leaving the final approval to the appropriate person.
The experience becomes less about searching for information and more about expressing an intention.
This is particularly useful for repetitive work involving multiple steps. Instead of manually navigating several screens, employees can describe the desired outcome and let the system handle the permitted operations.
That doesn't mean every workflow can or should be automated. Some tasks require judgment, context, or specialist knowledge that can't be reduced to a simple instruction.
But there are plenty of routine operations where a conversational interface could remove unnecessary friction.
If you're thinking about automating repetitive business tasks with AI, start by identifying the actions your team performs repeatedly and the information people constantly ask someone else to retrieve.
Those are often better starting points than trying to automate everything at once.
Start With One Annoying Task
Here's my advice for any business considering this approach: don't begin with a grand AI transformation strategy.
Start with one annoying task.
Maybe your support team repeatedly checks order statuses. Maybe your sales team spends too much time generating reports. Perhaps your operations manager has to ask a developer for a database query every other day.
Pick one of those problems.
Then ask three questions.
First, is the necessary information already available?
If the data exists in a database or through an API, you may already have much of what you need.
Second, can the task be expressed clearly?
A request such as “Show me all orders placed today that haven't shipped” is easier to work with than an ambiguous instruction like “Fix the shipping situation.”
Third, what should happen before an action is executed?
Reading an order status may require only permission to view the record. Cancelling the order could require stronger authorisation or human approval.
Once you have a clear use case, you can evaluate whether an existing integration or an AI platform such as Caterfli can help connect the workflow to a conversational interface.
Measure the results. Look at the time saved, the accuracy of the answers, the number of manual steps removed, and whether people actually prefer the new workflow.
If it works, expand gradually.
If it doesn't, you'll have learned something useful without committing to a massive rebuild.
The Future of Software Might Feel Less Like Software
I keep coming back to a simple observation: most employees don't wake up excited to navigate an ERP, configure a CRM filter, or open another reporting dashboard.
They want to solve a problem.
They want to know which orders are delayed, which customers need attention, how much the business sold today, or whether a particular invoice has been paid.
Software is supposed to help them accomplish those things. Yet, in many organisations, operating the software has become a task of its own.
Conversational AI offers a chance to change that relationship.
Instead of forcing every employee to learn every screen, we can make existing capabilities accessible through familiar language. Instead of building a new application for every small workflow, we can explore how the tools we already have might work together. And instead of giving AI unrestricted control, we can build around permissions, validation, and human oversight.
That combination is what makes the idea compelling to me.
Not AI for the sake of AI. Not another chatbot that gives polished answers but cannot help with real work.
Something more practical: software that becomes easier to operate without losing the controls that make it dependable.
The next time someone on your team asks, “Can you check this for me?”, consider why they have to ask in the first place.
Maybe the functionality is already there. Maybe the data is already available. Maybe the problem isn't your software at all.
Maybe the missing piece is a better way to talk to it.
And if one simple message could save your team an hour of repetitive work every day, wouldn't it be worth finding out?
What would you ask your business software to do first if you could operate it from WhatsApp, Telegram, or a simple web chat?
That's a much more interesting question than asking which application your company should buy next.
Top comments (0)