Picture a software company in Coimbatore, call it Vellore Digital Works for the sake of the story, that has built a good grievance-tracking tool. A state transport corporation publishes a tender for exactly this. The team is delighted. They write a thoughtful proposal, price it fairly at ₹48 lakh, and submit. Three weeks later they learn they were disqualified at the technical stage because a required certificate was uploaded in the wrong format. The bidder who won, at a lower price, had a product that was weaker. What went wrong?

Nothing unusual. That is how public procurement works, and it is worth understanding why before you chase a government customer.

Why the process looks the way it does

A government officer spends public money and must be able to defend every decision later to an auditor, a vigilance officer or a court. Personal judgement is a risk for that officer. A rule is a shield. So the system is designed to remove discretion: published criteria, sealed or online bids, a technical evaluation followed by a commercial one, and a clear winner defined by arithmetic. The officer is not being difficult; the structure protects them.

Much central and state buying now happens on the Government e-Marketplace, GeM, an online portal launched in 2016. Larger or customised requirements may still run as separate tenders on a department’s own portal or the central public procurement portal. Rules differ by organisation, and by whether the buyer is a ministry, a state government, a PSU or a bank; read the tender document itself rather than relying on what a colleague remembers from last time.

L1 and what it really means

You will hear “L1” constantly. It means the lowest-priced bidder, among those who passed the technical stage. L2 is the next lowest. In pure price-based buying, the contract goes to L1. Some tenders use quality-and-cost-based selection, where a technical score is combined with price in a stated ratio, mostly for consulting and complex services. Check which method applies, because your strategy differs completely.

Two consequences follow. First, price is not negotiable in the way a private-sector customer would negotiate; discussions after bids open are limited by rule, and the sealed price is what counts. Second, your entire effort goes into two places: getting through the technical gate, and pricing properly without knowing the competition. Underpricing to be L1 and then discovering you cannot deliver profitably is a well-known way to lose money on public contracts.

Where the sale is actually won

Not at bid submission. Before a tender is published, many departments hold consultations, issue requests for information or publish draft requirements for comment. Participating in these, openly and in writing, is legitimate and is how a vendor can point out that a specification is unrealistic or accidentally excludes a whole class of solutions. What you must not do is lobby privately for terms written around your own product. That risks disqualification at best and criminal exposure under the Prevention of Corruption Act at worst.

Then comes eligibility, which is where Vellore Digital Works was lost. Typical conditions include a minimum annual turnover, experience in similar projects with completion certificates, registrations such as GST and PAN, sometimes specific certifications, and a bid security or earnest money deposit. Exemptions exist for some categories of bidder, such as registered MSMEs and startups, under government policy, but the details depend on the buyer and the tender. Build a standing bid library: audited financials, certificates, past-order proofs in the formats the portals expect. Then a deadline is a matter of assembling, not scrambling.

Preference for locally manufactured or developed products is another feature. Government orders on local content, commonly called Make in India preferences, can favour bidders with a stated percentage of local value addition, and the thresholds vary by product category. If you resell a foreign product, ask what that does to your eligibility before spending weeks on a response.

After the award, the real work starts

A won order often brings a performance guarantee, usually a modest percentage of contract value held through the delivery period, milestone-based payments, acceptance testing by a committee, and sometimes liquidated damages for delay. Payment cycles can be long. Build that working-capital cost into the price, because a ₹48 lakh order that pays after ninety days to a company with thin cash is not the same ₹48 lakh.

Changes are slow too. A new requirement mid-project may need a formal amendment, approvals up the chain, and a revised order. A services team used to a friendly email saying “go ahead” will find that unsafe here. Insist on written change orders, always.

Is it worth it?

Sometimes yes. Government accounts are big, stable once won, and a reference from a respected department carries weight with other buyers. But the sales cycle can run many months, win rates on open tenders can be low, and margins are squeezed by L1 dynamics. A company that treats it as a side channel, with one tired person handling it, usually loses. One that builds a small dedicated bid team, a document library and a habit of qualifying tenders hard, saying no to the ones that are wired for someone else, tends to do well.

That last point matters most. Read the technical specification before anything else. If it names a proprietary feature that only one vendor has, the outcome may already be decided, and your time is better spent elsewhere.

Figures and names in the examples are illustrative.

Leave a Reply

Trending