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 to run the daily field motion: routes, call plans, face-to-face cadence, and post-call follow-through.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this to run the daily field motion. Start from the territory with account tiers and market potential, the call pattern or cadence SLAs, this week's route days, and the open threads from prior calls.
Prioritize the book by call pattern and market potential: tier each account, set the face-to-face cadence per tier, and sequence this week's route so the highest-potential due calls come first.
Plan the route day by day: calls in drive order, objective per call, and buffer for the drop-in that matters. A day with no plan is a day the territory plans for you.
Write the pre-call plan before every call: the objective, the two questions that matter, the likely objection with your answer, and the word-for-word ask. One screen, five minutes, no exceptions.
Keep the face-to-face cadence SLA: tier-A accounts see you on schedule, and a missed cadence gets a rebook date within the week, not next quarter.
Write the post-call analysis right after: what was learned, what changed on the opportunity, the dated next step, and the CRM update drafted. The call is not done until the note exists.
Review the week against the plan: calls made versus planned, cadence hits and misses, pipeline moved, and next week's route seeded. Misses get a cause and a fix, not a carry-forward. Hold the review as a weekly 1:1 pipeline inspection first; the team review is optional. Cover late-stage deals fast, then dissect early-stage ones: how you will work each, the next step, and why any stage moved back. Open with forecast variance before wins, work from a pre-read dashboard, and keep live time for decisions only.
The tiered call plan with cadences, daily routes in drive order, pre-call plans, post-call notes with dated next steps, and a week review with fixes.
No tiering yet means you draft tiers from deal size and potential labeled INFERENCE and get their yes. No CRM access means the call log lives in the sheet until it can be keyed in. Nothing goes to the buyer and no commitment is promised without your explicit 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.