GeM Price Reasonableness for Novel Software

Finance asked for last purchase price. The indenting officer looked at the wall. Nobody in the ministry had bought an on-prem agent with a training ban and an air-gapped log store. There was no LPP. There was a vendor number that looked like a software company's Series B optimism.

Price reasonableness is still required. GFR and GeM do not waive it because the article is new. Rule 149 has long told GeM buyers to be satisfied about rates. PAC buying, where competition is thin or absent, is called out for extra diligence. Novel software is where that sentence either becomes a method or becomes a shrug.

This guide is for the officer who has to sign, and for the founder who has to give them something signable. It is not legal advice and it is not a promise that your finance wing will accept any one method.

What reasonableness is

It is not the lowest number on earth. It is a documented judgment that the public is paying a rate that a careful person would pay for that article, in that configuration, at that time. Competition is the usual engine. When competition is weak, the engine is paper.

For printers, paper is last purchase price, GeM historical offers, and rate contracts. For agent platforms, paper is a breakup, a few imperfect comparables, and a ceiling. Anyone who tells you to invent an LPP from a private WhatsApp quote is telling you to forge the only defence you have.

Methods that can be honest

Reasonableness methods for a novel agent buy

Method	Use when	What you put on the file	Failure mode
Competitive bid with generic specs	Substitutes exist	Bid report, L1, responsiveness note	Brand-locked specs that fake competition
Module breakup	Always, even after L1	Licence, implementation, support, exit, GST	One lump that cannot be compared
Public award search	Someone has bought something nearby	CPPP/GeM award printouts with differences listed	Citing a different article as if it were the same
Internal cost-build	No market	Effort days, roles, hardware, named assumptions	A vendor deck labelled cost-build
Independent technical estimate	Value is high or PAC is in play	A note from someone not selling the product	The seller's cousin

The breakup that actually helps

Ask for lines you can test. Perpetual or term licence. Environment count. On-prem support hours. Integration to named systems. Training seats. Exit export and deletion certificate. Optional year-two support. Hardware if the seller is bundling it, separately if the department will buy the rack on GeM.

Then mark which lines have a market and which do not. Support hours can be compared to other IT support bids. A model-runtime licence in an air gap may have no twin. Do not pretend the second line is as comparable as the first. Write the gap.

How two committees wrote the paragraph

A reverse auction printout is not, by itself, a reasonableness method for a first agent buy. It proves bidders flinched. It does not prove the start price was related to cost, and it does not prove the remaining articles were the same. If RA is all you have, write that limitation in the paragraph. Honesty about a weak method is still a method. Silence is not.

Hardware bundles confuse every comparable. If the seller is wrapping a GPU rack into the software line, split it. Buy the rack on a goods category where last purchase prices exist. Keep the agent line as software. Reasonableness then has a chance. A single lump called sovereign stack is how you certify a number nobody can rebuild.

What not to put in the note

• A screenshot of a US vendor's website with a casually converted rupee figure.
• The phrase market rate with no market.
• A comparison to a hosted seat licence when you are buying an air-gapped install.
• A claim that DPIIT recognition makes the price reasonable.
• A claim that because it is AI it must cost this.

Objections from both sides of the table

If we delay for a method, the year lapses. Then write a shorter method: breakup plus one public comparable plus a ceiling. A thin honest note beats a fat fictional LPP. Lapse is a budget problem. A bad certificate is a vigilance problem.

The vendor will not open their books. You are not entitled to their private margin. You are entitled to a modular price and a story that can be compared. If they will not even modularise, treat that as a reasonableness failure.

GeM already ran a reverse auction, so we are done. Reverse auction proves the bidders were willing to go lower than their start. It does not prove the start was related to cost, and it is a poor tool for novel quality attributes. Still write why the final number is not absurd.

PAC plus reasonableness is two signatures

A justified PAC makes reasonableness harder and more important. You have already told the file that competition cannot help. The rate paragraph is now the only public-interest control left on money. Do not bury it in the PAC form. Do not let the vendor's uniqueness slide stand in for a method. Sit them as two papers, two dates, two officers if your rules allow it.

For a novel agent, insist on a rate card that would still make sense if a second vendor appeared next year. Per-environment licence. Per-system integration. Per-quarter support. A fixed exit. If the seller will only give a cloud of rupees called platform, you cannot test anything except your own fatigue. Fatigue is not a method.

Independent estimates are worth the week when the value is high or the PAC is in play. The estimator should not be the indentor and should not be the seller. A NIC or SDC architect, a sister-department CISO, a campus computer-centre head: anyone who can say what a similar install cost them, and what was different. Differences belong on the page. Hidden differences turn a comparable into a fiction.

After award, keep the method. If a variation arrives, run the same tests on the delta. Reasonableness is not a gate you pass once and forget. It is a habit that stops a cheap PAC from becoming an expensive career.

Ten-day playbook before the reasonableness signature

• Day 1: demand a modular breakup in the bid or the PAC pack.
• Days 2–4: search GeM awarded contracts and CPPP for nearby articles. Print differences.
• Day 5: decide whether an independent technical estimate is worth the week.
• Days 6–7: write the method paragraph naming what you compared and what you could not.
• Day 8: set a ceiling or a cut on uncomparable lines if needed.
• Days 9–10: competent authority signs a note that a stranger could follow.

File note, ready to edit

Reasonableness of the proposed rate for [article] has been examined in the absence of a like-to-like last purchase price. The seller's modular breakup is at folio [x]. Public awards consulted: [list], with differences recorded. Residual uncertainty sits in [named modules] and has been capped at [figure or method]. Competition status: [open / single / PAC]. This certificate records a method, not a guarantee. It is not legal advice.

Prcept AI will give a modular government rate card: install, support, exit, no training on your data. Use it to write your reasonableness paragraph, including against us.

How a buyer or seller should act on this

Treat “GeM Price Reasonableness for Novel Software” as an operating problem, not a thought piece. A P2 Procurement who searches “price reasonableness certificate” is usually one bid, one CRAC, or one rejection away from a cash event. The file that wins is the one with dates, document names and a named officer — not a paragraph that restates GeM’s homepage.

Novel agents have no honest last-purchase price. Reasonableness is a method you write down: breakup, comparables you actually have, and a ceiling you can defend. That is why this guide ends in artefacts: screenshots of the live portal term, the clause you invoked, and the date you last checked it. GeM, GFR notes and state portals move. A citation without a date is folklore.

Confirm the live GeM FAQ, the current revenue policy and the bid text before you copy any number from a blog — including this one. If the portal and this article disagree, the portal wins. Put the printout in the file.

• Write the purpose of the buy in one sentence a DDO will sign.
• Name the route: catalogue, custom bid, bid, RA, CPPP, or state portal.
• Attach the exemption or preference documents you will actually upload (Udyam, DPIIT, MII, OEM).
• Record who can accept the consignee receipt and who raises the bill.
• Do not invent a category, a PAC, or a price-reasonableness story after L1 is public.

Close this loop before the next CAB

Put “GeM Price Reasonableness for Novel Software” 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. “price reasonableness certificate” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.