treasury-and-liquidity
Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/treasury-and-liquidity && cp -r /tmp/treasury-and-liquidity/plugins/finance/skills/treasury-and-liquidity ~/.claude/skills/treasury-and-liquiditySKILL.md
# Treasury and liquidity Profitable companies fail on cash. Earnings are an opinion arrived at through accruals; cash is a balance you either have on the day or do not. ## Forecast cash directly The indirect method — net income adjusted for non-cash items — is right for reporting and nearly useless for operating. Build a direct forecast of receipts and disbursements by week, from actual expected timing. Thirteen weeks is the working horizon: long enough to act, short enough to be accurate. Roll it weekly and **compare last week's forecast against what happened**. A forecast never checked against outturn does not improve, and its errors are the most useful information it produces. Model timing, not just amount. A receipt that arrives four days late is the same money and a different liquidity position. ## Runway is a decision variable Runway is cash divided by net burn, but the useful version is scenario-based: the plan, a downside where revenue underperforms, and the case where a large receivable slips. Know your decision points in advance — the date by which a raise must start, the date a cost reduction must be committed to take effect in time. Decision dates always precede the cash-out date, often by more than people assume, and discovering that late removes the good options. ## Working capital is free financing, or a leak Cash is trapped in the cycle between paying for inputs and being paid for output: - **Receivables** — invoice promptly and accurately; disputed invoices age indefinitely, and most disputes trace to an invoice that did not match the contract. Watch the aging trend, not the average. - **Payables** — take terms offered, pay on time rather than early, and do not fund suppliers who did not ask to be funded. - **Inventory** — every unit is cash on a shelf. See `operations:supply-chain-and-logistics`. A week off the cycle is permanent working capital released, and it costs nothing in interest. ## Where cash sits Concentration in one bank is a single point of failure, as depositors have periodically rediscovered. Spread operating balances against counterparty limits, and hold reserves in instruments whose maturity matches when the money is needed. Do not reach for yield with money you have a date for. The return on operating cash is not worth the liquidity risk, and treasury losses of this kind are always described afterwards as conservative investments. ## Tooling Cash visibility and forecasting: Kyriba, Trovata, Tesorio, and similar. Bank portals plus a spreadsheet cover a single-bank, single-currency position honestly. Payments and AP: Bill.com, Tipalti, Ramp, Brex, and similar. The control that matters is not in the tool list — it is dual approval on payment release, by whatever means you get it. ## Never - Run the business on an indirect cash forecast. - Report runway as a single number without a downside case. - Let the decision date for financing pass while watching the cash-out date. - Concentrate operating cash in one counterparty because the relationship is convenient.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.