Multi-branch permissions
Role-scoped read and write, enforced server-side, re-checked per request.
Proven in: Hindusthan CRM, TIPLOperating software for industrial businesses
Optimate designs, ships and operates custom operating software for industrial businesses — production, inventory, costing, payroll, pricing and statutory reporting. Not a template. Not a chatbot. The system your company works out of every day.
Four custom systems. Three operating in production today.
| System | Sector | Status | Live since |
|---|---|---|---|
| Hindusthan Earthmovers CRM Hindustan Auto Suppliers | Heavy earthmoving dealership | Live | Jul 2026 |
| TIPL Operations Platform Techcon Infrastructure Pvt Ltd | Infrastructure contracting, multi-site | Live | Jul 2026 |
| Little Lore ERP Little Lore | Apparel manufacturing + retail | Live | Jul 2026 |
| Parts & Pricing System HAS / HE / TIPL group | Heavy earthmoving spare parts | In build | — |
What the shipped systems already prove.
Role-scoped read and write, enforced server-side, re-checked per request.
Proven in: Hindusthan CRM, TIPLConfigurable non-linear routes, kanban stage tracking, full stage history.
Proven in: Little LoreStock books, transfers, on-hand integrity under backdated corrections.
Proven in: Hindusthan CRM, TIPLDay-rate labour costing, attendance to salary sheet, true cost per piece.
Proven in: Little Lore, TIPLAppend-only price history, discount engines, money as integer paise.
Proven in: Parts & PricingPurchase orders on real letterhead with stamp, TR-series registers, print geometry tested.
Proven in: TIPLPDF and OCR into a mandatory human review step, never trusted blind.
Proven in: Parts & PricingOne column registry driving grid, form, bulk import, export and search.
Proven in: Parts & PricingWritten, phased, reviewed and operated.
A written PRD with numbered acceptance criteria. When there is a disagreement later, the spec wins, not whoever is loudest.
Each phase is a self-contained brief with its own definition of done. One writer per branch, so nothing collides.
Every behaviour-changing phase is reviewed by someone who did not write it, adversarially, before it goes near production.
The deploy refuses a dirty tree, so production always equals a specific commit. Migrations are additive and rehearsed against a copy of live data first.
Hourly backups, a restore path we have actually tested, and one person to call when something looks wrong.
The operational controls behind the interface.
Start with a conversation. Build as small or as large as the problem actually is.
We map how the business actually runs today — the registers, the spreadsheets, the hand-offs that break — and work out where software would genuinely pay for itself. You leave with a written scope and an estimate, whether or not you hire us.
Book a consultationOne register, one workflow, one screen that replaces a spreadsheet people are already fighting with. Small, sharp, and in use within days.
Message usMulti-module, multi-role, multi-branch — the system the whole company works out of. Priced on how many modules, how many roles, and how much of your existing process has to be modelled.
Message usPricing note. A platform is quoted after the consultation, never off a list — a single register and a whole-company system are not the same job. Hosting, TLS, hourly backups, monitoring and ongoing changes are quoted alongside the build. Infrastructure and third-party licences are billed at actuals.
Spreadsheets, paper registers, Tally, WhatsApp, or a mix of all four. Show us where the hand-offs break, what nobody can see, and what has to be right every day.