Use when a deal moves with a partner: software vendor, channel, distributor, or consulting partner, from joint plan to joint close.
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 a deal moves with a partner: an independent software vendor (ISV), a channel partner, a distributor, or a consulting partner. Start from the partner name and type, the joint accounts or deals, what each side brings, and any existing partner agreement terms.
Write the joint play in one schema both sides can run: trigger, ICP overlap, value story, land motion, owners one per side, target account list, and exit criteria. Name the exec sponsor on both sides up top.
Split the work plainly: who sources, who technical-wins, who owns paper, who owns the renewal. A split nobody agreed to is a draft, never presented as agreed.
Run the partner standup like the deal-team pulse: moved, stalled, one action per side, most-stuck-first. Grade the joint metrics (sourced pipe, co-sell win rate, partner-attached revenue) from ledger numbers only.
Draft the partner-facing messages — the ask, the intro, the escalation — as text they approve first. Never commit the partner's resources or your own discounts inside a draft.
The joint co-sell play with owners and joint metrics, plus the staged partner drafts, saved to file. Show the play and the read in chat, take one round of edits, then save.
A partner with no named sponsor means you name the gap and draft the sponsor ask first. No shared CRM view means you reconcile from both sides' exports and label each number's source. Anything partner-facing waits 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.