About
We build software other people have to live with.
That sentence is the whole company. Everything we do — how we scope, how we document, how long we stay — follows from taking it seriously.
Why we exist
We started Mehvexa in 2010 after a decade of watching the same thing happen. A business would commission software, an agency would deliver it, and within a year the people who built it were gone. The documentation was a folder of screenshots. Releases needed the one contractor who still remembered the deploy. The client owned a system nobody could safely change, and the agency had already moved on to the next pitch. We thought that was a choice, not a law. So we set up a company where the engineer who scopes the work is the engineer who builds it. Handover is a deliverable, not an afterthought. We stay attached to a system after launch, because that is when it starts to matter. It is a slower way to grow. Sixteen years on, we still think it is the right one.
That is why the company looks the way it does today. Three offices, in New York, London and Mohali, chosen so a client always has engineers online during their working day. Senior people on every engagement, because the hard decisions happen early and cannot be delegated. Scope, milestones and success measures written down before a contract is signed. Every repository, credential and document handed over with the code, so a client can leave us and keep working. Since 2010 that has added up to 174 delivered products across 56 countries, and a fair number of clients who never needed to leave.
What we believe
Four principles, and what each one costs us.
Engineering-led, not sales-led.
The people who scope the work are the people who build it. It costs us: we cannot bid on everything, and our proposals take longer to write.
Built to be owned.
Documented, tested and handover-ready from day one. It costs us: a client who can leave easily sometimes does.
Accountable to an outcome.
Scope, milestones and success measures agreed before work starts. It costs us: we have to say no to briefs that cannot be measured.
We stay for the hard part.
Production support, monitoring and iteration. It costs us: senior people stay attached to systems long after the invoice.
16+
Years building production systems
174+
Products delivered
3
Delivery regions
56+
Countries with clients
Leadership
The people accountable for your engagement.
Nirwair Singh
Accountable for every commitment we make to a client: scope, price, and who is on the team.
Navjot Kaur
Accountable for delivery across all three offices, and for the handover on every engagement.
Kunal Khurana
Accountable for the technical decisions on every engagement, and for the standard the code is held to.
Manav Sharma
Accountable for the operations behind delivery: staffing, working-hours overlap, security controls and production support.
Where we work
Offices chosen for overlap, not for cost.
New York (UTC−5) is where most engagements start: scoping, commercial and delivery leads for North American clients. London (UTC+0) carries delivery leadership and account management for UK and European clients. Mohali (UTC+5:30) is the engineering centre, where most of our engineers, QA and DevOps work. Office hours are 09:00–18:00 local, and the Mohali engineering team works 14:00–23:00 IST, so it overlaps about eight hours with London and about four with New York.
Tell us what you are building.
A 30-minute call with an engineer who will work on it.A 30-minute call with an engineer who will work on it. No sales sequence, no obligation.
Book a consultationor email us directly