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 the user names a GTM plan, a new market or segment, or annual or quarterly planning, or asks how to sequence a motion: the plan with motion, sequence, coverage, and readiness.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when the user names a GTM plan, a new market or segment, annual or quarterly planning, or asks how to sequence a motion. Start from the ICP and segments, the positioning, the routes and resources on hand, and the planning horizon.
The one commercial outcome for the horizon, the number behind it, and the date. A plan without a number is a wishlist — say so and get one.
Who sells, who markets, who partners, and what the buyer journey looks like end to end. One motion per tier; a segment with no motion is explicitly out.
Land segment first, expand segments next, each with entry and exit criteria. Name what must be true before the next segment opens — proof points, references, coverage.
Books per rep, capacity per book, and the top-down vs bottom-up quota check with the gap named. Coverage math you cannot staff is a risk, not a plan.
Positioning locked, pricing signed off, enablement packed, systems and routing live, support briefed. Each item gets an owner and a date; unchecked is not complete.
RACI inputs — who decides, who executes — and the weekly or monthly forum where the plan gets reviewed against the scorecard.
The GTM plan with motion, sequence, coverage, readiness checklist, and RACI inputs, saved dated. Review it when a segment misses its exit bar. You design the plan and the motion — quota ownership stays with sales, process rigor with ops.
No segment sizing means you sequence on qualitative fit and flag sizing as the first workstream. No headcount reality means you plan the motion and hold the coverage math. Never invent a market size, a headcount number, or a commit date.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。