Picture a vendor, call it Nimbus Route, and a prospect, a regional logistics company in Coimbatore. The prospect’s operations head says: “Looks interesting. Run a pilot on our data for a month and we will decide.” The vendor’s sales team is delighted. A pilot is a buying signal, surely.
Four weeks later the pilot has gone well, by the vendor’s reading. Routes are shorter. The dashboard looks good. The operations head says it is impressive and that he will discuss it internally. Then: nothing for two months. Then a message that the finance team wants to “revisit priorities next year”.
Nothing went wrong technically. What went wrong was that the pilot was never connected to a purchase decision. Let us go back to day zero and see what should have been settled before a single file was loaded.
A pilot is a test of a claim, so write the claim down
The first question the vendor should have asked: “What would you need to see in thirty days to sign?” Ask for it as a measurable statement. Suppose the answer is that daily route planning currently takes a planner about six hours, and the buyer wants it to fall by at least 30%. Six hours times 0.7 is 4.2 hours. Now there is a line. At or below 4.2 hours, the pilot passed. Above it, it did not, and nobody can argue afterwards that “it felt faster”.
Get those criteria in writing, in an email at minimum, signed off by the person who will make the buying decision, not just the person running the pilot. The user who runs the pilot is usually not the one who approves the budget.
Settle the commercial path before the technical one
Back to Coimbatore. Before starting, the vendor and buyer could have agreed three things in one short document:
- The success criteria above, and who judges them.
- The price and rough terms of the full deployment if the criteria are met, so success means “we proceed at this price” and not “we start negotiating”.
- The process after a pass: who raises the purchase requisition, what approvals exist, how long procurement takes at this company.
The third item is the one most often skipped. Procurement in mid-sized Indian companies can take weeks, and in larger ones, months, with vendor registration, security review and legal redlines. If you learn this after the pilot, the buyer’s enthusiasm has cooled by the time paperwork starts. Run those processes in parallel with the pilot, not after it.
Free, paid or nominal?
A fully free pilot is easy to say yes to and just as easy to ignore. The buyer has nothing at stake. A paid pilot, even for a modest sum that is credited against the first-year contract, filters for seriousness and often gets a budget owner involved, because someone has to approve the spend. Its cost is that it slows the start, since the paid pilot itself needs a purchase order. Opinions among sales leaders differ; a reasonable middle is free for small, short evaluations of standard products, paid or cost-recovered when the vendor must do real configuration or integration work for the buyer.
Bound it, in time and in scope
A pilot with no end date turns into unpaid production use. Fix the start, the end and a mid-point review. Fix the data and the sites in scope: for example one depot and two routes, not the whole network. Name the people on each side with the hours they will give. If the buyer’s planner cannot spare two hours a week to give feedback, that is the information you needed about how real this is.
Write down the exit rule as well: at the end, either the criteria are met and both sides proceed, or they are not met and the pilot closes, with a short note of what was learned. A pilot that fails against clear criteria is not a disaster. It saves both sides a year.
What to do while it runs
Send the buyer’s decision-maker a short weekly note: what was measured, how it compares with the agreed line, what is blocked. Do not wait until week four to show results to the person who signs. At the mid-point, ask directly whether anything would stop them proceeding if the numbers hold. This is where hidden objections surface: a competing internal project, a security concern, a budget freeze.
On the last day, hold a review meeting with the decision-maker present, put the result next to the agreed criteria, and move straight to the next step in the plan: the commercial proposal at the price already discussed. Leave nothing to “internal discussion” that has no date.
Not every pilot should be taken at all. If the buyer will not name success criteria, will not introduce the budget holder and will not say how a purchase would be approved, the polite name for what is being requested is free consulting. A vendor may still choose to do it, for learning or a relationship, but should call it that and not forecast it as a deal.
Figures and names in the examples are illustrative.
Leave a Reply