Solution · Business AI Transformation
The Weekly Management Brief, From Your ERP and Your Voice Notes
DataWise designs the weekly management brief for owner-run companies: sales, collections, stock and open orders from the ERP, each figure sourced.
Updated:
How does the person running the business get the week’s numbers on one page, each with its source, before the Sunday meeting rather than after it? By pulling them from the systems as they are. Sales, collections, stock and open orders are read from the ERP and the collections data at 07:00 on Sunday; what moved, what is late and which three items need a decision this week are separated from the noise; and one page lands in your inbox with the source of every figure. The meeting starts from it. DataWise designs this brief for owner-run Israeli companies, and the same worker takes a voice note from a site visit and files the report.
How it works
Sunday, 07:00: the brief is in your inbox.
Three steps sit under it.
Read the sources as they are. Sales by customer and item family, collections and overdue balances, stock on hand against open orders, deliveries due this week, from Priority, SAP or Hashavshevet and the collections data you already hold. Nothing is re-entered and nothing is written back.
Separate signal from noise. What moved against the trailing weeks, what is late against its own date, and the three items that need a decision this week. The rules for “moved” and “late” are yours, set once in scoping and adjusted as the brief earns trust.
One page, every figure sourced. The brief arrives by email, in your language, with the system and query behind each number. Where a number cannot be sourced it is marked, not shown as fact.
Demo · demo data
Your day, prepared
Five events on today's calendar: the agent attaches each event's documents, drafts an agenda for a client meeting and flags that client's invoice as 17 days overdue. The agenda email waits in your drafts, and you decide whether to send it.
One example, shown on Zenzap. We build the same agent on WhatsApp, Teams, Slack or the system you already run.
A voice note from the field
The same worker takes the week’s inputs from the people who are out of the office. You leave a twenty-second voice note on the way out of a site visit; the customer, the items and the terms are pulled from your systems; the form is filled, checked against what is on file, and sent, with one line back: sent.
What the brief does not do
It never makes a business decision for you. It never shows a figure without the system it came from. It never emails a customer or a supplier on your behalf. Those three refusals are designed in so that a managing director can trust it week after week.
What comes next
Decisions and tasks from the meeting reaching their owners is the designed next step of the in-meeting knowledge agent. What broke this week, delivered as a page on Friday, lives with the finance back office: supplier invoices and month-end.
What we’ve built
A management brief is a reconciliation, not a report: every figure is tied to the query and system it came from, movement is measured against the account’s own trailing weeks, “late” is measured against the item’s own date, and anything without a source is marked rather than shown. What we bring to it:
- WhatsApp operations agent, Hebrew voice and text: built (in-meeting knowledge agent). The voice-note step is designed on the same channel.
- Full-operation scoping and work-OS centralisation for a live-performance company: built and in daily production use, command-centre dashboard included (Business AI Transformation). The brief is the pushed, one-page form of that observability.
- Integrations against Priority, SAP, monday.com and Hashavshevet: scoped and built. The brief reads from there.
FAQ
How is this different from a dashboard?
A dashboard waits to be opened and shows everything. The brief arrives, shows what moved, what is late and what needs a decision, and stops. Each figure carries the system and the query it came from, so when someone asks 'where is that from?' the answer is on the page.
Which systems does it read?
The ones you run: Priority, SAP or Hashavshevet for sales, stock and open orders; the collections and card data you already have; the calendar for the week ahead. It reads; it does not write to any of them.