Build -
Two businesses asked for a CRM, so we built a demo they can use
Two CRM and ERP enquiries came in. Before the calls, we built a working demo with purchase orders and staff views, a short form and a privacy page.
Two businesses got in touch this week about a CRM and ERP. Instead of describing what we would build, we built a demo they can click through before the call.
It follows one customer from the first WhatsApp message to a paid invoice. The lead moves from new to contacted to quote sent to won. Winning it creates an order and an invoice, takes the materials out of stock, and raises a low-stock alert when something runs short. The owner sees all of it on one dashboard. There are two sample businesses, a fashion label and a manufacturer, and a "Play full flow" button that runs the whole journey in about 24 seconds.
Later the same day we added two things most businesses need. When stock runs low, the demo now raises a purchase order to the supplier, and the stock only goes up once the goods are marked received. And a "View as" switch shows the same system as the owner, sales staff or the accountant: sales staff never see revenue or invoices, and the accountant sees payments but not leads. A real system enforces this with separate logins; the demo shows the idea.
The demo asks for a name, phone number and email before it opens. We went back and forth on this. A form puts some people off, but a CRM is a conversation, not a self-serve product, and we want to know who is looking. People we invite to a call get a link that skips the form.
Asking for details meant we owed people a clear answer about what happens to them. So the site now has a privacy page in plain language: what we collect, where it is stored, how long we keep it, and how to ask us to delete it.
One honest note: the demo runs in your browser on sample data. A real system is built around how your business already works, which is what the calls are for.
Written by Rushi Prajapati