Danny wrote about the SPIFF email you got on Valentine’s Day. The 21-day window, new logos only, three qualifying SKUs, payout 60 days after install. He roasted it. The channel loved it. I read it and thought: yeah, I designed that SPIFF. Not that exact one, but one with the same structure, for the same reasons.

This is the Channel 101 version of how SPIFFs get built. Not the partner experience of receiving one, but the vendor experience of designing one. If you’ve ever wondered why SPIFFs look the way they do, why the windows are short, why the qualification criteria feel impossible, and why they always seem to arrive at the worst possible time, this is the other side of the table.

The Budget Meeting

SPIFF design starts in a budget meeting, usually 60 to 90 days before the SPIFF launches. Someone in sales leadership has a number they need to hit by end of quarter. The pipeline says they’re going to be short. The question on the table: where do we find incremental deals?

The answer is almost always “the channel.” Not because the channel is the best source of new business, but because it’s the fastest lever to pull. Running a SPIFF is cheaper and faster than hiring direct reps, launching a marketing campaign, or developing a new product. You design it on Tuesday, get legal approval on Thursday, and send the email on Monday.

The budget for the SPIFF comes from one of three places: the channel marketing fund, the sales acceleration budget, or (in desperate quarters) the regional VP’s discretionary budget. The amount is almost never as much as the channel team asks for. I’ve sat in meetings where the channel team requested $200K for a quarter-long incentive program and got $50K for a three-week sprint. The budget dictates the design.

The Math Behind the Window

The 21-day window that Danny roasted isn’t arbitrary. It’s driven by two constraints.

First, the budget. If you have $50K and you’re paying $1,000 per qualifying deal, that’s 50 deals. If you make the window 90 days, those 50 payouts get spread thin and partners don’t feel urgency. If you compress it to 21 days, you create scarcity. Partners who were going to close a deal in 45 days try to pull it forward. That acceleration is the whole point — and it’s why every carrier changes their comp plan in February. The SPIFF isn’t designed to generate new pipeline. It’s designed to accelerate existing pipeline.

Second, the reporting cycle. Most vendors report pipeline and bookings monthly. A 21-day SPIFF that starts on the first of the month gives you results before the month-end close. A 30-day SPIFF bleeds into the next month’s reporting window. A 45-day SPIFF is useless for the quarter you’re trying to save. Finance cares about when the deal books. The SPIFF window is built around the financial calendar, not the sales cycle.

New Logos Only

The “new logos only” qualification is the most criticized SPIFF criterion in the channel. Partners hate it because their best pipeline is existing customer expansions, not new logos. From how channel partners make money, you know that the real revenue compound comes from growing existing accounts, not chasing new ones.

So why do vendors restrict SPIFFs to new logos? Because new customer acquisition is the hardest metric to move organically. Existing customers renew and expand on their own cycle. New logos require outbound effort, competitive displacement, and longer sales cycles. Without a financial incentive, most partners prioritize the easier existing-account work.

The vendor’s board doesn’t report “customer expansion” as a headline metric. They report new logo acquisition. The SPIFF is designed to feed the metric the board watches. Is that misaligned with how partners actually generate revenue? Yes. Does the vendor know that? Also yes. The misalignment is a feature, not a bug. The SPIFF is designed to compensate for the natural tendency of partners to focus on renewals.

SKU Restrictions

When a SPIFF only qualifies for specific SKUs, that’s a product team decision layered on top of a sales team initiative. Here’s what usually happened in my experience.

The product team has a new offering that’s underperforming. Maybe it launched six months ago and adoption is below forecast. The product manager goes to the channel team and says: “Can we get partners to sell this?” This is how the best partner programs differentiate themselves — by aligning incentives with products partners actually want to sell. The channel team says: “Sure, if you fund a SPIFF.” The product manager contributes budget from their product marketing fund, but the condition is that the SPIFF only qualifies for their product.

Now the sales team has a SPIFF that only applies to three SKUs. The partners who sell those SKUs love it. The partners who sell everything else see a SPIFF email that doesn’t apply to them and file it in the same mental folder as spam.

The better vendors build multi-product SPIFFs with different payout tiers by product line. The budget-constrained vendors (which is most of them) end up with narrow SPIFFs that feel exclusionary. It’s a resource problem dressed up as a program design problem.

The 60-Day Payout Problem

Danny’s point about 60-day payouts landing after 90-day provisioning cycles is accurate and uncomfortable. From the vendor side, the payout timeline is set by finance, not by the channel team.

Most vendors pay SPIFFs only after the deal is “booked,” meaning the contract is signed, the service is provisioned, and the first invoice has been generated. For telecom services, that cycle is 30 to 90 days depending on the complexity of the install. The 60-day payout clock starts after booking, not after deal registration.

The result: a partner closes a deal on day 10 of the SPIFF, provisioning takes 75 days, and the payout arrives five months after the partner did the work. By then, the partner has forgotten which SPIFF it was for, the channel manager who promoted it has moved to a different territory, and the commission statement shows a line item that nobody can explain without opening a spreadsheet.

I’ve argued internally at multiple vendors that SPIFF payouts should start at deal registration, not booking. The counter-argument from finance is always the same: “What if the deal falls through after registration?” It’s a valid concern, but the current system optimizes for risk avoidance at the expense of partner trust. And partner trust, as carrier program design shows, is the most valuable asset a channel program has.

How to Design a Better SPIFF

If I were designing a SPIFF today, here’s what I’d change:

Expand the window to 45 days. 21 days is too short for any deal that requires a customer conversation. 45 days gives partners time to accelerate real pipeline without creating false urgency.

Include expansions, not just new logos. Cap the expansion payout at 50% of the new logo rate if you need to prioritize acquisition. But don’t exclude expansions entirely. You’re punishing your best partners.

Pay at deal registration with a clawback clause. This is what TSDs have been pushing for on behalf of their agents. Pay the partner when the deal is registered and qualified. If it falls through, claw it back. This shifts the financial risk to the vendor where it belongs and gives the partner immediate reward for the behavior you want.

Communicate the why. Tell partners why this SPIFF exists. “We need to hit our Q1 number” is more honest than “exciting new incentive opportunity for valued partners.” Partners respect honesty. They resent being managed. The vendors who get this right are the ones partners actually trust.

The channel deserves to understand how these programs get built. The more partners know about the constraints vendors operate under — and about how channel economics actually work — the better they can evaluate which SPIFFs are worth chasing and which ones are designed for someone else’s pipeline.

That email you got this morning? Now you know what happened in the room before it was sent.