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 asks how big an opportunity is, names TAM, SAM, or SOM, or needs an investment case for a GTM bet: the sized opportunity with stated math and the case with returns and risks.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when the user asks how big an opportunity is, names TAM, SAM, or SOM, or needs an investment case for a GTM bet. Start from the segment or market in scope, the pricing and conversion assumptions, and the investment asked for.
TAM (everyone with the problem), SAM (those you can reach), SOM (those you can win in the horizon). Each band gets its method, sources, and date — top-down, bottom-up, or value-theory, said plainly. When Apollo is connected, the bottom-up count of accounts matching the ICP firmographics is a real number, not a guess; use it and cite the filter.
At least two methods, and name where they disagree. The gap between methods is the honest range; a case built on one method says so. Flag a bottom-up vs top-down delta over 3x, and treat SOM capture above 5% in year one as needing extraordinary proof — 1–5% is the usual range for a new entrant.
Investment, expected return, payback, and the net revenue retention, LTV/CAC, or pipeline math that carries it. State the denominator behind every rate and the benchmark you judge it against.
Base, Adverse, Opportunity. Each grade gets the driver that breaks it and the leading indicator that warns you first. Never silently rebaseline — a reforecast says what changed and why.
The verdict and the risks: fund, fund-with-conditions, or pass, each with the evidence grade behind it. You build the case; finance validates the economics before money moves. Save under sizing, one folder per case with the model — a sheet when Sheets is connected — the assumptions log, and the verdict.
No hard data means a triangulated range with the method named, never a single false-precise number. No conversion baseline means you size the ceiling and flag the case as direction-only. Never invent a market size, a growth rate, or a customer count. Label each line FACT, INFERENCE, or UNKNOWN.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。