How to build a referral partner program that partners use
Revenue share alone rarely motivates. What referral partners actually want, the disclosure rules you are responsible for, and why three beats thirty.
Read
The deal did not go to a rival. It went nowhere, which is a different problem and needs a different fix.
Ask a sales team why a deal stalled and you will usually get a competitor's name, a price objection, or a shrug. Ask the buyer and you get something duller and more useful: it stopped being anybody's priority, or it hit a step nobody had accounted for.
That gap matters because the two explanations lead to opposite responses. If you lost to a competitor, you work on positioning. If the deal simply stopped moving, positioning is irrelevant and you have a process problem.
Pipeline reviews are built around comparison. Which rival, which feature, which price. That framing quietly assumes the buyer made a decision, and in a stalled deal they did not. Nothing was chosen. The status quo continued because continuing required no meeting, no budget request and no risk.
So the first correction is to stop recording these as competitive losses. A deal that ends in no decision is a different category with different causes, and merging the two hides the pattern you most need to see.
The most common cause, and the easiest to miss because the conversations are pleasant. The buyer agrees there is a problem, likes the solution, and is under no pressure. Agreement is not urgency, and a deal built entirely on agreement will sit indefinitely.
The diagnostic is blunt and you can ask it out loud: what happens in six months if this stays as it is? If the honest answer is nothing much, you do not have a stalled deal, you have a conversation that was never a deal.
Enthusiasm from someone without signing authority is the most flattering signal in B2B and the most misleading. They are not lying to you. They genuinely want it, and they genuinely cannot approve it, and they may be reluctant to say so because it costs them standing.
The fix is unglamorous and works: early, and without apology, ask what the approval path looks like and who else has to say yes. Teams avoid this because it feels like doubting the person in front of them. It is the opposite. It is taking their internal position seriously.
This is where Gulf deals stall most predictably, and it is almost never in the sales plan. The commercial conversation finishes, everyone agrees, and then the deal enters a compliance process with its own timeline and its own vocabulary.
Invoicing is the clearest example. Saudi Arabia's tax authority requires electronic invoicing, described in its own documentation as a procedure that converts the issuing of paper invoices and notes into an electronic process allowing the exchange and processing of invoices, credit notes and debit notes in a structured electronic format. It rolled out in two phases, the first from December 2021 and the second from January 2023, with defined data and security standards a supplier's system has to meet.
None of that is exotic if you have handled it before. If you have not, it arrives as a surprise after the buyer has already said yes, and the deal sits while somebody works out whether your invoicing can satisfy their finance team. That is a solvable problem, and it is very hard to solve in week eleven of a quarter.
Silence gets interpreted as a soft no, so the response is to back off and follow up gently. Frequently the truth is that your champion is stuck internally and has nothing to report, and your polite follow-ups give them nothing to work with.
What helps is arming them rather than chasing them. The internal case they have to make is not the case you made to them, because their audience is finance, or legal, or an operations lead who was never in the room. A one page version they can forward without editing does more than four check-in emails.
Nothing is wrong with the deal. The money simply is not available until the next period, and nobody told you because nobody thought to. This one is genuinely not a failure, but it is often recorded as one, and the deal gets discounted to rescue a quarter it was never going to land in.
The cost of discounting a deal that would have closed anyway is permanent, because the next renewal starts from the lower number. Knowing the budget calendar early is worth more than the discount you would otherwise offer.
A loss has a reason you can name and a date it happened. A stall has neither, which is why stalls accumulate in a pipeline and losses do not. If your forecast is regularly wrong in the same direction, the stalled deals are the reason, and they are sitting in your pipeline with dates that have been pushed more than once.
Two pushed dates is the signal we act on. Not a rule with anything scientific behind it, just a threshold that forces a decision rather than another polite extension. The point is to have any threshold at all, since without one the deal is never closed out and never worked. This is the same discipline that makes a pipeline you can actually forecast possible: the pipeline is only honest if things are allowed to leave it.
Some of this is not fixable by the seller. If a buyer's organisation cannot make decisions, no sequence of well-run meetings will change that, and continuing to work the deal is a cost with no return. The skill is not rescuing every stall, it is recognising early which ones cannot be rescued and moving the effort.
That is also the honest answer to whether better technique would have saved a particular deal. Sometimes yes. Often the deal was never available and the only mistake was how long it stayed in the forecast.
Three changes, none of which require new tooling:
If most of your deals stall in the same place, that is a system telling you something rather than a run of bad luck, which is the argument in business development as a system problem rather than an effort problem. Adding activity on top of a process that stalls at step four produces more stalled deals, faster.
One thing worth borrowing from how software gets bought: much of what looks like buyer hesitation is unclear scope, and the cure is defining the first deliverable narrowly enough to approve. Rivl make that case for technical projects in scoping a project before anyone writes code, and it transfers directly to services. A smaller first commitment is easier to say yes to, and a yes is what ends a stall.
Whether you fix this with your own team or bring in help is a separate question, and we have set out the trade-offs in outsourced BD versus hiring a salesperson. Either way the diagnosis comes first, because both options fail against a pipeline nobody has cleaned.
We review a live pipeline and tell you which deals are stalled, which are lost, and which stage is doing the damage. No tooling change required to start.
Book a Free Consultation