Every business product now claims to be powered by AI. Some of that is real and useful. Some is a text box added to a menu.
It helps to ask what kind of work the AI is doing. Inside business systems there are four kinds it does well.
01Reading
Turning unstructured material into structured data: an invoice into ledger fields, an enquiry into a quote request, a resume into a candidate record, a supplier sheet into product attributes. This removes the largest share of manual entry.
02Matching
Recognising that two records are the same thing despite different wording: duplicate customers, materials, suppliers or invoices. It is unglamorous and it is where much of the money in enterprise data is lost.
03Predicting
Estimating what will happen from what has: demand, churn, late payment, workload. It needs enough clean history and should always be shown with how often it has been right.
04Drafting
Producing a first version for a person to approve: an email, a summary of a long thread, a status report, a product description. It saves time and must never be the last step.
05Where to keep it out
- Calculations that must be exact: tax, payroll, pricing, postings. These belong to rules.
- Decisions about people, such as hiring, pay and dismissal, except as a transparent aid to a human who decides.
- Anything that cannot be undone, without a person approving it.
- Any use where nobody will measure whether it is right.
06Four questions for any AI feature
- What does it read, and where is that data processed?
- Does it show the evidence for each result?
- What happens when it is unsure?
- How was its accuracy measured, and on whose data?
In short
- AI in business software does four jobs well: reading, matching, predicting and drafting.
- Exact calculations and irreversible actions should stay with rules and people.
- A feature that cannot show its evidence or its accuracy is not ready for important work.
- It is only as good as the data underneath it.
Questions
Does AI in our systems mean our data goes to an outside provider?
Only if it is built that way. Language models can run on your own infrastructure, so records never leave it. Ask any vendor where processing takes place.
Which system benefits most from AI?
Whichever has the most reading and matching: accounts payable, master data, customer support and document-heavy processes are common first choices.
What is the difference between rules and AI in automation?
Rules do exactly what they are told, every time, and can be audited line by line. Models handle variety and ambiguity, with some error. Good systems use rules wherever rules suffice and models only where they run out.
Sounds like your problem?
Tell us about it. We'll say honestly whether the swarm can help, and what it would take.
Read next
- CRM, ERP, HRMS, CDP, PIM, WMS and the rest: thirty business systems explained in plain wordsBusiness systems
- Custom software or off-the-shelf: how to decide whether to build, buy or extendBuild or buy
- Custom CRM or off-the-shelf CRM: which does your sales team need?CRM
- When does a company need a custom ERP?ERP
- CDP vs CRM vs DMP: what each one stores, and which you needCustomer data
- CMS, DAM and PIM: what each one manages, and why a catalogue needs all threeContent and product data