Skill detail
company-cfo
Monthly CFO workflow for a company: pulls bank, processor, payroll, and expense data, reconciles, computes cash, forecasts scenarios, and writes a snapshot report.
Why we recommend it: Company cash flow, runway, and budgeting workflow; adjacent to personal finance but scoped to business books.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: company-cfo
description: Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse."
metadata:
version: 0.1.1
---
# /company-cfo — Monthly company CFO workflow
The standing analysis leadership uses to make distribution / cuts / hiring / runway decisions. Primary cadence is **monthly** (run on the 1st for the closed prior month). Weekly and scenario modes cover the in-between.
Anonymized team-scope sibling to `personal-cfo` (households). Same discipline (transaction-sum EOM, categorization traps, scenario modeling) applied to company books.
## Step 0 — Load company config + prior run
Before starting work, read these in order:
1. **`${COMPANY_CFO_ROOT:-$HOME/code/company-cfo}/CLAUDE.md`** — your company's specific methodology, data source map, categorization rules, distribution mechanics. **This is the source of truth for HOW your company computes things.** Don't invent your own methodology.
2. **The most recent report** in `${COMPANY_CFO_ROOT}/reports/monthly/` — last month's snapshot. Tells you what leadership decided + what was open.
3. **The most recent `*-followup.md`** in that folder (if one exists) — supplementary decisions, scenario analysis.
4. **Any relevant memory notes** in `~/.claude/memory/` — running context: known anomalies, leadership constraints, current churn state.
5. **`git log --oneline -10`** in `${COMPANY_CFO_ROOT}` — what's shipped since the last run.
If the `COMPANY_CFO_ROOT` dir doesn't exist yet: first-run walkthrough asks the user to `mkdir` it, seed a `CLAUDE.md` from `references/company-config-template.md`, and set the env var.
## Step 1 — Parse mode
| Invocation | Mode | Cadence |
|---|---|---|
| `/company-cfo monthly` (default) | **monthly** | Once per month on the 1st for the closed prior month |
| `/company-cfo weekly` | **weekly** | Thin cash pulse — current cash + next 2 weeks of expected flows |
| `/company-cfo scenario <question>` | **scenario** | Ad-hoc modeling in the projector |
| `/company-cfo pickup` | **pickup** | Resume where the prior run left off (checks git log + last report + open items) |
Below sections walk through **monthly** in detail. Weekly + scenario are summarized at the end.
---
## Monthly workflow
Ask the user: **Which month are we reporting on?** (Default: prior calendar month.)
Then walk through these phases. Pause and confirm before moving to the next.
### Phase 1 — Pull raw data
For the target month, pull raw data from each source. Standard source categories (each company's actual tools live in their `CLAUDE.md`):
| Source category | What it gives | Common tools |
|---|---|---|
| **Bank / cash accounts** | Cash truth, internal vs external transfers, distribution recipients | Mercury CLI, Plaid, direct bank export |
| **Payment processor** | Revenue, subscriptions, churn, payout timing | Stripe API, Paddle, LemonSqueezy |
| **Payroll / contractors** | W-2 payroll, contractor pay | Plane, Deel, Gusto, Rippling |
| **Expense management** | Reimbursements, corporate cards | Ramp, Brex, Divvy |
| **Alternative revenue** | Non-primary billing sources | Direct invoice tools, alternative payRead the full source on GitHub (opens external page)