Estimating Cost Before You Publish the Tender

Finance asked for the estimated cost so the NIT could go up. The indentor forwarded a vendor quotation and changed the letterhead. The quotation omitted GPUs, assumed a hosted model, and priced AMC as a courtesy. When bids arrived, everything was higher. Someone said the market had moved. The market had not been asked a complete question.

GFR practice wants a reasonable estimate before you invite prices you cannot judge. For a novel agent stack you will not have last-purchase price. You also should not invent a fake precision study with three decimal crores. Order-of-magnitude honesty is the adult move: a stack, bands, and assumptions written down.

This guide is for DDOs and indentors the week before the tender is published. It is not a costing certificate. It is the skeleton that stops a vendor PDF from becoming the official estimate.

The stack you can write without a consultant

Platform software for three years — licence or subscription — including the isolation mode you actually want. Implementation SI: discovery (if any), integration to named systems, training, documentation. Person-months in a band, not a hope.

Compute: GPU or CPU class, number of nodes, power and rack if you own them, or hosting if you honestly do not. Lead times belong here as calendar, not only as rupees. Department people: product owner, gate officers, a technical counterpart, DPO time. These are often free on paper and scarce in life. If you omit them, you have omitted the control.

AMC or years two and three: security patches, support hours, N refreshes or none, exit drill. Once: eval-set labour, redaction, perhaps an escrow verification, perhaps a PoC you will pay for.

Order-of-magnitude lines — fill bands, not theatre precision.

Line	What to write in the estimate note	Common lie to avoid
Platform	On-prem isolated vs named-egress hosted — pick one object	Averaging both because you have two quotes
SI	Months × a published rate band for named integrations	Implementation included with no hours
GPU / CPU	Class, count, whether already owned	Silence, to be indented later
People (department)	FTE fraction for gates and owner	Zero, because no invoice
AMC / Y2–Y3	Percent of platform or a quoted band; what is in	Year-one only
Exit / eval / escrow	Small, explicit, once or yearly	Goodwill

How to get bands without being captured

Look at recent CPPP and GeM awards for nearby objects — not AI, but on-prem software, SI months, GPU workstations. They are evidence, not gospel. Ask two or three firms for budgetary quotes against your stack, not against their brochure. Mark them as vendor inputs, not as the estimate.

Ask your SDC what a rack and a GPU node cost them last time, including power. Ignore a vendor who says compute is free because the model is efficient. Do not use the preferred vendor's quote as the official figure and then design a spec only they meet. That pair is an integrity story.

How this note works after bids arrive

When L1 or the QCBS winner lands, finance compares the stack to your bands. A bid far below the SI and GPU lines is a hollow bid, not a bargain. A bid far above should be explainable — extra site, extra language, a heavier isolation drill — or it is just dear.

If you never wrote bands, every number looks like a surprise. Surprises are how reasonableness notes become novels.

What this is not

It is not a sanction of a particular rupee figure as scientific truth. It is not a last-purchase price you invented. It is not a reason to reject a lawful L1 without a process. It is a map of the object so the invitation to bid is not a fishing expedition.

States and PSUs will have their own estimate and AA/ES rules. Follow those. This skeleton is the AI-specific filling.

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.

We cannot estimate what we have never bought.

You can estimate people, racks, and SI months. You can leave a wide band on the platform line. What you cannot do is publish a number you copied from the firm that will bid.

A wide band is unprofessional.

False precision is unprofessional. Write the assumptions next to the band.

Finance wants a single rupee.

Give a midpoint and a range, and say which object the midpoint assumes. A single rupee without an object is a fiction they will make you defend.

GeM catalogue price is enough.

It is a data point. Agent isolation, SI and GPU often sit outside the SKU. Read the live listing before you pretend it is the stack.

Write the estimate the week before the NIT

1. Day 1: freeze year-one cards and isolation mode.
2. Day 2: fill the six lines with bands and assumptions.
3. Day 3: collect two budgetary inputs and one internal compute note.
4. Day 4: separate vendor inputs from the departmental figure on the page.
5. Day 5: finance concurrence that this is an order-of-magnitude aid, then float.

How this shows up in the file

Subject: Order-of-magnitude estimate for the proposed agent procurement.

The attached stack covers platform, SI, compute, departmental effort, Y2–Y3 support, and once-off eval/exit items for the stated year-one cards. Figures are bands with assumptions, not a costing study. Vendor budgetary quotes are placed opposite and are not adopted as the official estimate. This note is not legal advice.

AA / ES language without fake precision

Administrative approval and expenditure sanction want a number they can print. Give them a midpoint, a range, and the object the midpoint assumes: two year-one cards, isolated on-prem, one site, three years, department-staffed gates. If leadership later adds four districts, the sanction is for a different object. Say that in the same paragraph so nobody treats the midpoint as a ceiling you must smash through with variations.

Write the assumptions as bullets a finance member can challenge: GPU already owned or not; SI months for named APIs only; AMC includes security patches but not a new language; exit drill included once. Challenged assumptions are how the estimate improves. Unchallenged vendor PDFs are how it rots.

If your organisation publishes estimated value on the NIT, publish the midpoint and keep the working on the file. If you do not publish it, still keep the working. A later reasonableness note that starts we had no idea is not a note. It is a confession.

This article is a field guide for Indian public buyers, not legal, procurement, financial or audit advice. Confirm every citation against the live GFR compilation on doe.gov.in, the relevant DoE procurement manual, GeM terms, CVC guidance and your own counsel before a sentence enters a tender file.

How to put this in the RFP, not the preamble

A P2 Procurement who searches “estimate AI project cost government” is usually drafting or scoring a bid. “Estimating Cost Before You Publish the Tender” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

You do not need a consultancy-grade costing model. You need a departmental stack — people, GPU, SI, platform, AMC — written before bidders teach you the number. QCBS weights are a choice you must publish before opening. Accuracy is a task plus a dataset, not a slogan. SLAs for agents must name tool-calls, human gates and log export — uptime alone is a hosting metric.

Do not let a vendor write the specification and then bid on it. Record unsolicited proposals. Pay for pilots that touch personal data. Write exit before you write go-live.

1. Move the control from the preamble into a scored or eligibility row.
2. Attach a one-page definition (accuracy, SLA, language, data handling).
3. Require an artefact in the technical bid, not a slide.
4. Extend the bid date if a corrigendum is material.
5. Minute the demo on your data, offline if you claimed air-gap.

Close this loop before the next CAB

Put “Estimating Cost Before You Publish the Tender” 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 P2 Procurement, not “the vendor.”

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