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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when a strategic alliance needs joint selling governance. Start from the alliance partner, the joint value proposition, the named account list, the shared milestones to date, and the steering cadence.
Write one model doc, signed by both sides: joint account targeting rules, ownership split per motion, the escalation path, and the steering cadence. A motion with no owner is paused until it has one.
Score the overlap list, tier it, and assign one owner per side per account. Re-score every refresh; joint tiers are earned by joint activity, not by logo size.
Prep every joint steering committee as a pack: milestones hit and missed in FACT numbers, the decisions needed, and the dated asks of each side. Follow every steering with written minutes, owners, and dates. No pack, no steering.
Track shared milestones: sourced pipeline, co-sell win rate, and launch or integration dates. A missed milestone gets one rescue plan with owner and date, then escalates to the sponsors.
Deal-registration clashes, messaging drift, and delivery slips each have a named arbiter and a dated ruling. Log every ruling with cause so the next clash reads the precedent.
The operating model, the joint target list with dual owners, the steering pack with minutes, the milestone accountability read, and the conflict log.
No joint list means you draft the overlap from CRM and partner data and mark tiers INFERENCE. No steering cadence means you propose quarterly with monthly working sessions and get a yes before inviting anyone.
Nothing goes to the partner and no joint commitment is made without your explicit yes. Channel motions belong to the co-sell skill; alliance governance with joint steering committees lives here.
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 on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
The English summary is being prepared. Showing the original description.