Vision
Every business keeps two sets of books.
The first is the ERP. It knows what was ordered, invoiced and paid, after the fact. The second is everything that decided those numbers: the enquiry, the negotiated rate, the promised date, the delay, the complaint, the follow-up. That second set lives in WhatsApp groups and personal chats, and until now no system has kept it.
DataLense is building the system of record for that second set: first to capture every order, promise and payment, then to flag what is pending or at risk, and step by step to do the follow-ups, with the owner approving what matters.
The expensive half is the one nobody can see.
When the commercial conversation lives in chat, three costs follow. Enquiries go unanswered because nobody owns the group they arrived in. Promises slip because the person who made them is the only one who remembers. And the owner becomes the integration layer, spending the day asking for status that already exists somewhere in a phone.
None of these show up in the ERP. They show up as a dealer who quietly orders elsewhere, a payment that runs thirty days late, a production plan built on last week's numbers. The opportunity is not another dashboard on top of the transactions. It is making the conversations themselves a source of truth.
Five steps, each earning the next.
The order a manufacturer set out in its own requirements for us: find first, then flag, then recommend, then draft for approval, and only then act on routine work within limits you set. What ships today is marked; the rest is the direction we are building in, not a dated promise.
- 1
FindAvailable now
Find any order, promise or report in seconds
Everything your team says and shares in chat, searchable next to your ERP, without anyone changing how they work.
One inbox across every number
Every WhatsApp and Telegram chat and group, with one history per customer.
Sheets become records
Dispatch sheets, order lists and delivery notes read into records by code, linked to their source.
Answers with sources
Ask about orders, customers and payments; every fact links back to the message or record.
- 2
FlagPartly available now
See what's pending, at risk or overdue
The right person hears about the exception, instead of everyone hearing about everything.
Who is waiting
Customers still waiting for a reply, across every number, sorted by how long. Available now.
Promises tracked
Dispatch dates and payment promises made in chat, checked against your ERP and flagged before they slip. Coming.
The owner's brief
A short daily summary on WhatsApp: pending orders, dispatch due, payments overdue. Coming.
- 3
RecommendComing next
Suggest the next step, with the evidence
When something needs a decision, DataLense says what it would do and shows exactly why.
Which order to chase
The follow-ups that matter most today, with the messages and records behind each one.
Customers drifting away
Dealers whose orders slow down or whose complaints repeat, while there is time to act.
- 4
Draft for approvalComing next
Prepare the work, you approve it
Commercial commitments always need a person. DataLense does the typing; you do the deciding.
Replies with the facts
Draft replies that already include live stock, the agreed rate and the real dispatch date.
Orders into your ERP
A confirmed order in a dealer group becomes a draft sales order in ERPNext, Odoo, QuickBooks, Xero or Tally, posted when you approve.
Payment reminders
Polite reminders for overdue payments, with the invoice and amount, sent only after you approve.
- 5
Act within your limitsLater
Routine work done, within rules you set
For the routine you choose, DataLense acts on its own, within limits on amounts, customers and hours, with a full log and an off switch.
Rules you set
Which customers, which actions, up to what amount, at what hours.
Everything logged
Every action linked to its source and reversible, with a person approving anything outside the rules.
What a working day looks like when it compounds.
An illustration of how everyday moments change as each step arrives, not a measurement.
| The moment | Without DataLense | With DataLense |
|---|---|---|
| Knowing the state of the business | Calls and messages to three people for status | A briefing that is ready when you are |
| An order confirmed in a dealer group | Typed again into the ERP, sometimes wrong | Drafted from the chat, posted when you approve |
| A payment promised in chat | Remembered until it isn't | Tracked, and a reminder drafted when it's overdue |
| A customer waiting for a reply | Noticed when they complain | Flagged while there is still time to answer |
| A promised dispatch date | Remembered by whoever made it | Tracked against the ERP until it is met |
| The daily report shared in a group | Scrolled past, then searched for | Already a record you can filter and ask about |
| A new team member | Learns accounts by asking around | Asks DataLense and gets the history |
Why this is possible now.
Machines can finally read the way businesses talk
Mixed-language messages, shorthand, photos of printed sheets and forwarded spreadsheets used to need a person to interpret them. Modern language and vision models read them reliably, and the cost of doing so keeps falling.
The transaction layer is already digital
Invoicing, payments and inventory moved into software over the last decade. The conversations around them never did. Joining the two is now the highest-leverage step left.
The work already happens on messaging
Customers, dealers, suppliers and shop floors coordinate on WhatsApp and Telegram by default. Any system that asks them to move loses. One that works where they are compounds.
Why it gets harder to copy every day.
- It compounds
- Every approved report format, every recognised person and every connected record makes the next answer better. The longer a business runs on DataLense, the more it knows.
- It meets businesses where they are
- No migration and no new app for dealers or the shop floor. Adoption is a QR code, which is why it can reach businesses other software never does.
- Trust is built into the design
- Per-chat control, AI off by default, numbers masked before any model sees them, and answers that show their sources. Owners stay in charge of what is read and what is done.
- It sits between the systems
- Messaging on one side, ERP and accounting on the other. DataLense is the layer that connects them, which makes it the natural place for the work between them to happen.
Start with step one.
Everything ahead builds on the history you start keeping today. Link a WhatsApp number and DataLense begins learning your business from the first message.
Sign in with Google or your email. AI stays off until you turn it on.