Our People
SakhiSoft is a senior engineering team, not a body shop. The people who scope your project are the people who build it — and the ones who answer when something breaks at 3am.
Leadership
Leadership here is hands-on. Every person below still reviews code, sits in architecture calls or joins client demos.
Founder & Chief Executive Officer
Founder of SakhiSoft. Sets the company's direction and stays close to delivery, sitting in on architecture reviews for every major engagement. Works directly with clients to turn operational problems into software that ships.
Chief Technology Officer
Owns the technical bar across every engagement — architecture decisions, code review standards and the engineering interview loop. Believes boring, observable technology beats novelty on anything that has to run at 3am.
Delivery Lead
Runs the sprint cadence, demos and written status across all client teams. The person who tells you a date is slipping the week it starts slipping, rather than the week it was due.
AI Lead
Leads the applied AI practice — retrieval systems, document intelligence and evaluation. Pushes back hard on AI features that cannot be measured against a baseline.
How we work
Culture is what survives a bad week. These are the practices we hold to when a deadline is tight.
Decisions live in a written decision log, not in someone's memory or a call nobody recorded. New joiners read their way in; clients can audit why a choice was made a year later.
If a date is slipping or an estimate was wrong, it goes in the weekly status the week we know — not the week it was due. Nobody here is punished for raising a problem early.
The engineer who builds a feature sees it through review, release and the first week of real traffic. Handing work over the wall to an ops team is not how we operate.
We choose mature, observable technology for anything business-critical, and save the novelty for problems that genuinely need it. Future maintainers are a stakeholder.
Every change is reviewed by someone who did not write it. Reviews explain the reasoning, not just the objection — that is how the bar rises across the team.
Meetings are clustered, standups are short, and the rest of the day belongs to the work. Overtime is a planning failure, not a badge.
If you want to own features end to end, work with people who review your code properly, and never be asked to ship something you would be embarrassed by — talk to us.