Getting Listed as a Preferred Vendor Post-Pilot

A Banaras Hindu University-adjacent institute in Varanasi ran an eight-week on-prem pilot on synthetic and then redacted academic-admin tickets. Officers liked the drafts. The registrar said, generously, 'we will make you a preferred vendor'. Nobody knew what the phrase meant in the purchase manual. A year later the pilot VM was off, the officers were back on Word, and a different firm had won an advertised bid the institute had to float because finance refused a handshake list.

Preferred vendor, empaneled vendor, rate-contract holder, and 'the people who did the POC' are four statuses. Only some of them exist in a given manual. A successful pilot is evidence you can attach to the next instrument. It is not the instrument.

This guide is for vendors who just got a kind word, and for officers who want to keep a working agent without walking into a vigilance story. It is not a way to lock out competition with a thank-you note. Prcept would rather be competed on a well-written RFP than listed by accident.

Not legal advice. University, municipal, PSU and central manuals differ. Read the one that pays.

What the pilot actually bought

A pilot, if paid, bought a time-boxed evaluation under a statement of work. If unpaid, it bought even less — a demonstration with data-handling duties you still had. In both cases the deliverable should have been a report: workflows, eval scores, incidents, where data sat, whether anyone trained on it (no), and whether officers would use it without the vendor in the room.

That report is the asset. Without it the kind word evaporates when the registrar changes. With it, a competent purchase officer can write the next specification, including the air-gap rows the pilot proved.

The pilot did not buy a three-year exclusive, a logo on the institute site, or a right to match any future bid. If a vendor asks for those as a 'success fee', refuse.

Lawful next steps after a good pilot

Next step	When it is honest	What the file needs	When it is a trap
Advertised / GeM bid using the pilot report as spec	Almost always, if you still want the thing	Spec, eval, estimated value, GeM-or-not sentence	Writing the spec so only the pilot vendor's UI fits
Limited tender among known capable firms	If the manual's limited-tender conditions hold	Reasons, list of firms, why not advertised	Listing only friends of the pilot
Onboarding onto an existing panel / RC	If a live panel category fits and its RFE allows mid-term add	The panel's own process, not a registrar email	Pretending a POC is a mid-term add
New empanelment RFE (maybe several firms)	If you want a pool for several departments	A real RFE, validity, mini-bid template	A one-firm 'empanelment' that is a PAC in costume
Single source / PAC-like path	Only if the true GFR or manual limb exists — rare for agents	The actual limb, reasons, finance	Uniqueness of a chatbot UI

What the vendor should do in the week after the demo

Send the report before you send the commercial. The report should be usable if they bid against you. That is the price of a public-institution pilot. If you withhold the eval so they 'have to take you', you are training them to distrust you.

Offer a transition price for 90 days so the VM does not die while they float a bid. Make it a small, lawful extension of the pilot SOW if the manual allows, not a stealth three-year AMC.

Give them language for a fair spec: outcomes, isolation, no-training, logs, languages — not your product name. If they still choose you on a scored bid, you earned it. If they choose someone else who meets the spec, the institution still modernised. That is allowed.

Do not write 'preferred vendor' on your website. Write 'completed a paid pilot at [only if they permit the name]'. Preferred is their word, and they probably used it loosely.

What the officer should do instead of a handshake list

Commission the report as an institute document, not a vendor brochure. An internal officer should sign that the facts are observed.

Take the report to purchase and finance with a recommendation: float this bid / use this existing panel / stop, the pilot failed. Include the failure mode if it failed. A failed pilot that is written down is a success of governance.

If several departments want the same agent, consider a panel or a ceiling-rate instrument so you are not running eight pilots. See the rate-contract comparison.

If a minister or a VC says 'just continue with them', write the legal path or write a dissent. Continuing without a path is how the next registrar inherits a mess.

Data after the pilot

Delete or return production-like data. Delete vendor copies of tickets. If the vendor's 'eval tenant' still holds names, that tenant is now an unauthorised store. Put deletion on the last invoice milestone.

If you will bid a production system, decide whether the pilot VM becomes production or will be rebuilt. Rebuild is cleaner. In-place 'we will just turn on more users' is how a pilot's weak identity model becomes a campus-wide incident.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

If we do not lock preferred status we wasted the pilot.

You bought information. Information is what public money may buy without a production contract. A lock that evades competition can waste far more.

The manual has no 'preferred vendor' chapter, so we can invent one.

If the chapter does not exist, you cannot invent a status that spends money. Use the chapters that exist.

A PAC is justified because they already know our system.

Familiarity is not a GFR limb. See the PAC pieces in this series. Knowledge of one UI is not proprietary manufacture.

We should keep the pilot data to improve the model for them.

Not without a written purpose and, if the product promise is no training on customer data, not at all. Delete.

The 30 days after a good pilot

Vendors and officers can run parallel columns of this list.

1. Days 1–7: freeze the report. Officer signs observations. Vendor sends deletion certificate for any personal data they should not hold.
2. Days 8–14: purchase workshop. Choose advertised / limited / existing panel / stop. Write why.
3. Days 15–21: if continuing use, extend the pilot SOW lawfully or switch the VM off. Do not run production on a handshake.
4. Days 22–30: draft the spec from the report. Remove product names. Issue or calendar the instrument.

How this shows up in the file

Officer note: 'The pilot dated … produced the attached evaluation. It does not create a preferred-vendor right. Recommended next instrument: … Reasons: … Pilot data deletion certificate is at folio …'

Vendor note: 'We will not market a preferred-vendor status. We will support a fair specification. A 90-day extension is offered as a separate, priced SOW if permitted.'

This article is informational field guidance for Indian public institutions and their vendors, not legal, tax, procurement or engineering advice. Confirm the live circular, RFE, GCC, GeM term, state G.O. and your counsel before you file anything. Incentives, ceilings and portal screens change.

How to run the route without confusing the letterhead

“Getting Listed as a Preferred Vendor Post-Pilot” is a route problem. A P5 Startup/Vendor 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 “preferred vendor government” is not the same as being on a panel that can receive a work order.

Pilots create evidence, not entitlement. The next lawful step is a documented evaluation, then a competitive instrument or a tightly reasoned exception. Do not ask a registrar to 'just empanel us'. 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 Listed as a Preferred Vendor Post-Pilot” 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 Startup/Vendor, not “the vendor.”

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