Consortium Bidding for Small AI Vendors

Three founders met in a Koramangala café the week a NICSI-adjacent notice appeared. One had the agent. One had a prior government implementation. One had the people who could sit in a state data centre. They drew a triangle on a napkin and wrote 'consortium'. Nobody wrote who would be jointly and severally liable if the agent hallucinated a beneficiary name into a public notice.

Indian public bids sometimes allow consortiums, sometimes allow a lead with named sub-contractors, and sometimes forbid both. There is no universal format you can download and treat as law. The bid you are looking at is the only constitution you have. A café triangle is not an amendment to that constitution.

This guide is for small AI vendors who need a larger friend to clear experience or manpower rows. It is commercial field guidance, not legal advice. If the work is real, pay a lawyer to turn the clauses below into an agreement that matches the live notice.

Only when the bid says so

Read the eligibility chapter before you call a partner. Some notices say a consortium is permitted with a maximum number of members, a lead who must meet a subset of criteria, and a jointly signed form. Some say no consortium, no joint venture. Some are silent, which is not permission.

GeM custom bids inherit whatever the buyer wrote. NICSI and other empanelment RFEs write their own membership rules. Do not import a World Bank JV template into a notice that never invited one.

If the bid forbids consortium and you still need a partner, the lawful shapes are usually prime-and-sub (if sub-contracting is allowed) or a no-bid. A hidden sub who is actually performing the essential scope is how buyers later allege misrepresentation.

What the buyer is actually afraid of

Buyers are not against small firms. They are against an award that dissolves into three invoices and no one to sue. Joint and several liability is the usual answer: the department can recover from any member for the whole. If your partner will not accept that sentence, they are not a consortium member. They are a tourist.

The second fear is eligibility shopping — each member bringing one certificate so that together you 'meet' everything, while no single firm can perform the essential work. Many bids therefore say the lead must meet the deployment or experience row, or that essential scope cannot be sub-let. Respect that even if it hurts.

The third fear is foreign control wearing an Indian lead. If the ATC cares about Indian legal entity, data residency or Make in India, a consortium cannot launder a foreign hosted model through a local invoicing partner. The architecture is still the architecture.

If you cannot fill the right-hand column, you do not have a consortium. You have a group chat.

Question to settle before the logo slide	Weak café answer	File-ready answer
Who is the lead	We will decide after we win	Named lead who signs, invoices, and holds the DSC
Who is liable to the buyer	Each for their part	Joint and several if the bid requires it; written among yourselves to match
Whose experience counts	Whoever has a PDF	Only the experience the bid allows to be counted, with work orders in that member’s name
Who holds the data and the model	The AI startup, obviously	Named processor, named hosting, named exit — consistent with the technical bid
Who gets paid, and when	We will split 40/40/20	A payment waterfall after the lead receives GeM / PAO money, with times, not vibes
Who can exit	Anyone, with notice	No exit that leaves the buyer with an incomplete essential scope; substitution only if the bid allows

Evidence, the packet, and whose stamp is on which annexure

Every annexure has a person. Turnover certificates must say which member’s books they are. Work-order experience must be in the name the bid will accept. Integrity and non-blacklisting usually need to be true of all members, not only the lead.

Power of attorney or authority letters must match the portal identity. A lead who cannot bind the others is a lead only on Slack. If the bid supplies a consortium form, use that form. Do not invent a friendlier one.

Technical scope should be split in a schedule the buyer can read: who supplies the model runtime, who does the SDC install, who staffs the helpdesk. Vague 'partners will support' language is how day-60 blame starts.

The private agreement the café never writes

The buyer’s form is not enough to protect the small AI vendor. You still need a private consortium or teaming agreement: IP in the agent and the prompts, who may reuse the work elsewhere, who pays for extra GPU time, who owns a fine-tune trained — if ever — on whose data, and what happens if the lead is slow to pass through payment.

Government payment cycles are long. If the lead is a large SI, the small firm can die waiting for an internal AP queue that is not in the GeM SLA. Put a pass-through clock in the private agreement. Do not rely on goodwill after the banner goes up.

Non-solicit and non-circumvent clauses should be modest. The department is allowed to talk to any member. You cannot contract to hide a specialist from the buyer.

• Match the bid’s liability sentence; do not contradict it privately.
• Name the essential scope that cannot move without buyer consent.
• Write IP and model-weight ownership in words a later investor can understand.
• Write a payment pass-through clock and a dispute path that does not stop delivery.
• Write substitution rules that defer to the bid.

When not to consortium

If you can meet the bid alone, adding a logo usually adds a tax, a delay and a future argument. Consortiums are for gaps the bid will not waive.

If the only partner who can clear the experience row will not accept joint liability or will insist on replacing your runtime with their hosted model, walk. You would be bidding a product that is no longer yours.

If the bid is silent on consortium, do not 'interpret' silence as yes. Ask in pre-bid. If they say no, believe them.

Comfortable sentences that blow up after award

If you hear these in the partner call, stop the logo slide and open a document.

We are all friends; we do not need joint and several.

The buyer is not in the friendship. If the bid requires joint and several, a private 'each for their part' is a contradiction the file will not honour. Friendship is not a performance guarantee.

The SI’s old work orders will cover us even if the bid says lead-only experience.

They will not. Experience counts the way the notice counts it. Shopping certificates across members against a lead-only row is a responsiveness fail waiting to be marked.

We will sign the official form and write the real deal later.

Later is after you are bound to the buyer on the official form. The real deal has to be signed before upload, and it cannot promise the buyer something different from what you signed with the buyer.

Consortium is always allowed for startups under Startup India.

No. Startup India relaxations, where a bid implements them, speak to EMD, turnover and experience — not to a universal right to combine firms. Consortium is a bid-specific permission.

Ten days to a consortium you can upload

Do this only after you have confirmed the live notice allows the shape you want.

1. Day 1–2: extract the consortium clauses. Maximum members, lead tests, liability, forms, whose experience counts.
2. Day 3: pick the lead for portal and payment reasons, not ego. If the AI firm cannot be lead, decide whether you still want the work.
3. Day 4–6: draft the private agreement — liability match, scope schedule, IP, pass-through clock, substitution. Send it to counsel.
4. Day 7–8: collect member-wise annexures. No shared 'group turnover' fiction unless the bid allows consolidation.
5. Day 9: sign buyer forms and private agreement. Align technical bid with the scope schedule.
6. Day 10: upload as the lead, with every member document named. Store hashes. Stop adding logos.

What goes in the file — yours and theirs

The buyer’s file should contain the consortium form the bid supplied, authority letters, member-wise eligibility evidence, and the liability sentence. They do not need your café napkin. They do need to see that the lead can bind the others.

Your own file should contain the private agreement, the scope schedule, the pass-through clock, and the exact packet. If the partnership sours, that folder is the only memory that will matter.

Consortium structures are bid-specific. This is not legal advice and not a standard form. Joint and several liability is a common buyer requirement, not a universal statute. Use counsel and the live notice — GeM ATC, CPPP RFP or NICSI RFE — before you sign.