Indian enterprise procurement has four stages. Stage two is where most SaaS deals die.

The pilot is live. The business unit lead is enthusiastic. The product is working, the data is good, and your champion at the 2,000-person company has been telling you the deal is close for six weeks.

Then it stalls.

Not because the product broke. Not because a competitor appeared. The pilot enters a holding pattern with no clear timeline, while internal meetings happen that you are not part of, involving people you have never met.

This is stage two of Indian enterprise procurement. It is the stage founders spend the least time preparing for, and the one that quietly kills the most deals.

The four stages of Indian enterprise procurement

Most SaaS founders who sell to Indian enterprise treat procurement as a single event: the customer decides yes or no. The reality is a structured four-stage process, each with its own gatekeepers, timelines, and ways to stall.

Stage one is POC initiation, where most sales conversations start. The business unit has a problem, you have a solution, and a pilot gets approved. This stage feels like momentum because it is, but with a specific scope: you now have permission to demonstrate value, not permission to become a vendor.

The remaining stages are the ones most founders never plan for. Understanding them does not make procurement faster, but it does change the number of deals that actually close.

Stage two: the champion authority problem

When a B2B SaaS company signs its first SMB customers, the champion and the decision-maker are usually the same person. When the same company pursues its first enterprise deal, the champion is almost never the decision-maker.

This creates a specific failure mode. The champion (the HR director who wants your platform, the legal team lead who ran the pilot) is genuinely enthusiastic. They give you updates. They introduce you to colleagues. They describe themselves as your "internal sponsor." But they cannot write the purchase order. They cannot convene the committee. They often cannot schedule the meeting with the CFO's office.

Stage two is where the champion must convert their personal enthusiasm into organisational will. They need to brief their own manager, address the IT infrastructure team's concerns, and produce a business case that can survive a procurement committee. Most pilots that fail, fail here.

What to do: before the pilot ends, ask your champion directly: who else needs to say yes before this becomes a contract? Write down every name they give you. If the list is empty, that is a warning sign, not a green light.

The founders who close deals fastest also help their champions build the internal case. That means a one-page business case document (not a pitch deck), a clear statement of the problem before the pilot, and quantified outcomes from it. Most champions want to advocate for your product; they do not always know how to present it to a committee.

Stage three: the VAPT requirement that surfaces at the wrong time

Vulnerability Assessment and Penetration Testing (VAPT) is now standard vendor onboarding practice at most Indian enterprises above approximately 500 employees. It is the InfoSec team's mechanism for ensuring that a new SaaS vendor cannot be used as an attack surface.

The problem is not that VAPT exists. The problem is when founders learn about it. In most cases, a founder does not hear about the VAPT requirement until after the pilot has succeeded and the commercial conversation has started. At that point, a review process that takes three to six months appears on the timeline, and the urgency the champion had at the end of a successful pilot has already dissipated.

Post-DPDP, this has become more consistent across industries. Enterprises handling customer data as data fiduciaries are now more careful about the security posture of their data processors. For SaaS vendors, that translates into longer and more detailed InfoSec reviews.

The straightforward approach: in week two of any enterprise pilot, ask the business unit champion to introduce you to the IT security contact. Not to pass VAPT, but to understand their process and what documentation they will need. This conversation surfaces requirements early and signals to the enterprise that security is not an afterthought.

If you have SOC 2 Type II or ISO 27001 certification, share it proactively at the start of the pilot. Many enterprise InfoSec teams will accept a current certification in lieu of a separate VAPT, shortening this stage by months.

Stage four: budget cycles and committee sign-off

Indian enterprises typically operate on an April-to-March financial year. Budget is allocated in Q1 (April to June). New vendor approvals during Q1 are harder to push through unless the budget was specifically allocated for the category in the prior year.

The highest conversion window for new SaaS vendor contracts at Indian enterprises tends to be Q3 (October to December), when budget has been allocated, the year's trajectory is clear, and teams are motivated to deploy approved spend before year-end reviews.

If your champion is pushing to close in June, the honest conversation is: the deal is real, but the timing is working against it. Aim for October. Can the pilot structure still be top of mind in September?

The committee composition at large Indian enterprises is often more opaque than founders expect. A buying committee for a SaaS product typically includes the business champion and their manager; an IT or infrastructure representative; a procurement or vendor management lead; legal, for contract review; and finance, for budget sign-off.

Not all of these people will have seen your product. The procurement lead's job is vendor evaluation, not product evaluation. They are often comparing you against an RFP scoring rubric that may have little overlap with what your champion found compelling about the pilot. Preparing a standard vendor questionnaire response before it is requested saves two to four weeks in this stage.

Treating procurement as something to navigate, not endure

The founders who close enterprise deals faster do not move faster through procurement. They navigate it rather than waiting for it.

Three shifts that change the outcome:

• Map the full approval chain before the pilot starts. Ask your champion to sketch the approval path for a software purchase above a certain threshold. This conversation tells you whether your champion has the organisational context to guide you, or whether they are guessing about a process they have not been through themselves.
• Introduce your security documentation before it is requested. Share your SOC 2 report, VAPT summary, or security posture overview on day one of the pilot. Enterprise InfoSec teams appreciate not being treated as an obstacle at the end of a deal.
• Get your champion to own the internal timeline. The deals that close fastest have champions who treat the internal process as a project, not a formality. They know what the next internal milestone is, who is responsible for it, and what would cause it to slip. If your champion does not have this clarity, your deal is running on optimism.

One thing that rarely changes the outcome: pressure. Indian enterprise buyers know their procurement process is slow. They also know that every SaaS vendor believes their use case is urgent. Artificial urgency creates resistance, not acceleration.

What this timeline implies for pipeline planning

An enterprise deal from first conversation to signed contract typically takes six to eighteen months in India. This is not a product problem or a sales execution problem. It is the cost structure of selling into large organisations with structured procurement processes.

The practical implication: enterprise deals that close are often started during a period when the founder was not primarily focused on enterprise. The pipeline that converts in Q3 was planted in Q4 of the previous year. The timelines are long enough that the only rational enterprise sales motion is parallel: working multiple accounts across different stages simultaneously, rather than sequential, where you wait for one deal to close before focusing on the next.

Start earlier than feels necessary. Keep pilots alive even when the timeline slips. And treat every procurement contact as a relationship, not a checkpoint to pass and move on from.