We take longer to start, and less time to finish.
Most of what goes wrong in these projects is decided in the first two weeks, before anyone opens an editor.
We listen properly
One conversation, on your floor if possible. We say the problem back in your words until you agree we have it.
We go away and think
No answer in the room. We look at how the work actually moves — the people, the steps, the workarounds nobody documented.
A scope and a fixed price
One page. What is in, what is out, what it costs, by when. Signed by both sides before anything begins.
Then we build it
Process, training and software together — because shipping only one of the three is how these projects quietly fail.
Anything that costs you money every week and lives in one person's head.
- Quoting and costing that guesses at margin
- Handovers between departments that lose things
- Approvals nobody can find the status of
- One person who is the only one who knows
- A system bought last year that nobody uses
- Reporting that takes three days to assemble
- Spreadsheets holding a critical process together
- Data in four places that never agree
- Tools that don't talk to the ERP you already paid for
Manufacturing and operations is where we are most useful, because that is where we have stood. The method does not care about the industry.
Four things, whatever the money.
Saying no to the wrong project is the only reason to believe us when we say yes to yours.
- —
A timeline we don't believe
We would rather lose the project than quote a date to win it.
- —
Work we can't do excellently
We will say so on the call and point you somewhere better.
- —
A project nobody inside owns
Without one named person who can decide, it will not survive contact with the floor.
- —
Replacing something that works
If the system is doing its job, the answer is not a new system.
Built by someone who ran the factory, not just the software.
15 years running a manufacturing business. The job was people, process and systems — every day, on the floor. Not slideware, and not somebody else's case study.
Purusham Labs is small on purpose. You deal with the same person from the first conversation to the handover. Behind that person is a delivery team that has shipped production software for companies far larger than ours.
The name is my grandfather's. Labs is because I like building things that haven't been built yet. Both are meant literally.
Tell us what isn't working.
Thirty minutes, no charge, no deck. If we are not the right people we will say so on the call and tell you who might be.