Nishant Mehta

I am Nishant Mehta, Co-Founder of Orospor Consultants and Services LLP. Gurcharanjit Singh had been building the practice since 2016; in 2023 we formed the LLP together. He is the engineer — infrastructure, software engineering, cyber defense, and the standard all of it is held to. My side is everything that has to exist around that engineering for it to reach a client and hold: how work is scoped and priced, how it is contracted, how it is staffed, how it is delivered, and who is answerable when a decision is needed. I do not make architectural decisions and I do not pretend to.

My background is management. Before Orospor I spent twelve years inside multinational corporations, in managerial and high-level positions, and that is where my operating instincts come from. Large organisations move on clarity — a defined scope, a named owner, a decision path, and terms that survive scrutiny from people who were not in the room when the work was agreed. What looks from the outside like a single decision is a sequence of approvals, and each function along it asks a different question. Engineering asks whether the architecture is sound. Procurement asks whether the commercial terms — and the supplier's own stability — will hold over a multi-year term. Finance asks what the number becomes in year three. A supplier who answers only the first question gets a good technical meeting and no contract. That is a preparation problem rather than a sales problem, and we structure our side of it accordingly.

Commercial discipline, in practice, is mostly the discipline of saying accurately what will happen. We quote what can be delivered, in the time it will take, with the people who will do it. Where a request sits outside what we should take on, we say so early — a declined engagement costs everyone far less than a mismanaged one. The same honesty governs the products. OroLink and OroStat are commercial systems, licensed, with the full source going to the organisation that licenses them, auditable line by line. That is a deliberate answer to the question procurement always reaches: can our own auditors verify what this software does, and what happens to us if Orospor is gone? It is a relationship with obligations running in both directions, and it is written down as such before anyone signs.

Most of what decides whether an enterprise relationship lasts happens after the signature. Reviews get scheduled and quietly dropped. Reporting arrives in a format nobody reads. An issue is raised at the wrong level and sits there for three weeks. Each of those is a management failure, and each is preventable. We agree the escalation path before it is needed — who is contacted, in what order, and who is accountable if the first two do not respond. Bad news should reach the client from us, with our assessment attached, rather than from their own monitoring. The published figures — 12,000+ global nodes, sub-5ms OroLink latency, 99.99% uptime — are Gurcharanjit's engineering when they are measured and an operating commitment every day after. A 99.99% commitment is really a question about three in the morning on a Sunday: who picks up, and what are they authorised to do without waking anyone else. My work is to make sure that answer exists in writing and does not depend on any one person being available.

The rest is people. Engagements come apart on an unowned dependency, a decision nobody made, a scope change that was discussed but never recorded — rarely on capability. Removing that is unglamorous, repeatable work, and it is most of my job. It is also what I hire for. I look for people who will take an outcome rather than a task, and then give them what that requires: explicit responsibility and the room to decide. We work from Jalandhar, Punjab, for organisations operating globally, across four practices. Gurcharanjit holds the engineering standard. I hold the standard for everything around it.