Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Use when the portfolio needs program-level design: tiers, incentives, the MDF loop end to end, certifications, and enforced partner-system rules.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when the portfolio needs program-level design rather than one partner's plan. Start from the partner portfolio, the current tiers, the incentive and market development fund (MDF) spend, the partner relationship management (PRM) system in use, and the certification state.
Three tiers by default, four at most. Each tier gets a name, a weighted earn scorecard — partner-sourced revenue, joint deals, certifications, joint business plan participation, co-marketing engagement — with partial credit rather than a revenue cliff, and what the tier unlocks: exposure, MDF access, registration queue priority, margin deltas.
Graduation and demotion bars need teeth: tiers recomputed quarterly and losable. If nobody has been demoted in twelve months, the bar is a ratchet, and you say so.
As a rule of thumb the middle tier should be reachable by 60 to 70 percent of partners within eighteen months, or the bar is too high.
Pilot before you publish: shadow-score fifteen to twenty-five partners on trailing twelve-month data, and communicate 60 to 90 days before the first real review. Publish a partner-facing tier sheet draft with progress indicators toward the next tier.
MDF, sales performance incentive funds (SPIFs), rebates, and co-sell funds, each with a guardrail band. Fund initiatives against outcomes, never as per-partner entitlements.
Check fiscal-year expiry and reallocate unspent or underperforming funds quarterly on documented results.
Tier rules, registration operations, claim workflows, and certification tracking as enforced rules — plus automation triggers for a new registration, a stale claim, a lapsed certification, and a tier change — and the admin checklist that keeps them honest.
The registration block: BANT-qualified opportunities only (budget, authority, need, timeline); eligibility on new-logo against upsell plus deal size and type; a two-business-day approval SLA; a 90-day protection window renewable on activity; documented overlap and escalation rules with a fair dispute audit; and decline reasons limited to named causes — house account, already registered, partner not in good standing.
Certification tracking sends renewal reminders 60 and 30 days before expiry, then fires the lapse trigger.
The tier sheet draft, the incentive portfolio with its bands, the MDF loop with its SLAs, and the enforced rule list.
No partner system means the same rules as a tracked sheet with owners, and you say what breaks at scale. No MDF pool means an organic-only program, and you say so.
Tier changes, fund approvals, and anything partner-facing wait for your yes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.