What we built, and why we built it that way
Written as engineering accounts rather than marketing summaries — the real constraint, the decision it forced, and the parts that were genuinely hard.
Client names are withheld under confidentiality, and outcomes are described qualitatively where we do not hold a clean measured baseline. We would rather be vague than precise about something we cannot evidence. Outcomes are specific to those clients and are not a prediction of your results — see our Disclaimer.
Replacing four disconnected systems with one patient record
A 120-bed multi-speciality hospital in Maharashtra
A hospital running separate software for OPD, pharmacy, lab and billing, where a discharge bill took two hours to assemble by hand.
Finding out which trips actually made money
A transport contractor running 140 vehicles across west India
An operator with healthy revenue and unpredictable profit, because fuel, driver advances, tolls and detention never reached the trip they belonged to.
An MVP that survived contact with a regulated market
An early-stage lending startup in Bengaluru
A founding team with ten weeks of runway before a funding conversation, needing a working lending product rather than a prototype.
School software teachers did not abandon
A school group with five branches and about 4,200 students
A group on its third attempt at school software, having twice bought systems that administrators used and teachers quietly ignored.
A replatform that did not lose a day of trading
A D2C apparel brand shipping about 900 orders a day
A brand outgrowing its hosted storefront, needing custom logic its platform could not express — without a migration that cost it a peak week.
Learning what a finished part actually cost
An auto-component manufacturer in Pune with about 180 employees
A manufacturer quoting from estimated costs, discovering after implementation that two of its highest-volume parts were being sold below cost.
Using an LLM where it helps and rules where it must
An insurance intermediary processing about 3,000 claims a month
A claims operation drowning in unstructured documents, where a fully automated extraction would have been both unreliable and unacceptable to auditors.
Billing that keeps working when the internet does not
A supermarket chain with 22 stores across two states
A chain whose cloud POS stopped billing during every connectivity outage, in a business where a stalled counter empties the store.
Let's talk about what you're building
Tell us what you need and we will come back with a scoped estimate and a realistic timeline — within one business day.