Skip to content

t1k:business:finance

FieldValue
Modulebase
Version0.12.1
Effortmedium
Tools—

Keywords: arpu, board deck, burn, burn multiple, cac, cash flow, cfo, churn, client concentration, cohort retention, currency conversion, finance, financial model, fx rate, hhi, investor report, investor update, kpi dashboard, ltv, monthly finance, mrr, nrr, p&l, pnl, profit and loss, revenue concentration, roas, rule of 40, runway, unit economics

/t1k:business:finance
[audience: investor|internal|board] [topic?]

A knowledge-base skill for generating finance reports tailored to audience (investor / internal ops / board / founders) from raw monthly P&L + client + headcount data. Covers services firms, SaaS/product businesses, and ad-arbitrage (UA) in one unified framework — most real studios and ops-heavy startups are hybrids.

IS: Framework, methodology, KPI definitions, chart patterns, data-model patterns, worked examples, audience-aware templates. A CFO-grade reasoning toolkit.

IS NOT: A replacement for a licensed accountant/auditor. Does not generate tax filings, audit opinions, or compliance sign-off. All output is review input, not final authority. See charter.md for full boundaries.

User asks about…Primary reference(s)
“investor update”, “investor email”, “monthly investor report”references/audiences.md → templates/investor-monthly.md
“board deck”, “quarterly board report”, “board metrics”references/audiences.md → templates/board-quarterly.md
“monthly ops”, “variance to plan”, “internal finance review”references/audiences.md → templates/ops-monthly-variance.md
“runway”, “burn”, “cash position”, “default-alive test”references/cash-runway.md
“unit economics”, “LTV”, “CAC”, “payback”, “Rule of 40”, “burn multiple”references/unit-economics.md
“client concentration”, “HHI”, “revenue concentration”, “top client risk”references/client-concentration.md
“client retention”, “cohort”, “churn vs pause”, “new vs existing client”references/client-concentration.md
“ROAS”, “CPI”, “cohort ROAS”, “UA payback”, “ad arbitrage”references/unit-economics.md → UA section
“P&L”, “income statement”, “gross margin”, “OpEx”, “COGS”references/p-and-l.md
“multi-currency”, “FX rate”, “USD/VND”, “currency conversion”references/multi-currency-fx.md
“how to structure finance YAML”, “data model”, “period rollup”references/data-modeling.md
“waterfall chart”, “stacked bar”, “cohort heatmap”, “accessibility”references/visualization.md
“vanity metric”, “non-GAAP reconciliation”, “finance report mistake”references/gotchas.md
“services KPI”, “utilization”, “revenue per head”, “billable rate”references/unit-economics.md → Services section
  1. Identify audience. If not stated, ask via AskUserQuestion: investor / internal / board / founders.
  2. Load references/first-principles.md — anchor every analysis in accrual vs cash, matching, conservatism, entity.
  3. Load references/audiences.md — get the audience-specific section checklist + top KPIs + commentary style + cadence.
  4. Route to domain references per the table above.
  5. Check references/gotchas.md for the 10 anti-patterns BEFORE drafting output. Currency mix-ups and double-counting are the most common.
  6. Draft the report/analysis, then self-review against gotchas + data-validation checklist.
  7. Flag uncertainty explicitly — if data has gaps or assumptions, say so in the output.

Every finance output starts with one question: “Who is reading this, and what decision must they make?” Investors decide funding/valuation → narrative + trajectory + unit economics. Internal ops decide resource allocation → variance + utilization + margin. Board decides strategy + risk → concentration + runway + scenario. Founders decide priorities → simple dashboards + red flags. The data is the same; the framing differs. Use one monthly SSOT table and re-project per audience.

This skill registers t1k-business-finance in the theonekit-business activation fragment. Keywords (see YAML frontmatter above) auto-activate this skill whenever finance/investor/board/CFO language appears in the user prompt.

The formulaic half of this skill is cheap-tier work; the narrative and every financial judgment stay on a reasoning tier (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”):

StepAgent
Compute LTV, CAC, ROAS, payback, burn multiple, runway/burn and Rule-of-40 from the stated inputs in the SSOT tablet1k-metrics-reporter
Compute HHI / client concentration and cohort-retention rates from stated revenue + cohort datat1k-metrics-reporter
Reconcile two or more sources that both claim the same figure against a stated tolerancet1k-data-verifier
Draft the board-deck / investor-update NARRATIVE, pick the framing per audience, or make any financial judgmentstays on a reasoning tier

The math is fully specified before it starts; deciding what the numbers mean for the audience is the part that pays for a reasoning tier.

  • Never expose raw payroll data by individual without the user explicitly requesting it (privacy).
  • Always label currency per number. Mixing USD and VND without unit labels is the #1 gotcha.
  • Always separate one-time items from recurring base revenue. Show both.
  • Never retroactively revalue historical transactions with today’s FX rate. Use frozen FX at transaction date.
  • Never claim compliance/audit authority — output is decision-support, not sign-off.