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 partnership needs numbers behind the terms: business case, deal profit and loss with sensitivity, guardrail bands, and reusable templates.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when a partnership needs numbers behind its terms. Start from the deal shape, the money expectations on both sides, the volume assumptions, and the guardrails the owner wants.
Upside, cost, payback window, and the top three risks. Every load-bearing number is labelled FACT, INFERENCE, or UNKNOWN with its source.
Never invent a number. A missing input is named, not estimated into place.
Fees, margins, revenue share, payout triggers, and marketplace fees where they apply — with sensitivity on volume at base, low, and high.
Show the break-even line. A range without a break-even is a vibe, not a model.
Revenue-share bands, MDF caps, discount floors, and the floor-approval owner per band.
Anything outside a band is an exception draft for the owner, never a quiet yes.
Turn the modelled terms into deal templates the next partnership starts from, and score the portfolio on one prioritisation card — potential, impact, fit, readiness — so the next dollar goes where the math says.
The business case, the profit-and-loss model with its sensitivity, the guardrail bands, and the templates plus the portfolio card.
No volume data means modelling with the missing inputs left blank and naming the report or the contact that fills them. No precedent deals means wider bands, and you say so.
Every number here is a draft. Committed terms need 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.
日本語の概要は準備中です。原文の説明を表示しています。