AI for sales in Business Central
Who stopped buying, who is buying less, where discount is leaking margin, and which accounts are worth a call this week — from posted documents rather than from memory.
Short answer: sales analysis in Business Central is mostly about noticing changes in patterns, and pattern-noticing across hundreds of customers is exactly what nobody has time for. The data required is already there in posted sales documents and customer ledger entries.
Customers who stopped buying
The most useful sales question in a B2B business is rarely “who are our biggest customers” — everyone knows that. It is “who used to buy regularly and has quietly stopped”, because in a business with recurring orders churn is silent. Nobody cancels; they just stop ordering, and six months later someone notices.
The analysis needs a definition of normal per customer rather than a single global rule. A customer who orders every three weeks and has not ordered in eight is a signal. A customer who orders twice a year is not overdue at four months. That distinction is the difference between a useful list and one the sales team ignores after the second week.
- Customers with no posted document beyond their own typical interval
- Customers still ordering but at declining value or frequency
- Accounts that dropped specific product lines while continuing to buy others
- Prior-year revenue at risk, so the list is ranked by what it is worth
Discount leakage
Discount is the fastest way to lose margin without anyone deciding to. Business Central records what was invoiced against what the price list said, so the gap is measurable — by salesperson, customer, item and period.
What makes this analysis land is context rather than the number itself. A discount above policy on a large order that came with prompt payment may be exactly right. The same discount given routinely to a customer who also pays late is a different conversation. An assistant can put those two facts in the same answer; a discount report cannot, which is why discount reports get produced and then quietly ignored.
Performance and territory
Comparison against plan, between territories, between periods, by product mix. This is well-covered ground in Power BI and if you already have a dashboard that answers it, keep the dashboard — it is faster to read. Where AI adds something is the follow-up: the dashboard shows that one territory is down 14%, and the useful next question is why, which nobody built a visual for. Our note on Power BI and Business Central covers where each fits.
Working with the CRM data you actually have
An honest limitation. If your sales process lives in Business Central's built-in CRM, opportunity analysis works. If opportunities are tracked in Dynamics 365 Sales, another CRM, or a spreadsheet, then Business Central holds the outcome but not the pipeline — and an assistant reading it can analyse what was sold but not what was nearly sold or why a deal was lost.
This is fixable by integrating the other system, which is a larger project. It is worth knowing up front, because “why are we losing deals” is a common first request and is frequently unanswerable from ERP data alone. Our article on CRM or ERP first covers the underlying question.
Sales agents
Beyond analysis, a sales AI agent can prepare the follow-up: draft outreach for lapsed accounts, create quotes from a described requirement, flag orders that breach credit terms before they are released. Order release and pricing decisions typically stay with a person — margin is given away one approval at a time, and that is a decision worth keeping human.
Frequently asked questions
What data does sales analysis need?
Posted sales invoices and credit memos, customer ledger entries, item and category structure, and price lists if you want discount analysis. All standard Business Central data. Salesperson and territory analysis additionally needs those fields filled in consistently.
Can it tell us why we lost a deal?
Only if the reason is recorded somewhere the assistant can read. If lost-sale reasons are not captured, no analysis produces them. Business Central holds what you sold, not what you nearly sold, unless your pipeline lives in its built-in CRM.
Does it work with Dynamics 365 Sales or another CRM?
It can, through integration, but that is a larger project than reading Business Central alone. Worth scoping deliberately — the question of what data lives where is usually the main variable in what a sales assistant can answer.
How does it define a customer who has stopped buying?
Against that customer's own ordering pattern rather than a fixed number of days. A customer who orders every three weeks and has not ordered in eight is a signal; a twice-yearly buyer at four months is not. A single global rule produces a list the sales team stops reading.
Can it write to customer records?
An agent can, within its permission set — updating a contact or creating a quote, for example. Credit limits and pricing decisions are normally kept with a person, because those are commercial judgements rather than data entry.
Ready to modernize your business?
Leave your details and we'll send the details of a free process audit. We reply within one business day.
or write directly: info@nbcs365.com · +380 98 107 5878