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 deal is a credit facility or capital product that needs underwriting and a term sheet, not a SaaS order form.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Run this when the deal is a credit facility or capital product. Underwrite first, structure inside approval bands, and sequence internal consensus before the borrower ever sees terms.
The borrower's cash-flow picture and capital need, the facility size and use of funds, the underwriting checklist, your approval bands, and the founder, CFO, and lender-side owners.
Inflows, burn or seasonality, existing facilities, and what the new capital unlocks. Every number is FACT with a source or UNKNOWN until the statements arrive.
Size, tenor, pricing, covenants, and collateral shaped to the risk you found. If the ask exceeds the band, say so early with what would need to change.
Economics, conditions precedent, key covenants, and the path from sheet to docs to funding — commercial truth the founder and CFO can sign. Legal language waits for counsel. Label the term_state drafting while you write.
Risk, ops, and exec each get the sheet with the risks named, not hidden. An internal no after a founder yes is the failure mode, so sequence risk before the founder sees terms. The sheet stays term_state in review until every internal owner signs off, then approved.
Founder, CFO, and co-lender steps each carry a date and an owner. A quiet month gets a dated check-in, never a surprise expiry.
The signed sheet (term_state signed) goes with the conditions checklist attached: each condition precedent has an owner and a date, and funding waits on all of them.
Cash-flow read with sourced numbers, an offer inside approval bands, a plain-terms sheet draft, internal consensus log, and a dated cycle tracker through funding.
No financials yet: record the founder's stated numbers as claims, each attributed to them, and leave the number itself UNKNOWN until the statements arrive — the rule above does not bend because the statements are late. List exactly which statements close the gap. No approval bands on file: ask for them before any structure is shown.
Nothing goes to the borrower and no size, price, or term 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.
日本語の概要は準備中です。原文の説明を表示しています。