The practice, and the person behind it.
LumenWorks is led end to end by one practitioner. The same person who studies your operation builds it, and answers when you call. Here’s where that comes from.
Most consultants study operations from the outside. I learned them from the inside.
Not from a boardroom, but from the day-to-day reality of running a business: customers waiting for answers, deliveries running behind schedule, equipment breaking down at the wrong time, and decisions that carried real consequences.
Before founding LumenWorks, I spent years inside operating businesses. Solving problems wasn’t a presentation or a framework. It was the work itself. Every improvement had to function in the real world, under real constraints, with real people depending on it.
That experience shaped how I approach every engagement today.
LumenWorks exists to understand how a business actually works before recommending how it should change. The goal isn’t to introduce more software, more processes, or more complexity. The goal is to remove friction, improve clarity, and build what supports the way people actually work.
From diagnosis and design to implementation and support, every engagement is led end to end by the practitioner who runs the practice.
Because the most important part of the work is making sure the right thing gets built in the first place.
Understand first. Build second.
“Your software should work for you. Not the other way around.”— Rahul Chindaliya, Founder, LumenWorks
Patterns we keep seeing.
The WhatsApp group becomes the ERP.
Nobody trusts the report, so everyone builds their own.
Most businesses have reporting. Fewer have visibility.
When the owner becomes the integration layer between tools, the owner becomes the bottleneck.
Many approval chains exist because information arrives too late.
The problem you can name is rarely the one that's actually costing you.
Three days before month-end is the wrong time to find out the books are off.
Most businesses aren't short on data. They're short on confidence in it.
The work usually isn't broken. The information flow is.
The rules that protect the quality of the work.
Code, credentials and documentation, handed over at the end.
No lock-in. No dependence on us.
Most businesses already have tools that work: Tally, Excel, WhatsApp, email.
We build around reality, not around a clean slate.
The truth rarely lives in the org chart. It lives with the people closest to the work: the ones entering the data, taking the calls, managing the stock, handling the customers.
If we can't talk to them, we won't understand the business.
Most projects start with software. We start with understanding: how information moves, how decisions get made, where the friction sits.
Only then do we decide what should be built.
If we don't understand it, we don't build it. Guessing is expensive.
Taking the time to understand is usually cheaper than rebuilding later.
We take on only what we can see clearly. When attention gets divided, the work suffers.
We'd rather say “not yet” than do rushed work.
Your business shouldn't depend on us forever. The work should be understandable, maintainable and transferable.
Your team, or your next developer, should be able to run it.
The person who answers is the person doing the work. No account managers, no layers, no relays.
Just direct conversations.
Monday to Saturday, even when we're in the middle of a build.
Better businesses waste less.
Less time looking. Less work repeated. Less money going somewhere nobody intended. More clarity. More control. More room to grow.
LumenWorks — technology for businesses that intend to keep improving