Why Services Now Match Products on GeM

For years a certain kind of GovTech founder treated GeM as a hardware mall: chairs, laptops, printers, the occasional boxed licence. Services were what we do on a work order after the cart. That habit is now expensive. Rule 149's language takes goods and services together. The portal has service catalogues, service SLAs, manpower and outcome-shaped listings, and bid tools that buyers actually use for implementation and managed work. If your only listing is a goods SKU, you are invisible to a large class of lawful carts.

You will hear precise-sounding shares in conferences — a percentage of GMV that is services, a multiple by which forward auctions grew in a fiscal year. Unless you are reading that number off a current official GeM or MeitY publication, do not put it in a board note. This article will not invent 49% or any other share. If you need a figure, open the live dashboard on gem.gov.in the morning you write, screenshot it, and cite the screenshot's date.

What you can say without a dashboard is structural. Services are in the Rule. Services are in the portal. AI platforms are often services in substance even when the invoice says licence. Founders who ignore that will keep losing to SIs who listed implementation of AI while the product company listed a PDF.

What changed is the object, not a percentage we made up

Early marketplace politics was about common-use goods and rate discovery. That problem did not vanish. A second problem grew: departments were buying people, AMC, cloud, training and outcome SLAs on email because the mall did not feel like the right aisle. GeM's service machinery is the response. Whether services are a third or a half of GMV this quarter is a dashboard fact. That they are a first-class aisle is a product fact.

For AI, the substance is rarely a shrink-wrapped good. You are selling a right to run software, a duty to keep it patched on media, a set of people who will sit through an isolation drill, and sometimes a managed desk. Those are services, or a mix. Buyers who still force everything into a goods code are not being conservative. They are misdescribing the acceptance. Sellers who only know goods listing flows will under-describe SLAs, over-promise uptime they cannot measure on an air-gapped box, and then lose custom bids to firms that spoke service language.

Structure first. Statistics only with a URL and a date.

Old habit	Why it breaks for agents	Service-shaped alternative (confirm live)
One goods SKU, perpetual licence	No place for isolation drill, hypercare, language eval	Licence listing plus an implementation / support service listing
AMC as a footnote	Air-gap support is the product after month two	A service SLA that assumes media and tickets, not tunnels
Manpower supply disguised as platform	You become a body shop by accident	If you sell people, list people; if you sell a platform, do not hide FTEs
Ignore GeM services, wait for CPPP SI RFP	Rule 149 may already want the service on GeM	Be findable in the service search the PMU will run
Quote GMV shares in the pitch	Stale or invented numbers become board folklore	Cite a dated official dashboard or cite nothing

How to read a dashboard without lying

If GeM publishes a public dashboard or an annual report, use that primary. Note whether the share is GMV, order count, or seller count. Services can look larger in GMV (long-running contracts) and smaller in order count, or the reverse. Do not compare a GMV share to an order-count share from a tweet. Forward auctions, reverse auctions and service bids are different tools. A press line that auctions doubled is meaningless unless you know which auction and which year. This article's only statistical rule is: no primary, no number. Internal investor decks should follow the same rule. A Series A slide that says GeM services are 49% of GMV without a footnote will be in a journalist's inbox the week you least want it.

What founders should build this quarter

A service listing that matches how a department will actually accept your on-prem work: install, isolation drill, training, annual support on media. Price bands you can invoice. A goods or licence listing only if you truly sell a versioned artefact. Do not delete it. Do not let it be the only door. A one-page explanation for buyers of why they may need both lines in one architecture note. You are teaching Rule 149 hygiene, not upselling. Sales training that stops saying GeM is for products. That sentence makes you sound like 2018 and steers buyers toward the wrong aisle.

• Open gem.gov.in dashboard on the day you need a share; do not memorise one.
• List the service you can fulfil without a standing tunnel.
• Keep licence and service SKUs from contradicting each other.
• Never invent a GMV percentage in a public blog or a bid.
• Read service SLA templates before you copy a SaaS uptime clause.

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.

I need a number for the board.

Then assign someone to screenshot the official dashboard or the latest official report and put the date in the footnote. A round number with no source is not a KPI. It is a liability.

Our lawyers say we only sell software goods.

Lawyers can classify invoices. Buyers classify acceptance. If you send people and a drill, you are in the service conversation whether the invoice says licence or not. Align the two.

Services on GeM are just manpower.

Manpower is one template family. Outcome, AMC, cloud and professional services exist. Read the live catalogue rather than the rumour.

A ten-day services hygiene pass

1. Day 1: screenshot any official mix you intend to cite; otherwise delete unofficial shares from decks.
2. Days 2–4: write the service fulfilment note for on-prem install + support.
3. Days 5–7: draft or fix the service listing; check SLA templates for air-gap sanity.
4. Days 8–10: brief sales that GeM is goods and services; pick one friendly buyer to try the search.

How this shows up in the file

Keep the dated dashboard screenshot if you cite a share. Keep the service fulfilment note next to the goods listing. A later dispute will ask what support meant. If this article is reprinted in a year, replace every temptation to add a percentage with a new screenshot. That is the point of a data study that refuses fake data.

How to cite GeM without becoming a statistician

Permitted: As of [date], the GeM public dashboard / [named official report] showed [metric] of [value]. Screenshot in the file. Forbidden: Services are now half the marketplace, as everyone knows. Forbidden: Forward auctions doubled in FY26 without a primary. This discipline is not pedantry. Joint secretaries have staff. Staff have browsers. If GeM publishes no share that day, say we do not have a primary share; we are listing services because the Rule and the templates do. That sentence is adult.

Teaching sales the two aisles

Role-play a purchase officer who searches AMC on-premises software and never types your brand. If your service listing does not appear, your goods listing will not save you. Role-play a store officer who only searches goods. You need both doors. One afternoon of role-play prevents a quarter of wrong-aisle pitching.

What a service SLA looks like when the WAN is dead

Write response clocks that start when a ticket hits a number or an email you monitor, not when a SaaS agent pings. Write restore clocks that assume media. Write a clause that standing tunnels are not a remedy you may force. Buyers who care about isolation will recognise the sentence. Do not copy 99.9% from a public cloud page. You do not measure that on a collectorate blade, and you should not pretend to.

What the next noting must contain

“Why Services Now Match Products on GeM” belongs in a file, not only in a search result. A P5 GovTech Founder should be able to point at one artefact that proves “GeM services procurement”: 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.

Treat services as first-class on GeM because the portal and the Rule do — not because a slide said they are 49% of GMV. If you need a share, open the live dashboard. 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 C3 GeM & Procurement: 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 “GeM services procurement”, 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, not legal or procurement advice. GeM screens, fees, preference rules and dashboards change. Confirm on gem.gov.in, doe.gov.in and current FAQs before you act. Do not treat any figure here as a live statistic.