Where your products and customers actually live
One product master with images and rates. One customer record matched on mobile number or GSTIN, that gets better every time somebody uses it.
Scattered across supplier PDFs, phones and your own memory
Your product information is in forty supplier PDFs, none of them in the same format.
None of that is a system. It is a set of places where the truth might be, and a different answer depending on who you ask on a given morning.
Forty supplier PDFs
none of them in the same formatA salesman's WhatsApp
where the current rate actually isThree phones
your customer numbers, in his contactsA different answer depending on who you ask
None of that is a system. It is a set of places where the truth might be.
One product, entered once
What one product record holdsName and description. Brand and category. Price and tax. Web and video links. <strong>And the image.</strong>
Why the image pays for the restEnter it once and it appears on every estimate, every price list, every catalogue and every QR scan.
- The image is the part that pays for the rest — Enter it once and it appears on every estimate, every price list, every catalogue and every QR scan. Your customer sees the same product in five different documents, and nobody uploaded it five times.
- One thing this is not — The product master holds products — codes, images, specifications, rates.
Read from supplier PDFs
Our engine reads your suppliers' price list PDFs into product data.
Photographed off your display
Your own team, four taps, without taking the panel apart.
Or we build it for you
Done-for-you data setup, priced by volume and complexity.
It does not hold stock. Your quantities stay in your ERP, where they belong.
The customer master gets better every time somebody uses it
Every customer is one record, matched on his mobile number.
For a business account it is matched on GSTIN instead, and the mobile number is ignored — because a firm has one GST registration and four people who might ring you, and all four are the same customer.
Then the part that matters over time.Admin authorisation is required only for the operations that deserve it: bulk imports, bulk deletions.
For the duplicates you already have, from before any of this, there is a merge tool.
New customers can be created on the spot while an estimate is being built.
Most customer databasesThe old way- Duplicates accumulate — the same person, four times, four spellings
- Addresses go stale — and eighteen months later nobody trusts it
This one- Corrected by whoever notices — a salesman does not need permission to fix a spelling
- Approval only where it deserves it — bulk imports and bulk deletions
- A merge tool for what you already have — from before any of this
Nobody has to set anything up first.
A network you did not set out to build
Architects, designers, engineers, contractors, the customer who referred his brother — recorded with their category and their number, as your team notes down who sent somebody.
Nobody sets out to build this list. It accumulates as a by-product of ordinary work, and after a year you have a categorised professional network that belongs to the business — in trades where one architect specifying your products can mean years of orders.
When a salesman leaves
His customer list does not leave with him.
You already know why that sentence is on this page.
Two records, two jobs
Your ERP has customers and it has items.
It is the financial record of your business and it should stay exactly that.
But it does not hold the product image. It does not hold what was discussed on the phone in January. It does not hold where the enquiry came from, or which architect specified the job, or which of three quotations the customer was comparing.
That is the selling side of your business, and in most firms it has no system of record at all.
Not a worse one — none.
Deleting takes two decisions
When somebody deletes a record, it goes to an archive.
It is out of the way, out of the lists, and not gone.
To remove it permanently, someone has to open the archive and delete it there — a second, deliberate act.
Which means the customer a new salesman removed on his third day is recoverable, and so is the product somebody archived during a tidy-up two years ago and now needs for a warranty claim.
See it with your own products and customers.
Ask for a demo