All insights

Empanelment & Routes

Getting Your First Government Reference Client

· 9 minute read

The first reference is a completion certificate for a small, lawful, performable job. It is not a logo on a slide and not an unpaid 'national pilot' that never became a file.

Every deck in the accelerator had a page titled 'in discussion with 11 ministries'. None of the founders could show a work order. One had an unpaid pilot on a professor’s laptop that the registrar had never seen. When a real GeM bid asked for a government completion certificate, the page titled 'in discussion' scored the number it deserved.

A first government reference is a named legal person, a lawful instrument, a defined scope that you actually finished, and a piece of paper that says so. Everything else is pipeline theatre. Theatre is allowed in a private notebook. It is not allowed in an affidavit.

This playbook is for Indian AI startups who need that first paper without bankrupting themselves on a ministry-shaped fantasy. It is not a list of officials to WhatsApp. It is a sequence of scopes and instruments that tend to complete.

Pick a completable object, not a transformation

Good first objects are boring: a retrieval assistant over a closed circular corpus, a drafting aid with mandatory human send, a helpdesk classifier that does not write to the system of record. They finish. They produce before/after samples you can redact.

Bad first objects are 'AI for the whole citizen lifecycle' and 'replace the grievance system'. They do not finish. They also scare the DPO.

Campus and municipal objects often complete faster than line-ministry objects because the competent authority is closer to the user. Prestige and completion are different KPIs. Choose completion.

Pick an instrument that can end in a certificate

A small GeM bid or a campus purchase order is a better first reference than an informal pilot. Informal pilots die when the champion transfers, and they leave no paper.

If they insist on a pilot, write it as a paid discovery with a PO, a start and end date, a no-personal-data rule or a tightly listed data class, and a completion letter as a deliverable. Free, endless, and undocumented is not a go-to-market. It is a hobby the department cannot admit.

Empanelment without a work order is not a reference. Do not list it as one.

If you cannot name the instrument, you do not have a client. You have a conversation.
ShapeWhy it can become a referenceHow it usually fails to become one
Small GeM / campus POThere is a contract and a paying legal personYou overscoped and never reached acceptance
Paid discovery with a letterYou can define 'done' in a week countYou allowed it to become unpaid production
NICSI / state WO as a named subSometimes the SI will give a completion letterYou were invisible and cannot show the paper
Unpaid laptop demoAlmost neverNo instrument, no data rules, champion transfers
MoU with a ministryRarely, if it includes a funded SOWMoUs without money are press, not references

Ask for the paper while they still like you

Build the completion certificate into the SOW. Provide a draft that states period, scope, that the work was completed, and — if true — that they permit a named, modest reference. Make it easy.

If they cannot logo you, a redacted WO plus completion without publicity is still gold for the next bid. Logo and exhibit are different trophies. Take the exhibit.

Store the paper in the experience drawer the day it arrives. Future you is a desperate bidder. Help them.

  • SOW small enough to finish in one competent-authority tenure.
  • No production personal data unless the file already allows it.
  • Human-in-the-loop on anything outward-facing.
  • Acceptance test of ten cases, not a vibe.
  • Completion letter as a numbered deliverable.

How to find the first buyer without eleven fake ministries

Start with institutions that already buy software on GeM: universities, municipal bodies, state societies, smaller PSUs. Search GeM for what they actually bought last year, not for what a conference slide said.

Use DPIIT and Udyam only as eligibility, not as a pitch. Pitch the completable object and the on-prem or campus-rack path.

A systems integrator with a live WO may give you a first paid slice. Take it if the completion paper path is written. Refuse it if you will be unpaid labour behind their logo.

Do not put the national emblem on your site. Do not imply a ministry endorsement you do not have. Do not name an officer without permission.

Do not describe a pilot as production. Do not describe a campus as a ministry. The next ATC’s affidavit will ask you to be precise. Practise precision now.

