2026-09-26
The shortlist is decided at the integrator
A B2B software company can have the best product, solid references and a strong team, and still never make the shortlist. Between the need and the choice sits a third party managing its own risk. Here is what your lost deals from the last twelve months say about that third party.
The silence after the demo
The demo went well. The IT director asked three precise questions, which is usually a good sign. Your references in their sector hold up.
Six weeks later, the shortlist has three names on it. Yours is not one of them.
You ask why. You are told the product is interesting, but the timeline calls for something the team already knows how to run. Nobody lied to you.
Sometimes the version is sharper. The requirements document was written by an outside consultancy and describes an architecture you cannot reproduce exactly. The outcome was set before you arrived.
The reflex: price and awareness
The first explanation usually comes in two branches. Price: too expensive. Awareness: they do not know us well enough, we need a trade show, more content, an analyst.
Both are sometimes right. Both have the advantage of being fixable fast. A discount can be decided in one meeting.
What they explain less well: why the same deals are lost at clients of different sizes and in different sectors, with contacts who seemed won over. And why, on the few large accounts you did win, someone from outside the client was in the room from the start.
Whoever recommends is managing their own risk
Between the need and the choice there is often an integrator, a systems firm or a consultancy. They do not recommend the best-rated technology. They recommend the one they know how to sell, deploy and defend when a project goes sideways.
The vendors who build partner programmes write this down plainly. One dominant cloud platform scores its partners on performance, certified skills and customer success [3]. A major infrastructure provider asks for technical expertise and demonstrated wins [4]. SAP talks about repeatable quality, fewer escalations, and protecting partner margin [5]. The intrinsic quality of the product appears nowhere on those lists.
The rest is arithmetic. At one leading CRM vendor, 72% of deployments go through a partner [1], and the ecosystem is aiming at close to seven dollars of services for every dollar of licence [2]. One large consultancy claims more than a thousand deployments and twenty-five hundred certifications on a single stack [7]. Another has industrialised preconfigured accelerators [6]. And SAP has acknowledged that large custom deployments could run to five times the licence value in consulting.
A working scenario, to be replaced with your own numbers: a licence at 300,000 euros, services at three times that, so 900,000 euros for the integrator. Proposing you costs them two consultants to train, no reusable template, and an escalation path with no phone number attached. The competitor brings them the same revenue with none of that risk.
They are not ruling you out. They are not seeing you.
What your lost deals say
Checking this needs no tool. It sits in what you already have: meeting notes, quotes, and email threads from the last twelve months on large-account deals.
What you are looking for is not the stated reason for the loss, which is always polite. It is the presence of a third party: who brought them in, at what point they appear, whether they had already deployed the technology that won, and whether anyone on your side knew their name before the first meeting.
Across ten or so deals, a pattern shows up, or nothing does. The exercise does not prove causation. The partner may have turned up because the deal was already going well, rather than the other way around. But if the deals you won are precisely the ones where a third party already knew how to work with you, that changes what you ask your sales team for next quarter.
And if no pattern shows up, price becomes the right question again.
On our last three lost large accounts, who wrote the target architecture, and did anyone here know that person before the tender opened?
What I can’t do : Build a mature channel in 3 weeks. Trust and the reflex to recommend cannot be bought. What I can do: identify the right partners, win the first sponsors, and use an existing network to speed up the first proof points.
Grid · 10 rows · 6 columns · 15 minutes
Third-party log for your large accounts
Ten lines on your large accounts, and an outside reading of what those ten lines say, or do not say.
Sources
- FY27 Consulting Partner Program — Salesforce, n.d.
72 % des déploiements impliquent un partenaire - Consulting Partner Program — Salesforce, n.d.
6,93 $ de revenu partenaire pour 1 $ Salesforce en 2028 - Solutions Partner FAQ — Microsoft, n.d.
Performance, compétences certifiées et succès client comme critères partenaires - AWS Competency Program — AWS, n.d.
Expertise technique et succès clients démontrés - Service Partner Program — SAP, n.d.
Qualité reproductible, réduction des escalades, dilution de la marge - Salesforce Industry Solutions — Deloitte, n.d.
Solutions et accélérateurs préconfigurés réutilisables - Salesforce Alliance — Accenture, n.d.
Plus de 1 000 déploiements et 2 500 certifications revendiqués
We sell direct and it works. Why open this up?
As long as your deals close with no third party in the room, the question does not arise. It arises the day the amounts go up and a consultancy writes the requirements before your first meeting.
How long before a partner really recommends us?
The reflex to recommend is built on proof: one successful deployment, one reusable template, one escalation handled well. It is not a contract signed on a Tuesday. The exercise is there to tell you whether you already have such a partner without knowing it.
Do we need a formal partner programme to start?
Not at the beginning. A programme with no deployment proof attracts nobody. The first signatories come because a project paid them, not because a document describes discount tiers.