Built in a godown. Not a boardroom.
We ran our own distribution business on Google Sheets for years. Then we built a system on top of them — deliveries, proof of delivery, attendance, approvals, payroll. It runs our operation across North Bengal and Sikkim every single day.
Five businesses. That's all we're taking this year.Five businesses. That's all we're taking this year.
Drivers on beat
It syncs itself.
It knows who has what.
It moves with the van.
It proves it happened.
Every invoice, GRN and cancellation leaves Tally on its own. Matched on Tally's internal ID, so a renumbered voucher reconciles itself instead of becoming a duplicate you find three weeks later.
Forty-two stops across four drivers in one morning pass. Each driver sees only their own beat, with invoice values hidden from them — and an invoice can only ever be assigned once.
Where a delivery is stops being a phone call. The office answers the customer directly, off one screen, while the van is still moving.
The POD photo attaches to the invoice and lands in your own Google Drive — findable in three seconds, three years later, when the customer disputes it.
pulling from tally · every 5 minutes
Where we actually are.
Written plainly on purpose. If you've been sold vapourware before, here is everything you'd otherwise have to drag out of us on the call.
Our own delivery staff, drivers, billers and managers have been running on it for months. It is not a prototype.
Your team installs it from the Play Store like any other app. It's the same build our own staff have been running for months.
For most distribution teams in India this doesn't matter — field staff are on Android. If your office runs on iPhone, tell us and we'll be straight with you about timing.
That's a day of our time per business, plus a couple of hours with whoever looks after your Tally machine. It's why we're taking five and not fifty.
Built for the business with vans, staff and a Tally licence.
Not a generic ERP. Stemzo was written inside one FMCG distribution business and shaped around the way that kind of operation actually works.
Multiple brands, invoice prefixes that decide who sees what, delivery boys and transporters, GRN and e-invoice follow-ups. This is the operation the product was built inside.
Anyone moving goods out of a building against invoices, who currently proves it happened with photos on someone's personal phone.
If attendance, advances, penalties and leave are argued about on payday, the payroll and approvals half stands on its own — with or without deliveries.
Four tools already live in the field.
Not slideware — these are real tools deployed and running with live users every day, with several more shipping every month.
Every invoice, GRN and cancellation syncs with your Tally automatically. Matched on Tally's own internal ID, so renumbered or edited vouchers reconcile themselves instead of creating duplicates you find three weeks later.
Assign vehicles and drivers each morning, set the order of the day's stops, and every driver gets their route on their phone — without invoice values exposed to them.
Leave, expense, onboarding and designation requests in one queue instead of four WhatsApp groups. Two-stage routing where it matters, self-approval blocked, oldest request always at the top.
Geofenced clock-in from the phone, proxy marking for staff without smartphones, and payslips that itemise every advance, penalty and leave day — so nobody argues about the number on payday.
Every invoice, GRN and cancellation syncs with your Tally automatically, matched on Tally's own internal ID — so edited vouchers reconcile themselves instead of creating duplicates.
Assign vehicles and drivers each morning, set the day's stops, and every driver gets their route on their phone — without invoice values exposed to them.
Leave, expense and onboarding requests in one queue instead of four WhatsApp groups. Self-approval blocked, oldest request always at the top.
Geofenced clock-in, proxy marking for staff without smartphones, and payslips that itemise every advance, penalty and leave day.
What the first week actually looks like.
No pretending this is self-serve. Here is the honest sequence, including the parts that need someone from your side in the room.
We install a small tunnel client on the PC already running Tally, so Stemzo can read your sales vouchers over an encrypted, outbound-only connection. No inbound port is opened, and nothing is ever written back into your books.
2–3 hours, scheduledCompanies, brands, employees, vehicles, transporters and roles. The sheets and tabs build themselves — what takes the time is deciding who is allowed to see and approve what. This is the step that sets your real start date.
Half a day of engineering, plus your data entryDelivery staff confirm on the app and on paper for a day or two, so nobody is trusting a new system with the only copy. Then the paper stops. We watch the first live day with you.
2–3 days, then you're on itWhat the pilot actually is.
Five businesses this year. Not a free trial you click into — a month of us working on your operation with you.
Your real deliveries, your real staff, your own Tally. Not a sandbox.
Companies, employees, brands, vehicles, roles, and the connection to your Tally — we do that work, not you.
That's the deal. We're not looking for polite feedback, we're looking for the thing that makes your biller give up on day four.
First customers get first-customer terms, and we put the date on it so you know exactly what changes at renewal.
Your data stays yours.
Stemzo connects to the Tally already running in your office over an encrypted, outbound-only tunnel — no inbound port is opened on your server. We pull the sales vouchers needed for reconciliation, nothing else.
POD and LR photos, master sheets, payslips and exports live in Google Drive and Google Sheets you can open, export or take with you — not locked inside a database only we can read.
Stemzo runs on Google Cloud. Every customer's data sits under its own organisation, separated at the database level and enforced server-side — one customer cannot read another's.
We never sell it, never share it between customers, and never use it to train models. Your operations data is used to run your operations, and that's all.
Google Sheets
Google Drive
We run our own business on it, every day.
Stemzo began in 2019 as an FMCG distribution business out of Siliguri, and has grown into a group spanning distribution, warehousing and contract tissue-paper manufacturing. Every module here was built to fix something that was going wrong in that operation. That business is still trading, under its own name, at stemzo.in — super-stockist, distribution and CNF across nine states.
These are our distribution numbers, not Stemzo SaaS customer numbers. We'd rather say that plainly than let you find out in a demo — being customer zero is the stronger claim anyway. Go and check the distribution business; it does not need us to vouch for it.
The questions you'd ask on the call.
In the product today, there isn't much, and we'd rather say so here than have you find out in the demo. Route ordering is manual. Payroll deductions are explicit, rule-based arithmetic. Nothing is being predicted or decided by a model. We built the operational core that works first, and we'll call something AI on this page the day we can show it to you running.
Not yet, and we're not going to give you a date on a web page. Android is live on Google Play today. The app is cross-platform already, so iOS is a build, an Apple enrolment and device QA rather than a rewrite — but Apple's enrolment is the part we don't control, so any date here would be a guess. If your office or field staff are on iPhone, tell us on the call and we'll give you where we actually are that week.
Your books stay on your own machine — we connect to your Tally over an outbound-only encrypted tunnel and pull only the sales vouchers needed to reconcile. Documents, master sheets and payslips live in ordinary Google Drive and Google Sheets you can open, export or take with you. Operational records sit on Google Cloud, isolated per organisation and enforced server-side. If you have a specific residency or retention requirement, ask and we'll confirm in writing what we can support.
We price per business, on the call, rather than publishing a number that would be wrong for most people — and the five pilot businesses get introductory terms in writing, with the date on them so you know exactly what changes at renewal. What we can tell you now: there's no per-invoice fee, and the Tally connection isn't a paid add-on.
Realistically two to three weeks from signing, and the limiting factor is almost never engineering — it's how fast your master data (employees, vehicles, brands, roles) gets entered and who signs off on the approval rules. We onboard one organisation at a time on purpose, so you get the whole team rather than a queue position.
Nothing, for the first few days. Delivery staff confirm on the app and on paper in parallel so no one is trusting a new system with the only copy of anything. When the two agree for a couple of days, the paper stops.
Fifteen minutes, on your operation.
What you'll actually see.
A live system running a real distribution business — not slides, and not a sandbox with three fake invoices in it. We'll call you; fifteen minutes is usually enough to know if this is worth either of our time.
- Today's despatch floor, with real invoices moving through it
- The Tally sync catching a renumbered voucher, live
- A payslip built from the attendance the app captured
- An honest answer on anything that isn't built yet
We'll come back to you with two or three slots, usually the same day.
Fifteen minutes. Your operation, not a slide deck.
We'll show you the same system running our own distribution business — invoices, drivers, payroll, the lot.


