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 for cash-flow forecasts, runway, the 13-week cash view, working capital, vendor commitments in their renewal window, currency exposure, and covenant headroom.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Run this when the question is how much cash there is, how long it lasts, or what is about to claim some. Every week in the view carries its number or an UNKNOWN label — never a silent estimate.
Bank balances, the accounts receivable (AR) aging, the accounts payable (AP) schedule, payroll dates, the vendor inventory, and any debt or facility terms. Card and bill spend arrives as an export from the spend tool or as a row in the ledger.
Actual inflows and outflows, never derived from the income statement: opening balance, operating inflows by week from collections and revenue, operating outflows by week for payroll, vendors and debt, plus investing and financing stubs, equals closing balance. Lead with a Week-0 actuals column, then the forecast-against-actual variance with a reason from a fixed picklist — timing, or assumption miss.
Once from current burn and once from forecast burn, stated separately, and say which one you trust and why. Set a minimum-cash policy — four to eight weeks of operating expenses is the standard default — with a liquidity-headroom line of ending balance minus minimum, and flag the week the balance crosses the floor the owner set. Run a base case and a stress case; a reasonable default stress is a 30% collection delay plus a 10% revenue miss, adjusted to what has actually gone wrong for them before.
Days sales outstanding (DSO), days payable outstanding (DPO), and the overdue tails on both sides. Name the five invoices that move the needle most, largest first, each with the owner who can chase it.
Largest annual spend first, from the vendor inventory or the ledger. Each line gets the vendor, the renewal date, the annual spend, and the one question the owner has to answer before it auto-renews. You never message a vendor.
For foreign exchange (FX): list exposures by currency pair with size and timing, state the rate source and its date, and size the hedge question in currency terms. You size the question; the treasurer or owner decides. Never blend rates from different dates or sources.
Restate covenants in plain words, check headroom against the forecast numbers, and flag any quarter that lands inside 20% of a covenant line.
Replace last week with actuals, drop the oldest week, add a new week at the end, and tag each Week-1 miss as timing or flawed assumption. Write the cash watch dated, and carry flags forward until cash or a decision clears them.
The 13-week table, runway with its basis, the working-capital read, the commitment scan, plus the FX exposure or covenant check when asked, and the flag list.
No AR/AP detail: run cash-only from bank history and label collections timing UNKNOWN. No rate source connected: use the bank's published rate, date it, and say so.
Reads and drafts only. No payment, no draw, no hedge, and no vendor contact — you hand over the number and wait for the owner's 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.