Skip to content
Brihat InfotechBrihat Infotech

Delhi NCR

Where the procurement rules are written, and the systems they govern.

Custom software and platform engineering for central government departments, PSUs and institutional buyers in Delhi — built to the documentation standard public procurement actually asks for.

The short answer

Brihat Infotech serves Delhi from its Noida office, an hour away, with on-site discovery and in-person phase reviews. The work here is weighted towards central government departments, PSUs and institutional buyers, where GFR procurement rules and STQC documentation shape the build as much as the requirement does.

We do not have an office in Delhi.

Run from Noida, under two hours door to door. Discovery is on site, pre-bid meetings are attended in person, and phase reviews happen in your building rather than on a call.

The market

What makes Delhi different.

Delhi's enterprise buyers are disproportionately institutional: ministries, regulators, PSU headquarters, industry bodies and the national offices of organisations run from elsewhere. That changes what a software engagement is. The constraint is rarely the technology — it is a procurement process with a fixed evaluation matrix, an audit trail that has to survive a CAG review, and a documentation burden most vendors discover after signing.

Regulation

What actually shapes a build in Delhi.

Not a compliance checklist — the specific rules that decide architecture, retention and reporting before a requirement is written.

GFR 2017 and GeM

General Financial Rules govern how a government body may buy software at all. The evaluation matrix is published with the tender, and a proposal that ignores its weighting loses on arithmetic rather than on merit.

CVC guidelines

Central Vigilance Commission expectations on transparency shape what has to be logged, retained and produceable — which is a system design constraint, not a policy footnote.

STQC empanelment

Security and quality certification from a recognised body before a government system goes live. Designing for it from phase one is materially cheaper than retrofitting.

MeitY cloud empanelment

Government workloads must sit on empanelled infrastructure, which constrains the architecture before a line is written.

The estate

What is already in the building.

Anything new has to talk to these, and usually cannot replace them on day one.

  • NIC-hosted departmental portals
  • Legacy PSU ERP installations
  • Paper file movement with a digital veneer
  • Departmental Excel registers
Where the buyers are

Delhi business districts.

Run from Noida, under two hours door to door. Discovery is on site, pre-bid meetings are attended in person, and phase reviews happen in your building rather than on a call.

  • Connaught Place and Barakhamba Road
  • Nehru Place
  • Bhikaji Cama Place and RK Puram
  • Dwarka

Before you ask

Questions about working with us in Delhi.

Do you have an office in Delhi?

No. The office is in Noida, which is under two hours from central Delhi, and NCR engagements get the same on-site discovery and in-person reviews as any other. We do not claim a presence we do not have.

Can you meet STQC and GeM requirements?

We design for STQC from the first phase rather than retrofitting, and we have delivered against GFR-governed procurement. Whether we can bid on a specific tender depends on its turnover and headcount floors, which are set in the document before capability is assessed.

How do you handle a CAG or vigilance audit trail?

Retention, immutability and produceability are architectural decisions taken in the Define phase, not features added later. What has to be logged and for how long comes out of the tender and the department's own retention policy, and it goes into the target architecture as a constraint.

Working somewhere else in India? See every market we cover. The method does not change by city — only how much of it happens in your building.

Next step

Bring us the problem. We will bring the architecture.

A discovery call takes forty-five minutes. You leave with our read on the problem, the shape of the system we would propose, and a straight answer on whether we are the right team for it.

  • No sales deck
  • An engineer on the call, not an account manager
  • NDA before you share anything