Understand first.
Build second.
An independent practice for businesses where the work is bigger than a single piece of software — equipment yards, retail counters, family-run manufacturers.
Most businesses don't have a software problem. They have a clarity problem.
If three of these sound familiar, we should talk.
More software rarely fixes any of these.
The hard part is the figuring out.
Understand
We show up, sit down, walk your floor. Plain talk, no slides. What you think's broken is almost never the real thing — finding the real one is the job.
Map
We pull the whole operation apart on paper before any code. Where the money leaks, where work waits, what breaks the moment someone's away.
Design
We build it around the people you've already got — they don't learn the software, it learns them. You sign off before a line of code gets written.
Build
Start with one thing, where it bleeds most. Get it live, then grow from there — no giant leap. Source, IP and logins are yours at the end.
The first thing we ask isn’t what’s broken.
It’s why you do it that way. Then plain questions, one after another, until the real problem shows itself. No jargon, no deck.
Walk me through what happens the moment an order comes in.
Why that step — and who decided it should work this way?
What breaks when the person who normally does this isn't here?
If this number's wrong, who finds out — and when?
Running in production. Today.
A family tyre dealership had outgrown Tally and a stack of Excel sheets. Margin surfaced two weeks late, after the accountant reconciled cash and credit.
One Next.js app on Postgres. FIFO batches keep landed cost honest; sales, purchases and cancellations move through atomic database functions.
The shop closes the day, not the week. Margin computed at the moment of sale. The owner sees what's owed, overstocked and idle without leaving the dashboard.
Chindaliya Rentals — multi-yard equipment ledger, dispatch without the owner in the loop. Goyal Ji — production records and dispatch for an FSSAI manufacturer.
What changed once the system shipped.
Margin unknown until the accountant closed the books, two weeks late.
Margin computed at the moment of sale. Books close on the day.
Dispatch ran on calls and WhatsApp; the owner was the integration layer.
Branch managers dispatch independently. Every yard on one screen.
Compliance docs, batch records and invoices in three stacks of paper.
One system covers production, QC and dispatch. Audit prep in hours.
Most software makes you bend to it. We build it to bend to you.
Off-the-shelf tools arrive with someone else’s idea of how your business should run. We build around the people you’ve already got — your team doesn’t learn the system, the system learns them.
The toolkit we use in our own engagements.
Free for everyone.
15 calculators for people running businesses — EMI, amortisation with Excel export, GST, margin, break-even, inventory. No login. No ads. Installs to your phone in two taps.
Most consultants study operations from the outside. I learned them from the inside.
Equipment rental, retail, logistics, hospitality, construction support — not advising from a boardroom, but as the person responsible for keeping things moving when customers were waiting, equipment was delayed, systems were breaking and decisions had real consequences.
LumenWorks was built from that. We study how work actually happens inside a business, find the friction, and build the systems it should have had in the first place. The phone is answered by the same person who designs the system and ships the code.
“Systems should serve the business — not become another thing the business must serve.”
Patterns we keep seeing.
Most businesses have more reporting than visibility.
The problem you can name is rarely the one that's actually costing you.
The number of WhatsApp groups a business runs on is roughly the inverse of how much it trusts its own systems.
Many approval chains exist because information arrives too late.
People avoid software because it slows down the work.
The system everyone fights with is the one built for someone else's business.
Three days before month-end is the wrong time to find out the books are off.
When the founder is the integration layer, the founder is the bottleneck.
Three ways to work with the practice.
Start with the conversation. If it’s a single problem, we scope a build. If it’s bigger than that, we embed.
First look
A focused 30-minute conversation — in person or on a call. Free, no obligation.
We listen to how the work actually moves today and tell you what we'd look at first. No proposal, no deck.
- Free
- ≈ 30 minutes
- In person or call
Build Sprint
One scoped operational system, designed and shipped.
Dashboards, internal tools, client portals, inventory and operations software. Source, IP and credentials handed over at the end.
- One scoped outcome
- IP transferred
- Investment by scope
Operating Partner
Long-term, embedded across the operation.
For businesses where the work is bigger than a single system. We run alongside leadership for four to six months at a time.
- 4–6 months typical
- Retainer-based
- Two slots active
Starter websites from ₹4,999 · Counter is free for everyone. Consulting is scoped per engagement.
Operational problem nobody’s figured out?
Thirty minutes. Free. No proposal, no deck — just a first look at where the work is stuck.
Replies within 24 hours · Mon–Sat