Ask your business. See the source.
A bot that signs in to your ERP and documents and answers questions about sales, stock, credit and products in plain English, every morning and whenever you ask.
No ERP replacement and no retrained model. Answers show their sources and a person reviews them before anyone relies on them.
Signs in to your ERP with its own login, or works from your spreadsheets and documents.
The business questions agent layout
The business questions agent delivered for a client, reproduced with its layout and navigation. Branding and content are replaced; no client data appears. Read the customer story.
Ten-second illustrative film for the business questions agent: records become one reviewable answer with its context.
Try the guided demo01 / What it is configured around
Your knowledge. Your rules.
- Sources your team chooses: product documents, price lists and specifications, exported correspondence, competitor notes and structured business spreadsheets such as sales and stock exports.
- Saved business rules and corrections: when the team corrects an answer or records how something is done, that rule is kept and applied next time. The underlying model is not retrained and no accuracy is guaranteed.
- Reviewable answers: every answer shows the document, row or rule it relied on, so anyone can check it against the source.
- Business data analysis: questions across spreadsheets and exports, such as which accounts are late against their usual interval or how one product family is moving across codes.
- Team responsibilities: who owns which knowledge, who reviews outputs and who can save a rule, agreed before build.
02 / How it reaches your data
Three ways in. Use whichever suits your systems.
The bot uses whatever route your systems allow, and you choose what it can see and do.
Signs in like a member of your team
The bot gets its own login to your ERP, inbox and portals, with the permissions you choose, and uses the same screens your team uses. No API and no upgrade needed.
You provide: a user account with the access you are happy to give.
A direct connection to your ERP
Where your ERP offers an interface, or runs on its own server, we connect to it or its database directly, with access agreed with your IT team.
You provide: access approved by whoever owns the system.
Your spreadsheets, exports and documents
Excel workbooks, multi-tab files and SAP exports, CSV, PDF, Word and emails, dropped in by hand or picked up on a schedule from an agreed folder or mailbox.
You provide: the files, and someone who can confirm what they contain.
03 / Reporting use case
Three workflows. Start with one.
Each is a defined piece of work with agreed rules, agreed exclusions and a check against your source records before handover. The tables are sample data.
01
Customer-order review
Compare each account’s days since last order with its own usual ordering interval, not a blanket cut-off. Returns, cancellations and one-off machinery lines are treated separately.
02
Stock-movement review
Read dispatches alongside receipts and on-hand quantities so a fresh delivery is not mistaken for slow stock. Agreed periods, agreed exclusions, totals reconciled to the source report.
03
Product-code grouping
Equivalent products sold under several codes are mapped to agreed families, with matching units and specifications signed off by your team. Review the family as a whole while keeping every source line visible.
04 / Acceptance checks
Checked before anyone relies on it.
These are the checks we agree with your team and run against sample exports before handover. They come from the kinds of problems that surface in real reporting work.
- 01Scope confirmed, rows reconciledConfirm the export’s filters, period and scope first, then reconcile the loaded row count with the file. Truncated files are caught here.
- 02Correct documentThe report type, period and site are verified against the question before anything is calculated, because a wrong export can look plausible and even reconcile internally.
- 03Totals reconcileQuantity and value totals in the output match the source report for the same period, and any difference is explained before handover.
- 04Exclusions behaveRecent arrivals are not flagged as slow stock. One-off machinery sales do not make a consumables customer look lapsed. Seasonal pauses are treated as agreed.
- 05Spot-checks against sourceYour team picks accounts and products and checks the output against the original records. Only then is it handed over.
A few practical questions
Before we start.
Do we need to change our ERP or give you access to it?
You don’t need to change it. The bot needs access the way a new member of staff would: its own login, with the permissions you choose. If you would rather start from exports, it works from those too.
How much data do you need for the first conversation?
None. We use sample data to talk through the question you want answered. Real exports come later, once we have agreed what to look at.
What does the output look like?
A short review list or table your team can read in a few minutes, with the rules written down beside it.
How is it priced?
A fixed price per pilot, agreed in writing, half to start. Scope and acceptance checks are agreed in writing first. See pricing.
Is this the same as the website product questions agent?
No. This bot answers your team’s questions about the business. The website product questions agent answers product questions for visitors on your website. Either can be taken up on its own.
A 15-minute conversation
Bring us one repetitive task.
Bring one task your team spends hours on every week, and we will show you where a bot helps first, in the systems you already run. No preparation needed. We can use sample data.