A partner adds your line when the numbers work for its business. A feature comparison rarely decides it. Demand, gross profit, the effort to get started and the risk to its customer relationships decide whether it signs. Support, channel conflict rules and people who answer the phone decide whether it keeps selling. Pitch those, in that order, with a one-page business case built on the partner’s own numbers.
partners are adding and cutting at the same time
In Canalys’s 2025 survey of 1,010 partners, as reported by Dutch IT Channel, about half planned to expand their vendor portfolio and 48% planned to reduce it, with cybersecurity named as the main growth area. Futurum’s 2026 survey found the average portfolio narrowing from 5.47 to 4.99 technology categories.
Read together: partners are open to new security vendors, and they are also clearing out the ones that cost them time. Your line competes for a shrinking amount of attention, and often it has to replace something to get in.
the partner’s decision, factor by factor
decides whether it signs
the first meeting
- Demand. Will my customers buy this, and when?
- Profit. How much gross profit per deal, with services and renewals?
- Effort. How many engineer days to learn, demo and deploy?
- Risk. Could this cost me a customer or a tender?
decides whether it keeps selling
the first two years
- Fit. Does it compete with a line we depend on?
- Conflict. Will the vendor take my customers once I've built the market?
- Support. Does anyone help when a deployment breaks?
- People. Do these people answer the phone?
None of this is new. A Forrester analysis from 2010 listed market potential, revenue and profit streams, enablement, ease of doing business and how the vendor showcases successful partners. The list has aged well.
The right column is where relationships end. In CompTIA’s survey of 400 US IT firms, 50% had dropped a vendor in the previous two years because of poor partner experience, and nearly nine in ten rated technical support as a priority. GTIA’s 2026 State of the Channel found the share of partners very satisfied with their vendors down to 18%. Partners rarely terminate a contract. They stop selling.
bring the partner a business case
Partners decide on gross profit and on how many engineer days a deal consumes. A one-page case answers both, with assumptions the partner can change in the meeting.
A fictional but typical example: a 40-person integrator considers adding a privileged access line. All values are illustrative.
| Year 1 | Year 2 | Year 3 | |
|---|---|---|---|
| New customers | 3 | 5 | 6 |
| Product gross profit, at 15% of EUR 30,000 per deal | 13,500 | 22,500 | 27,000 |
| Services gross profit, 12 days per deal at EUR 300 margin per day | 10,800 | 18,000 | 21,600 |
| Renewal gross profit | 0 | 2,430 | 6,480 |
| Start-up cost: training, certification, unbilled presales | 9,000 | 2,000 | 2,000 |
| Net contribution (EUR) | 15,300 | 40,930 | 53,080 |
Three things show up in almost every case like this one.
Services matter as much as margin. Services gross profit is of the same order as product gross profit. A pitch that leads with the discount misses half the partner’s economics. Omdia describes leading security vendors moving from a margin model to a “multiplier” model that covers advisory, design, implementation and managed services. Show the partner which services it can attach to your product.
Break-even comes after the second deal. In the example each new customer brings roughly EUR 8,100 of gross profit in year one against EUR 9,000 of start-up cost. One deal loses money. Say the break-even number out loud, then lower it: your presales on the first deals, free certification seats, a lab environment.
Renewals are slow. They become material only in year three, and the shape depends on licensing. Perpetual licences with maintenance renew at a fraction of the first-year value. Subscriptions renew at close to full value, which changes the case completely. Model your actual licensing.
Rules that keep the case credible: use the partner’s own customer counts and day rates, show ranges instead of single numbers for win rate and deal size, include every start-up cost, never present your market growth slides as partner economics, and compare the case with actuals at the six-month review.
the objections you will hear
Most objections in a first partner meeting are about effort, risk and conflict. Few are about your product.
| What the partner says | What is usually behind it | What to bring |
|---|---|---|
| “We already have a vendor in this category.” | Investment in the incumbent | Where the incumbent falls short; references where both coexist |
| “Our customers don’t ask for this.” | No visible demand | Regulatory dates, tender requirements, number of buyers affected in its segment |
| “The margin is too low.” | A product-only view | The business case with services and renewals |
| “We don’t have engineers for this.” | Capacity | Hours to certification, your presales on the first deployments |
| “You’ll go direct once we build the market.” | Past experience | Written rules of engagement, named direct accounts, registration rules |
| “A tool that shortens deployments cuts our billable hours.” | Revenue depends on days | A fixed price for an outcome, with the arithmetic at their day rate |
| “We’re too busy right now.” | Low priority | A small first step: a two-hour session, one POC in a quiet quarter |
Two of these need straight answers. When a partner asks about your direct sales, say exactly which accounts your team sells to directly. When it asks what happens to its registered deals and renewals if your channel model changes, describe the terms. Evasive answers here end relationships later.
proof, and promises you can keep
Proof that a partner believes comes from other partners: a reference call with a partner of similar size, the time your support took to answer during a real deployment, registration approval times. Joint selling is proof too. In the CompTIA survey, half of the respondents said joint selling makes their firm look bigger. For a small integrator, your engineer in front of its customer is often the strongest argument you have.
Then deliver it. A value proposition that is not delivered in the first 90 days pushes the partner into the inactive majority. Promise what you can do for two years, write it into a one-page working agreement, and review it together at day 90.
the question for your channel team
When did a partner last stop selling your product, and did anyone ask it why?
questions
Why do partners add a new vendor?
When four questions have good answers: will my customers buy it, can I make money, how much effort and risk does it take, and does it fit my practice. Whether they keep selling after the first deal depends on support, channel conflict rules and whether the vendor's people answer the phone.
What should a partner business case include?
The partner's target customers, a realistic win rate, average deal value, product margin, services days per deal at the partner's own rate, renewals, and every start-up cost including unbilled presales hours. Show the number of deals the partner needs to break even.
Why do partners drop vendors?
Rarely by terminating the agreement. They stop selling, usually after slow technical support, a deal lost to the vendor's direct team despite registration, margin cuts without notice, or a key certified engineer leaving.
sources
- Forrester: the five things channel partners want from tech vendors (2010)
- Dutch IT Channel: Canalys Global Channel Partner Pulse Survey (2025)
- CompTIA: Partner Experience Trends 2022
- Omdia: 2025 vendor champions in the Cybersecurity Leadership Matrix
- GTIA: State of the Channel 2026
- Futurum Group: partner growth polarization (2026)
Security Revenue · every Tuesday
How security vendors build pipeline.