Define the numbers
We list the questions management asks and write down how each metric is counted: what is an order, a return, an active customer.
- Metric definitions
- The questions to answer
- Who sees what
Reporting and AI answers across your business data.
We bring sales, orders, stock and support data from your CRM, ERP and store into one model, build the reports management asks for, and add an assistant that answers questions in plain language within each user's permissions.
- Sources
- CRM · ERP · store
- Answers
- Query shown
- Access
- Per role
What we build
One source for the numbers you run on.
Built on your own systems, so every number in a report traces back to the records behind it.
Join the dataOne data model · Permissions on data
One model, one set of definitions.
One data model
Sales, orders, stock and customers from separate systems joined into one schema.
CRM + ERP + store → one model
Permissions on data
Each user sees only the branches, teams and customers their role allows.
Branch manager → own branch
ReportManagement dashboards · Scheduled reports
The numbers, on time.
Management dashboards
The weekly numbers per branch, team or product, from live data instead of exports.
Weekly sales per branch
Scheduled reports
Summaries sent by email or WhatsApp at the time each team needs them.
Sunday 08:00 → management
Ask and alertPlain-language questions · Alerts
Questions answered, changes noticed.
Questions in plain language
Ask in Hebrew, Arabic or English and get an answer with its query and sources.
“Which branch grew most this quarter?”
Alerts on changes
A message when stock runs low, returns jump or a pipeline stage stalls.
Returns above usual → alert
How it fits
One data model. Every report reads from it.
We read from the systems you run today and keep reporting separate from them, so dashboards, exports and the assistant all count the same way.
01 · Your systems
- CRM
- ERP & accounting
- Online store
- Support inbox
- Spreadsheets
02 · Data modelread-only · reconciled · per role
Numbers counted one way
- Read-only connectionsreplicas · syncs
- Metric definitionsagreed in writing
- Row-level accessper role
- Query layerSQL
- Reconciliationagainst the source
Totals are checked against the source systems before anyone relies on them
03 · Where it is used
- Management dashboardweekly
- Branch reportsper branch
- Assistantplain questions
- Scheduled reportsemail · WhatsApp
- Alertson change
Definitions first
Most arguments about reports are about what a number means, so we agree on that before building.
Reporting stays separate
Read-only connections, replicas or scheduled syncs, so reporting queries don't slow down the people working in the system.
The query is shown
The assistant doesn't calculate numbers itself. It runs a query and shows it next to the answer.
Trust in the numbers
Every number traces back to its records.
A report is only useful if people believe it. Each answer and dashboard carries how it was counted and what it was read from.
Query log · question 312Sample
| 08:15:02 | ask | returns by branch · last month |
|---|---|---|
| 08:15:02 | scope | role: regional · 3 branches |
| 08:15:03 | query | returns ⋈ orders ⋈ branches |
| 08:15:04 | check | totals match source |
| 08:15:04 | answer | shown with query |
Metric definitions
What counts as an order, a return or an active customer is agreed in writing and used everywhere.
one definition each
Row-level access
A branch manager sees their branch, sales sees their customers, management sees everything, in dashboards, exports and questions.
per role
The query is shown
Every answer from the assistant comes with the query it ran and the tables it read, so a wrong reading is visible.
per answer
Reconciliation
Dashboards are checked against the source systems until the totals match, before anyone relies on them.
before launch
Read-only by design
Reporting reads through read-only connections, replicas or scheduled syncs. It never writes to your systems.
read-only
Metric definitions
What counts as an order, a return or an active customer is agreed in writing and used everywhere.
one definition each
Row-level access
A branch manager sees their branch, sales sees their customers, management sees everything, in dashboards, exports and questions.
per role
The query is shown
Every answer from the assistant comes with the query it ran and the tables it read, so a wrong reading is visible.
per answer
Reconciliation
Dashboards are checked against the source systems until the totals match, before anyone relies on them.
before launch
Read-only by design
Reporting reads through read-only connections, replicas or scheduled syncs. It never writes to your systems.
read-only
Query log · question 312Sample
| 08:15:02 | ask | returns by branch · last month |
|---|---|---|
| 08:15:02 | scope | role: regional · 3 branches |
| 08:15:03 | query | returns ⋈ orders ⋈ branches |
| 08:15:04 | check | totals match source |
| 08:15:04 | answer | shown with query |
How we work
Define it. Reconcile it. Then ask it questions.
Definitions come first, because most arguments about reports are about what a number means.
01 / 04 · swipe
Case study
Commercial intelligence for a travel agency.
Nazarene Tours · CRM
Sales, market and pricing data in one set of screens
- Joins
- The agency's own sales, Ben Gurion passenger statistics, stored price searches, supplier quotes and pricing rules.
- Screens
- Overview, market against the agency, destinations, airlines, suppliers and opportunities.
- Method
- Every insight carries a note naming its sources. Nothing estimated is presented as measured.
FAQ
Questions about analytics.
How is this different from the reports in our CRM?
Your CRM reports on what it stores. Most questions management asks need several systems at once: orders from the store, invoices from accounting, conversations from the inbox. We join them so one report can answer the question.
Can the AI give us a wrong number?
The assistant does not calculate numbers itself. It turns the question into a query on your data model, runs it, and shows the query and its sources next to the answer, so a wrong reading of the question is visible and can be corrected.
Who can see what?
Access follows roles you define: a branch manager sees their branch, sales sees their customers, management sees everything. The same rules apply to dashboards, exports and questions asked to the assistant.
Will reporting slow down our live systems?
We read through read-only connections, replicas or scheduled syncs, depending on the system, so reporting queries don't compete with the people working in it.
We only need reports on website traffic. Is this the right service?
Probably not. Website traffic, campaigns and conversions are covered by our Analytics & tracking service, built on GA4. This one is for business data: sales, orders, stock and customers.
Start with one report
Bring the report everyone argues about.
We define its numbers with you, check where the data lives, and show you what one model and an assistant on top of it would look like.
Useful to bring
- The report management asks for most
- The systems the numbers come from
- Who should see which branches, teams and customers