License revenue has nowhere to live
You quote the client one number and earn a different one. Your CRM cannot model the difference, so it stops tracking at closed-won.
A partner firm sells licenses it does not invoice and earns revenue it cannot easily name. No standard tool was built to hold that.
The proposal and the books never match. You quote the client a full ARR figure: ten licenses, 100 dollars per user, one year, 12,000 dollars. But you do not earn 12,000 dollars. You earn a commission percentage of it, the vendor invoices the client directly, the client pays the vendor, and the vendor pays you. The number on the proposal and the number in your revenue are two different facts about the same deal.
Then it gets more specific
- The commission rate depends on the product, the deal size, and who sourced it
- The term might be monthly, annual, or multi-year, each with its own renewal behavior
- Sometimes the license revenue flows into the client’s delivery budget, sometimes it does not, and you need that to be a choice
- Recognition might happen at close or at payment, and accounting treats each path differently
A sales CRM models a deal as one number that goes to closed-won. License revenue is at least three numbers, and the deal is not over when it closes. It renews.
Why this matters
Renewals are revenue you already earned the right to and can still lose. A CRM built for one-time sales does not surface a renewal date until the revenue is already gone. Multiply that across a book of multi-year license deals and the leak is structural.
PartnerView models license revenue the way it actually behaves: quoted value and earned value as separate fields, commission logic per vendor, renewal dates that surface before they lapse, and an explicit choice about whether the revenue touches the delivery budget. The number stops falling through the floor.