If the work went badly, do not invent a certificate. A clean no-reference is better than a forged yes.

The stories that keep founders away from small POs

If your ego needs a ministry, your company still needs a completion certificate.

Small campus work will brand us as small.

The next bid does not score brand. It scores similar work in the format they annexed. Small and finished beats large and mythical.

If we do not do it free they will pick a Big Tech pilot.

Then let them. A free production service is not a reference; it is a dependency they can end without paying. Price a discovery or walk.

We can use a private bank as 'regulated industry' experience.

Only if the next ATC says so. Many government notices want government work. A bank letter is a different drawer. Keep it; do not relabel it.

The SI said we can claim their WO as ours.

Only if the bid allows consortium/sub experience and the paper names you. Otherwise you are writing fiction.

A ninety-day first-reference run

One object, one instrument, one letter. Not eleven discussions.

  1. Days 1–10: pick three completable objects you can staff. Kill the transformation narrative.
  2. Days 11–25: find three institutions that bought similar software on GeM or campus tender last year. Write them a one-page SOW with a completion letter as deliverable.
  3. Days 26–40: bid or negotiate one instrument. Prefer paid. Write data rules.
  4. Days 41–80: deliver against the ten-case test. Do not expand scope without a change note.
  5. Days 81–90: obtain the letter, file it in 04-experience, write the redacted sample, and only then update the deck — in language the letter supports.

What goes in the file — the first-reference pack

Instrument (PO/WO/bid award), SOW, acceptance record, completion letter, invoice, permission note for any public mention, redacted sample. That pack is the company.

If the client refuses a letter, file the PO and your own completion report plus the email thread. It is weaker. It is still better than a slide.

This playbook is commercial field guidance, not a guarantee of award and not legal advice. Publicity using government names and emblems is restricted. Follow the client’s rules and applicable law.

How to run the route without confusing the letterhead

“Getting Your First Government Reference Client” is a route problem. A P5 GovTech Founder should know which legal person they are talking to — NIC, NICSI, a state IT corporation, iDEX, or a GeM buyer — and which paper that person can actually issue. Searching “first government client startup” is not the same as being on a panel that can receive a work order.

The first reference is a completion certificate for a small, lawful, performable job. It is not a logo on a slide and not an unpaid 'national pilot' that never became a file. Empanelment letters are not purchase orders. DPIIT recognition is not a technical score. Reserved startup seats, if a notice writes them, are local to that notice. IndiaAI compute empanelment is not NICSI application-software empanelment.

Keep a warm evidence pack: CIN, GST, DPIIT, Udyam, financials, work-completion letters, architecture one-pager, DPA draft. Renewals are lost by people who treat the panel as a trophy.

  • Screenshot the live RFE paragraph you are relying on, dated.
  • Match the bidding entity name across every certificate.
  • Do not mix iDEX, TDF, NICSI and GeM clocks on one tracker cell.
  • Record the validity end date 90 days before it dies.

Close this loop before the next CAB

Put “Getting Your First Government Reference Client” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P5 GovTech Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “first government client startup” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

Questions this usually raises

Does a paid pilot count as a government reference?
It counts if there is an instrument and a completion paper that matches what the next bid wants. A handshake pilot usually counts for nothing.
Can a university count as a government client?
Often as a public institution, depending on the next ATC’s definition (Central / State / PSU / government-aided / autonomous). Read that definition before you claim 'government'.
Should we do the first job at a ceremonial rupee one?
Be careful. A rupee-one production service can create GeM and audit confusion, and it trains the client that your work has no price. A priced discovery is cleaner. Confirm any rupee-one idea with counsel and the buyer’s finance, not with this FAQ.
Is being DPIIT recognised a substitute for a reference?
No. It may relax a prior-experience row if the bid says so. It is not a completion certificate.
Can we name the department on our website?
Only with permission and without misusing emblems or implying endorsement. Default to the exhibit in the next bid, not to a homepage banner.

Sources