We built Billjot inside 500+ Indian kitchens
Not in a boardroom. We walked into dhabas, sweet shops, canteens and fine-dining counters across India, watched how billing really happens, and built custom software and hardware around what we found.
It began with one frozen screen
A lunch rush. A frazzled cashier fighting a frozen POS. The owner, exasperated, muttered the line that started all of this:
“If only this system worked as smoothly as it should.”
It wasn't unique. So we asked the obvious question: what if there were a better way?
Three questions: What, Where, Why
Every conversation came back to the same three.
What are they using?
- An old billing machine
Prints a total, never the items behind it.
- A notebook for tabs
Regulars, dues and counts, all by hand.
Where is the problem?
- Token system
Issued early, matched by hand, and easy to lose.
- Salaries & expenses
Tallied manually, nothing to reconcile against.
- Order counts
No item-level record. One lost slip hides theft.
Why still use it?
- Cost
₹30k+ before a single bill. A non-starter.
- Complexity & fear
"What if we press the wrong button?"
- Inertia
Twenty years of habit is hard to break.
What the field told us to build
A clear set of goals, and the questions to answer next.
- Build a POS that actually fits a small kitchen
- Keep it minimal by default
- Let complexity switch on only when the user needs it
- Make it standalone, so it keeps working on its own
- Hardware-driven or software-driven model?
- How much cost do we cut, and how much is worth spending?
- What are the real options on the market today?
- How many others are stuck with exactly this?
One size fits none
A dhaba bills nothing like a bakery. We mapped 200+ types, which is why Billjot is customized, not configured.
Validated in 8 live deployments
No guesswork. The bar shows how many of 8 pilots kept each feature.
- Frontend: Next.js & PWACore8/8
- Offline modeCore8/8
- Backend: Node.jsCore8/8
- Database: MongoDBCore8/8
- On-site server: Raspberry PiHardware6/8
- Custom local domain: Bind9Infra8/8
- Role-based access (RBAC)Security8/8
- Receipt printingCore8/8
- Inventory managementCore8/8
- Sales analyticsCore8/8
- Sync when onlineCore8/8
- Cloud data backupOptional5/8
- Customer managementOptional3/8
- Tabs for regularsOptional3/8
- Barcode / QR scanningOptional3/8
- Payment gatewayRazorpay, PayU, PhonePe, Google Pay & moreIntegratingRolling out
- Virtual walletDropped0/8
- Custom websiteDropped0/8
Low scores aren't failures, they're the point. Optional stays optional, unused ideas get dropped, and gateways roll out across Razorpay, PayU, PhonePe and Google Pay. You carry only what your kitchen needs.
Custom software
An offline-first PWA that runs the floor without the internet, syncs the moment it's back, and shows only the features your team actually uses.
Custom hardware
An on-site server (a Raspberry Pi where it fits, your existing machines where it doesn't) and printers, sized to your counter, not to an enterprise price tag.
Your kitchen could be the next one we build around
Message us or reach out. We'd love to learn how you work, the same way we've done 500+ times.