For B2B SaaS teams choosing technology partners
Partner FitPartner selection is a data problem - every partner earns its rung with evidence, and finance trusts only two capped numbers.
Answer a short interview, then paste your candidate partners and the certifications you plan to join. Your browser reads each partner's demand evidence, places it on the depth ladder from referral to OEM, ranks the portfolio and where the function reports, and checks certification renewals and attribution. Then the portfolio, and the attribution rules.
The company, and a short interview free
The partners and the certifications free
The checks free
What the page flags
The gates
Portfolio, ladder and reporting line, ranked
The scorecard and the certifications
Area by area
Your attribution rules draft free
The rules RevOps builds into the CRM - two capped numbers claimed at creation - with what is not true yet called out.
Attribution rules (Markdown)
The partnership portfolio metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved portfolios
How it works - and what is sourced
The ladder follows the skill. Every candidate needs a written demand-evidence line - deals, requests, customer share or retention - or it is parked. Co-sell is the default rung; thin evidence steps down to referral; the reseller rung is deleted when the model cannot carry partner-transacted deals; co-build and OEM are earned only on proven joint economics, and then governed like a product with a joint plan and real QBRs.
A certification is a standing cost with a renewal owner, never a launch project. Finance trusts only two capped numbers - sourced and influenced - claimed on the CRM opportunity at deal creation inside a short window, with equal AE comp and one forecast review. The function reports into Sales by default, under Product to productize, and earns a standalone Alliances org.