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 hits its lifecycle tail: change control mid-term, the renewal play from 120 days out, and clean exits with dated transitions.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when a partnership reaches its lifecycle tail. Start from the agreement (term, renewal, notice, exit clauses), the partnership health and delivery reads, the renewal or change request itself, and who owns the commercial call.
Log the requested change, its commercial and delivery impact, and the approval it needs. No change takes effect without the owner's yes and a dated amendment note.
Scope creep with no change record behind it gets called out, not absorbed.
Open the renewal window 120 days out with a health grade, a wins-and-gaps record, and the renewal motion: auto-renew, renegotiate, expand, or exit.
The 90-day mark is the standard non-renewal notice deadline, and the play has to beat it rather than meet it.
A renegotiation draft pairs every ask with a concession, and every concession sits inside the guardrail bands.
The notice-period timeline, the client and pipeline transition, the knowledge handover, and the joint statement draft.
Exits are staged as drafts with their evidence. The owner makes the call.
Every renewal, amendment, and exit, dated with its trigger and its outcome, so the next cycle starts from evidence instead of recollection.
The change log, the renewal play with its drafts, the exit plan where one is called for, and the updated lifecycle log.
No agreement on file means drafting from owner-stated terms marked INFERENCE, and flagging Legal review as the first step. No health read means running the portfolio health scan before the renewal play.
No renewal term, amendment, or exit notice goes to the partner 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.
日本語の概要は準備中です。原文の説明を表示しています。