This is a single worked example, start to finish. The company is Kaveri Retail, a chain with about 900 employees. The vendor is a workforce-scheduling software firm. The deal is a three-year subscription at ₹14 lakh a year, so ₹42 lakh in total. The operations head, Meera, has told the vendor’s account executive, Rohan: “We want to go with you. Send the paperwork.” Everyone treats this as a closed deal. It is not. It is the start of a different process, which runs through people Rohan has never spoken to.
Day 1: the request becomes a purchase requisition
Meera raises an internal requisition. In most mid-sized and large Indian companies this goes into an approval workflow in the finance or procurement system. Her budget owner approves, then her department head, then finance confirms a budget line exists. Rohan cannot see any of this, which is why he thinks nothing is happening. Something is, but it is waiting in somebody’s queue.
Rohan can ask Meera one useful question here: “Who else needs to approve, and what do they usually ask for?” Her answer defines the rest of the timeline.
Days 3 to 10: vendor onboarding
Kaveri has never bought from this vendor, so procurement sends a vendor registration form. It asks for the company’s PAN, GST registration, bank details on a cancelled cheque, a certificate of incorporation, MSME status if applicable, and sometimes financial statements for the last two or three years and a list of references. A vendor that has these ready returns the form in a day. One that has to chase its finance team for audited accounts loses a week.
Procurement may also run a basic check of the vendor’s standing and, for a deal of this size, ask for two or three competing quotes if company policy demands it. If Rohan was not told about that, a rival quote can appear now, unannounced. That is a good reason to understand the buyer’s policy before the verbal yes.
Days 5 to 20: security and IT review, in parallel
Because the software will hold employee data, Kaveri’s IT security team sends a questionnaire and may request a summary of certifications such as ISO 27001 or a SOC 2 report, and a description of where data is hosted. Some of this can run at the same time as the vendor onboarding, and sensible vendors start it as early as possible. Anything that arrives late here pauses legal, because legal often wants the security answers before accepting data-protection terms.
Days 10 to 30: legal redlines
Whose paper do we sign on? Rohan’s company sends its standard subscription agreement. Kaveri’s legal counsel returns it with changes marked, the redlines. For a deal like this, the commonly contested points are fairly predictable:
- Limitation of liability: the vendor wants liability capped at fees paid in the last twelve months; the buyer wants a higher cap, or no cap for data breaches and confidentiality.
- Indemnity for third-party intellectual property claims.
- Data protection: who is responsible for what, breach notification periods, deletion at the end, and compliance with India’s Digital Personal Data Protection Act, 2023 as its rules come into force.
- Termination rights, auto-renewal and price increase limits on renewal.
- Payment terms. The vendor asks for payment within 30 days; large buyers often push for 60 or 90.
- Governing law and jurisdiction, and whether disputes go to arbitration.
Each of these needs an answer from someone on Rohan’s side with authority: legal on liability and indemnity, finance on payment terms, the security lead on data terms. If every redline goes by email to the legal team who reply in four days, three rounds of exchange will use up the month. Rohan’s job in this phase is to be the project manager: keep a list of open points, name an owner for each, and get the two legal teams on one call. A single forty-minute call can settle what email takes two weeks to settle.
Days 28 to 38: internal approvals and signature
Once terms are agreed, the contract is checked against the delegation of authority: who at Kaveri is permitted to sign a ₹42 lakh commitment? Perhaps a vice-president can sign up to ₹25 lakh and the CFO above that. The CFO is travelling for a week. Meanwhile, on Rohan’s side, the discount and any nonstandard terms agreed in negotiation need his own finance and legal approval, and if they are not already in hand, the contract waits for his own company too.
On day 40, the contract is signed. Purchase order, if separate, follows; invoice cannot be raised until the PO exists. Rohan’s forecast had said “closing this month” at the verbal yes. It closed in just over five weeks, which was normal.
What the walk-through shows
The real timeline was driven by waiting, not by negotiation. Most of the forty days were spent in queues: a form, a questionnaire, a review, a signatory’s diary. Rohan could shorten several of them without conceding a rupee, by sending vendor documents on day one, starting the security pack before being asked, bringing legal teams together and checking signing authority early.
It also shows why asking for a mutual timeline at the verbal yes is not nagging; it is the only moment the buyer is warm enough to describe their own process. Timelines vary a lot: a startup may sign in a week on your paper, while a bank or government body can take several months, with extra committee approvals and tenders.
Figures and names in the examples are illustrative.
Leave a Reply