"Why not NIC, NICSI, CDAC, NeGD?" — the comparison done right

What the FA is actually asking

The literal question: "Why not NIC?" But the FA is really asking: "Has the in-house government IT capacity been formally consulted, on file, with documented response?" If the answer is no, the file is procedurally weak regardless of the substantive merit.

The bigger context: NIC + NICSI + CDAC + NeGD collectively offer significant capability. Many requirements they meet well. Many they meet partially. Many they don't fit. The file's job is to document which case applies — with evidence.

Why thin responses fail

The most common failure: silence. The file simply doesn't mention NIC. The FA returns it asking why.

The second: a one-line note saying "NIC not considered as private vendor selected". This is procedurally insufficient.

The third: an undated email forward saying "NIC said they can't do it". The FA wants a written response on NIC letterhead, dated, signed, attached to the file.

The shape of a holding response

Part 1 — Formal NIC consultation

A written request to your department's nodal NIC officer, with the requirement specifications attached. NIC responds with one of:

• "We can take this on, our timeline is X, our capacity slot is Y" — proceed with NIC
• "Our standard product covers 70% of this; the remaining 30% is custom" — partial fit; needs decision
• "This is outside our standard offerings" — full external procurement justified
• "Our queue is X months out for new modules" — timeline-driven decision

NIC's response (whatever it is) becomes an annexure to your file. The FA then has a clear basis for the decision.

Part 2 — Comparative analysis against NIC standard offerings

Map your requirement against NIC's standard products:

• NIC eOffice — file movement, dak, noting
• NIC eHRMS — attendance, leave, payroll
• NIC eProcurement — tendering, vendor management
• NIC eHospital — patient registration, ward management
• NIC eGramSwaraj — panchayat-level governance
• NIC eCourts, eCommittees, eChhawni, eGranthalaya — sector-specific platforms

For each closest-fit standard product, document:

• What it covers (% of your requirement)
• What it doesn't cover (specific gaps)
• Whether the gaps can be configured (NIC config) or need code (NIC custom + queue + timeline)
• Whether NIC code customisation gives you the operational flexibility your requirement needs

Part 3 — The NICSI / CDAC / NeGD parallel exercise

Same exercise for the other in-house options:

• NICSI — typically faster than NIC for specific carve-outs; uses panel vendors; cost varies
• CDAC — strong for HPC, language tech, specific R&D-adjacent work
• NeGD — DigiLocker, UMANG, Aadhaar-stack integration, MeitY initiatives
• STQC — testing & certification

Part 4 — Recommendation note

Closes the loop:

• Why a private vendor is the appropriate choice for this specific requirement, this specific timeline, this specific budget head
• What aspects of the in-house option remain leveraged (e.g., NIC eHRMS for adjacent modules, custom build for the gap module only)
• How the chosen vendor integrates with NIC infrastructure (single sign-on, data exchange, NIC cloud hosting if applicable)

The legal anchors

• MeitY policies on government IT — preference framework
• NIC Act / NIC charter — scope of NIC's mandate
• Office Memoranda from DoE on in-house preference
• GFR Rule 153 — in-house resource consideration
• Your departmental procurement manual — most have an explicit "consider in-house first" provision

Typical FA pushback patterns

• "NIC's response is from 4 months ago — refresh it" — pre-build a 2-stage NIC consultation: scoping, then specific RFI
• "Why not phase: first NIC standard, then external custom?" — answer with the integration analysis
• "Has the cost difference been quantified?" — link to cost-reasonableness annexure with NIC-as-comparable analysis
• "Did you consider NICSI panel vendors?" — pre-attach NICSI panel review

What we hand you

• A formal NIC consultation letter template drafted to elicit a specific written response
• A comparative-analysis matrix against the closest NIC standard product
• A NICSI / CDAC / NeGD parallel exercise documented
• A recommendation note for your file
• An integration plan documenting how our build complements NIC infrastructure
• A second-round pushback pack for the four most common FA NIC challenges

Read the rest of the FA-Objection Field Guide

• The pillar — all 8 FA objections at a glance
• 1. Cost reasonableness — defending the price tag
• 2. Single-vendor / Rule 161 nomination — the 70% kill zone
• 3. IPR transfer & source-code escrow — owning what you bought
• 4. Scope creep & cost overrun — the change-control protocol
• 5. Hosting — on-prem vs NIC vs cloud vs hybrid
• 6. Exit terms & vendor lock-in — the 14-clause exit annexure
• 7. "Why not NIC / NICSI / CDAC?" — the comparison done right
• 8. MSME / GeM / Make-in-India preference — the screen note

Related reading

• Big Helpers Government & PSU programme
• 7 legitimate procurement routes (no GeM, no MSME yet)
• Vendor lock-in: hidden ₹crores in PSU IT
• NIC eHRMS alternatives