Every ISV I work with wants visibility into partner pipeline. Almost none of them have it. The usual fix is a recurring pipeline review, and the usual result is a meeting the partner reschedules four times and then quietly stops attending.

I have been on both sides of that call. On the vendor side, I needed numbers for my own forecast. On the partner side, I watched sales managers dodge vendor reviews because the meeting gave them nothing and took an hour.

Why partners avoid your review

Your partner is not your sales team. They do not report to you, and your product is one of many they carry. When you run a partner pipeline review the way you run an internal forecast call, the partner hears one message: "Justify yourself to me."

That is the forecast interrogation pattern. Go deal by deal, ask for close dates, push on why the date slipped, ask for the next step, then log it in your CRM. The partner gets nothing out of it and leaves feeling audited.

They will stop showing up, or they will show up with a sanitized list that tells you nothing.

Cadence

For most partners, monthly is the right rhythm. Weekly is too much for a partner where you are one product of fifteen. Quarterly is too long, because deals change a lot in 90 days and you lose the chance to help.

For your top two or three partners, it can make sense to go every two weeks, especially during the quarter end. Ask them. Some will want it, and some will tell you monthly is plenty.

Keep it to 30 minutes. If you need an hour, you are either covering too much or doing the partner's pipeline management for them.

Who should attend

From the partner side, the sales manager or the rep who owns the deals. Not the owner, unless it is a small firm where the owner is the sales team.

From your side, the channel manager who owns that partner. Bring a sales engineer only when there is a specific deal that needs technical help. An extra person from your company in every call makes it feel like a review board.

What to ask

I shift the questions from "when will this close" to "what is in the way." The same information comes out, but the partner experiences it as help instead of an audit.

Questions I use:

  • Which of these deals are you most worried about, and why?
  • Where is the customer stuck right now?
  • Is there anything on our side slowing this down? Pricing, a missing feature, a slow trial license?
  • Are there customers in your install base we should be talking about that are not on this list yet?

That last question is where a lot of new pipeline comes from. Partners often have customers who are a fit but have not been approached, because nobody has had time to think about it.

What not to ask

Do not ask for probability percentages. Partners do not track your product's deals with that kind of rigor, and the numbers they give you will be made up on the spot.

Do not argue about a slipped close date. Ask what changed, and move on.

Do not ask the partner to update your CRM or partner portal as a condition of the meeting. If you want the data in your system, have your channel manager enter it after the call.

Keep the forecast separate

You still need a number for your own leadership. That is fine. Build it yourself from what you learn in these reviews, plus your deal registration data, plus your own judgment about each partner's track record.

I apply a partner-specific discount to their pipeline. A partner who has historically closed 30 percent of what they show me gets their list weighted that way, whatever close dates they gave me. That keeps the partner conversation honest and the internal forecast realistic, without making the partner do my forecasting job.

What you bring them

This is the part most ISVs skip. If the partner gives you 30 minutes of pipeline detail, they should leave with something worth more than 30 minutes.

Options that work well:

  • Deal help. Offer a demo, a reference customer, a technical call, or a pricing exception on a specific stuck deal. This is the most valuable thing you can bring.
  • Leads. If you have inbound interest in their territory or vertical, bring it to the review. Nothing changes a partner's attitude toward your meeting faster than receiving a qualified lead in it.
  • Product news early. A roadmap item that solves an objection they have been hearing. Partners like being told before the public announcement.
  • Peer intelligence. What other partners are seeing work, without naming the partner or customer. "Two partners closed deals this quarter by bundling us into the year-one renewal conversation" is useful information.

If you cannot bring at least one of these to every review, the meeting is not ready to happen. Postpone it rather than run an empty one.

Track what you give, not just what you get

I keep a simple log for each partner. Date of the review, deals discussed, what we offered, and what happened. After a quarter, the pattern is obvious.

Some partners take the help and close deals. Some take the help and nothing moves. Some never need the help. Each of those calls for a different relationship, and the log gives you the evidence to have that conversation directly.

When the pipeline is empty

Sometimes the partner shows up with nothing. Do not treat that as a failure in the meeting. Turn the call into an account planning session and walk their customer list together for 20 minutes.

If the pipeline is empty three months in a row, it is time to ask a harder question. Either your product does not fit this partner's customers, or something in your pricing or packaging makes it hard to sell. Sometimes the answer is that this partner should be a referral partner instead of a reseller.

The test

The test for a good partner pipeline review is simple. Does the partner ever ask to schedule the next one before you do?

When that happens, you have built a meeting they value. That is the version of the pipeline review that actually gives you the visibility you were after in the first place.