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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a deal moves with a partner: software vendor, channel, distributor, or consulting partner, from joint plan to joint close.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ad variants that each test one idea, within platform limits and supported claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.