Notes for owners · Industry playbooks
Why RPA pilots stall after the proof of concept
An automation pilot works and still goes nowhere. Why a proof of concept does not become an order, and what the vendor can fix before it starts.
The GullySales team · Updated 13 Nov 2026 · 5 min read

On this page
- The pilot answered the wrong question
- Nobody on the buyer's side owns it
- The proof of concept has no ending
- Support is written as an afterthought
- A pilot summary that gets signed
- The second process never comes
- Who should be in the room for the proof of concept?
- What should the pilot do with the exceptions?
- How do you show the result without overselling it?
- What goes wrong when IT is brought in late?
- How do you keep the sponsor interested between pilot and decision?
- What should a vendor keep after a pilot that does not convert?
- What to do next
Most pilots stall because nobody on the buyer's side owns what happens next. The proof of concept ran, the clerks saw a bot key in an invoice, and then the finance controller went back to the month-end close. There was no decision to make, no named person to make it, and no support terms to sign. A pilot that ends without a dated next step has already ended.
The pilot answered the wrong question
A vendor treats the proof of concept as a test of the technology. The buyer treats it as a test of the vendor. Whether the bot can read an invoice is not what worries the controller. What worries the controller is the March close, when the bank changes its login page and nobody is there to mend it.
So a pilot that proves the bot works, on a clean set of invoices chosen by the vendor, has shown the one thing the buyer did not doubt. Run the pilot on the buyer's own messy files, including the ones with a scanned stamp over the total, and show what the bot does when it cannot read one. A bot that stops and raises a flag looks more trustworthy than one that has never failed in the demo.
Nobody on the buyer's side owns it
In some companies the pilot is set up by the finance head and the IT head approves access, and neither of them is the person whose morning gets easier. The clerks who key the data feel threatened, not helped, and nobody has told them otherwise.
Ask for a named owner before you start, and write the name in the scope. Ask the clerk too. For example, an automation firm in Pune automating bank statement entry for a distributor in the same city would sit with the two clerks first, and ask which part of the morning they dislike most. The pilot then removes that part, and the clerks become the people who ask for the next one.
The proof of concept has no ending
A pilot that is described as "a few weeks of testing" has no finish line. Write the finish line down in the first meeting: the process, the volume of items to be handled, the measure of success, who judges it, and what the buyer does if it passes. The next-step line is the important one. It reads something like "if the pilot meets the agreed measure, we move to a scoped production phase and sign the support terms in the same meeting".
The time it takes depends on the buyer, so do not promise a number of days. Agree a decision date with them and write it into the plan.
Support is written as an afterthought
The buyer's biggest worry is a bot that breaks with nobody answering. If the pilot proposal says nothing about support, the buyer fills the gap with the worst case.
Put support terms next to the pilot terms. Cover who monitors the bots, how a failure reaches you, what the buyer's team does while it is fixed, and whose name the platform licence is in. That last point matters more than vendors admit, because a buyer who finds the licence is in your name starts wondering what happens if you leave.
A pilot summary that gets signed
| Item | What to write |
|---|---|
| The process | One process, in the buyer's own words |
| The systems it touches | Named, with who gives access |
| The buyer's owner | A person, with a role |
| The measure of success | One measure, agreed before the pilot |
| The decision | Who decides, and the date |
| If it passes | Production scope and support terms, signed together |
| If it fails | What the buyer keeps, such as the process map |
A one-page summary like this goes to the controller and the IT head together, so that information security is brought in at the start and not at the end. Credentials and logs are where pilots stall, so answer them on page one. The sales process page for automation firms covers the steps from discovery call to signed order.
The second process never comes
Even a pilot that goes live can end there. The vendor leaves and the buyer feels the work is done. But the clerks, the controller and the IT head have all just learned that automation works in their own company, and that is the moment to ask what they dislike next.
Keep a list of the processes you heard about during the pilot, and bring it back at the first review. Name the next process, not "more automation". Use the pilot as a described case for the next buyer too, with the client's permission. The buyer journey page shows where the second sale starts and the CRM page shows how to record who said what.
Who should be in the room for the proof of concept?
Invite four people to the kick-off, and write their names in the pilot summary. The person whose morning the bot will change is the first, because they know where the process really breaks. The controller or manager who judges success is the second. The IT head who grants access is the third. The fourth is someone from information security, if the buyer has one, so that credentials and logs are discussed before the bot touches a live system.
If one of the four is missing, the pilot will stall on that person's desk later. Their first question will be one you could have answered in the kick-off.
What should the pilot do with the exceptions?
Every process has items that do not fit: the invoice with a handwritten correction, the statement in a new format, the vendor who uses another name. Do not hide these from the buyer. Collect them during the pilot, count them in the buyer's presence and show what the bot did with each one.
Then agree who handles an exception in production. The usual answer is that the bot sets it aside in a list and a named clerk clears the list. When the buyer sees the list and the clerk's name, the fear of a silent failure goes away, because the failure is no longer silent.
How do you show the result without overselling it?
Show the buyer's own files going in and the finished entries coming out, on the buyer's screen. Do not show a slide of savings you have not measured on their process. The measure was agreed at the start, so report against that measure and no other.
If the pilot met the measure, say so and move straight to the production scope. If it fell short, say by how much and why, and what you would change. A buyer who has seen an honest shortfall trusts the next result. A buyer who was shown only the good days waits for the bad one.
What goes wrong when IT is brought in late?
The pilot runs on a test login that someone lent. When production is proposed, the IT head asks where the bot will run, which account it will use, how its password is stored and who can see its logs. None of these has an answer yet, and the project loses time for reasons that have nothing to do with the bot.
Put those four questions in the pilot summary and answer them in draft. Ask the IT head to mark what they would change. Their edits are not obstruction. They tell you what they will insist on later, and it costs less to hear it now.
How do you keep the sponsor interested between pilot and decision?
The gap between the pilot ending and the decision date is where interest drains away. Send the sponsor a short note after the pilot with three things: what was tested, what the result was against the agreed measure, and the date and the person for the decision. Do not send a long deck.
If the decision date passes in silence, call the named owner and ask what is in the way. The answer is a person, a budget cycle or a worry about support. Each can be answered if you hear it, and none can be answered if you wait.
What should a vendor keep after a pilot that does not convert?
Keep the process map, the list of exceptions and the buyer's own words about what they disliked most. With the buyer's agreement, record why the pilot stopped. Was it budget, an owner who moved, a system change or a doubt about support? Over a few pilots the pattern shows where your sales process is weak.
Return to the buyer when the reason has changed. A budget that opens in the next cycle or a new controller is a fresh start, and the pilot you already ran shortens the conversation.
What to do next
Pull out your last three pilots and write one line for each: who owned it on the buyer's side, what the finish line was and what was signed at the end. If any of the three has a blank, you have found where the next pilot will stall.
If you want help with how enquiries reach you and what happens after the first meeting, tell us what you need and we will read it before we call. For the trade as a whole, start at the business automation and RPA companies page.
Put the reading to work
Try this with your own records.
Bring real questions, objections, and call examples that the team finds difficult. Agree which selling behaviour needs to change and how it will be observed at work.
How to review the result
Use a realistic practice conversation, then review the same skill in live work with appropriate permission. Look for a change in behaviour before attributing a sales result to training.








