Daniel Chand
Software Developer
Daniel contributes to the architecture, development, and continuous improvement of Stock Sewa, helping transform business requirements into practical and dependable software solutions.
Our story
How Stock Sewa got here
No pivot, no origin myth. Five decisions, each one made because the previous one turned out to be right.
01The observation
The software never fitted the work
Pharmacies, churches, schools and distributors keep everyday life running, and almost all of them were handed the same generic system with the labels changed. Counter staff worked around it. Office teams kept a second set of records in a notebook. The software was never the problem anyone set out to solve, so nobody solved it.
02The decision
One industry at a time, properly
The obvious answer — a configurable platform that bends to any sector — is the answer that produced the generic systems in the first place. So we took the slower route: pick one industry, learn how it actually works, and build a product shaped around that, not around a template.
03The first product
A pharmacy that could see every batch
Retail pharmacy came first because the cost of getting it wrong is visible daily: expired stock written off, purchase and inventory disagreeing, a queue at the counter while someone checks a shelf. Selling, batch tracking, purchasing and billing had to stay in sync automatically, or the product was not worth installing.
04The second product
The second one proved the method
Church management shares almost nothing with pharmacy at the surface — members and offerings instead of batches and invoices — but underneath it needed the same things: records people trust, reports that close cleanly, and a system that stays up on the busiest day of the week. Building it a second time is what turned an approach into a way of working.
05Today
One platform, many products
Both products run on the same engineering platform: the same stack, the same release discipline, the same people answering the phone. That is what makes a third industry a decision about focus rather than a decision about whether we can support it — and why the empty slot in our architecture diagram is the point of the diagram.
