Anonymised engagements from lending desks to cold-chain fleets. Each one names the sector reality, the constraint, what we built, the stack and the measured result — not just adjectives.
Why we publish the sector reality, not just the win
Most agency portfolios show a logo, a screenshot and an adjective — "seamless", "robust", "game-changing" — which tells a buyer nothing about whether that team can solve their specific problem. A CRM built for a five-person startup and a CRM built for a 200-store retail chain look identical in a screenshot, and completely different in every decision that actually mattered.
The gap costs buyers at contract time: without the sector context, the real constraints and what was actually built, there's no way to judge whether a vendor's past work is relevant to your problem or just adjacent to it — so decisions get made on the size of the case-study logo instead of the size of the actual challenge solved.
Every engagement below names the sector reality it sat inside, the specific failures we found on day one, what we actually built module by module, and a measured before-and-after — so you can judge fit on substance, not adjectives.
What's in every case study
The four things a portfolio screenshot never tells you.
Sector reality
The industry constraints and rules the system had to work inside.
Day-one challenges
The specific failures we found before writing a line of code.
What we built
Modules, stack and integrations — named, not summarised.
Measured results
A before, an after, a timeframe and a named testimonial.
Downloadable reports we refresh on a schedule: how delivery is performing, and what custom software actually costs in India. Read them before you talk to us.
How our engagements performed this quarter: response times against the SLA, milestone punctuality, uptime on managed systems and the time clients got back from the delivery model. Published every quarter, whether the numbers are flattering or not.
94% of milestones delivered on or before the agreed date across 38 active engagements
Average first reply of 3 hours 40 minutes against the contractual 24-hour SLA, with zero breaches
99.96% uptime across managed production systems, with every backup restore-tested in the quarter
Thin-slice prototypes reached working software in 19 days on average from scope sign-off
Time returned to client teams per engagement, hours per monthView as table
What drives a ₹2–6 lakh build versus ₹8–20 lakh and beyond, the three variables that actually move the price, typical timelines per band, and the questions to ask any vendor before signing. Written for owners and CFOs, not engineers.
Three pricing bands with what fits in each, typical timelines and what is always included
The three variables that drive cost: user roles, integrations and genuinely custom workflow
A fixed-bid vs dedicated-team decision framework and the hybrid most SMEs should choose
Six vendor questions that separate a delivery partner from a body shop
Typical first-release timeline by pricing band, weeksView as table
