Partnering With an SI to Reach Empanelment

A Gurugram product team had the better agent. A Noida SI had the empanelment letter, the BG limit and a resident engineer in every zone. The RFE required a turnover the product team would not hit until year five. They signed a two-page 'teaming agreement' a BD lead downloaded. Eighteen months later the SI sold a hosted chatbot under the panel, used the startup's logo in the bid, and staffed the work with their own graduates. The product team had a clause that said 'preferred technology partner'. Preferred is not appointed.

Partnering with a systems integrator is a standard Indian public-sector move. It is sometimes the only lawful way through a pre-qualification gate. It is also how product firms become unnamed subcontractors on their own category. The difference is the paper.

This guide is for founders who need the SI more than the SI needs them, which is the usual case, and who still want to exist after the panel. It is not a hit piece on integrators. Good SIs run payroll in districts you cannot. Bad SIs rent your DPIIT number and your adjectives.

Not legal advice. Consortium and subcontracting rules sit in the RFE and the GCC. Read those before you sign a WhatsApp 'we are together'.

When you actually need the SI

You need them when the RFE's pre-qualification is a gate you cannot pass alone: turnover, years of government experience, a specified number of similar work orders, a geographic last-mile, a PBG capacity, or an explicit rule that product firms must bid through an empaneled SI. Those gates are annoying and often lawful.

You do not need them when the RFE is written for OEMs or for startups with DPIIT relaxations you already meet. Adding an SI then is how you pay a tax for a meeting. See also the opinion on hiring a bid manager — do not confuse a channel with a capability.

You should walk away when the SI wants exclusivity across all of government, perpetual logo rights, and ownership of your foreground IP, in exchange for 'putting you on our empanelment'. That is not a partnership. That is an acquisition of your government future for zero rupees.

Structures and who they protect

Structure	Who is bidder	Your usual role	Protect this in writing
Consortium / JV as the RFE defines it	The consortium	Named member with a work package	Joint liability terms, lead, exit, who holds the panel after
SI is bidder, you are OEM	The SI	Manufacturer / OEM authorisation	Authorisation is project-specific; they cannot swap you after award without the buyer
SI is bidder, you are named subcontractor	The SI	Disclosed sub	Buyer approval path; payment pass-through; audit rights on your scope
SI is bidder, you are unnamed	The SI	Invisible	Usually refuse. Many GCCs forbid undisclosed subs. You will also be unpaid last.
You are bidder, SI is delivery sub	You	Prime	Only if you meet PQ. Cap the SI, disclose as required, keep architecture.

The paper that has to exist before the bid PDF

A teaming agreement or consortium MoU that names the RFE, the roles, the work-share percentages or at least the work packages, the exclusive or non-exclusive nature (prefer non-exclusive outside this RFE), the branding rules, the IP, the payment waterfall, and what happens if the SI bids a different product after using your annexure.

An OEM authorisation if that is the RFE's form. Make it project-specific, dated, and withdrawable if they bid a substitute. Do not sign a global MAF that lets them use your name on every state panel for three years.

A data and architecture schedule. If you sell on-prem and no-training-on-customer-data, the SI must not be free to move the workload to their hosted SOC. Write that. If they will not sign it, they are not selling your product.

• Payment: you invoice the SI on milestones that match the buyer's milestones, with a maximum lag written in days, not 'after we are paid and after internal approvals'.
• Staff: named key people for your scope, with a substitution rule.
• Non-solicit that is mutual and time-boxed, not a one-way ban on you hiring anyone who ever met the SI.
• Dispute: Indian law, a city that is not only convenient for them, and a right to tell the buyer if they ship a different stack.

How to pick an SI without dating the whole NCR

Pick the SI who already holds the panel or the PQ you lack, and who has delivered in the buyer's culture — a power PSU SI is not a municipal SI. Ask for a redacted work order in that culture. If they cannot show one, they are a brochure.

Meet the delivery lead, not only the alliance manager. Ask who will sit in the SDC at 2 a.m. If the answer is 'your team, of course', you are the subcontractor. Price that truth.

Run a small paid subcontract first if time allows — a pilot, a data-migration, a documentation pack. People who will not pay a small invoice will not pay a large one.

Avoid stacking three SIs 'for coverage'. You will leak price and look unfaithful in a small market.

After award: stay visible

Ask the buyer, politely and in the kick-off, to note your firm as the product OEM or named sub in the minutes. Many officers will. That minute is how you still exist at renewal.

Do not let the SI change the deployment to hosted because it is easier for their NOC. That change is a contract change. It may also be a DPDP and residency change. Escalate in writing.

Keep your own register of invoices and of defects. When the relationship sours, you will need dates, not vibes.

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 ask for a real contract they will pick another startup.

Then they were going to bury you anyway. A two-page fluff note is not cheaper than no deal. It is more expensive, because you will staff their bid.

We should give exclusivity to look serious.

Give exclusivity, if at all, for one named RFE or one named account for a short window. National exclusivity is how you die waiting for their pipeline.

The RFE forbids consortiums, so we must be invisible.

If it forbids consortiums it may still allow disclosed OEM or disclosed sub. Invisible is often non-compliant. Read the GCC. If invisibility is the plan, walk.

They have the relationship; we should not talk to the buyer.

After award, a quiet introduction in kick-off is legitimate. Secret side-selling is how you lose the SI and the buyer. Visibility in minutes is not side-selling.

A 21-day SI decision

Do this before you send them your technical annexure.

1. Days 1–3: decide whether you truly fail PQ alone. If you do not, stop.
2. Days 4–7: shortlist two SIs who hold the relevant panel or culture. Ask for a redacted work order and a delivery lead meeting.
3. Days 8–14: issue your teaming template with work package, MAF limits, architecture schedule, payment lag, and non-exclusivity outside this RFE. See who redlines in bad faith.
4. Days 15–21: sign one, or bid alone, or skip the RFE. Do not enter bid week on a handshake.

How this shows up in the file

Internal note: 'We will not provide a technical annexure to an SI without a signed teaming note that names the RFE, our work package, and the deployment constraint (on-prem / air-gap / no training on customer data). Exclusive national rights are rejected. Payment lag maximum: [n] days from SI's corresponding receipt.'

If you are the buyer: require disclosure of OEMs and subs, and forbid stack swaps after technical scoring without a re-mark.

What the next noting must contain

“Partnering With an SI to Reach Empanelment” belongs in a file, not only in a search result. A P5 Startup/Vendor should be able to point at one artefact that proves “SI partnership government AI”: a packet capture, a processing schedule, a scored evaluation row, a dated notice, or a refusal rule. If the only evidence is a slide, you have a heading.

An SI can carry turnover, geography and a slot you do not have. They can also bury your agent inside a staff-augmentation blob. Write the work-share before you lend the logo. DPDP 2023 does not define sovereign AI and does not write a blanket localisation rule for every model hop. CERT-In’s 28 April 2022 directions still set specified incident clocks and 180-day log retention in India for in-scope events. The November 2025 AI governance text is guidance, not a statute. A Proprietary Article Certificate, when it is lawful, lives in GFR Rule 166 — not Rule 161.

Write three dated sentences under C4 Empanelment & Routes: what was decided, which designation owns it after the next posting order, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the designation that owns “SI partnership government AI”, plus a deputy.
• Attach one artefact a stranger can open next year.
• Name the instrument you are actually using — Act, direction, GFR clause, GeM term, or guideline paragraph.
• Leave unsourced percentages, GMV slides and house forecasts out of the noting.
• Revisit when the model, the SI, the notice, the region or the posting changes.

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.