cfo-advisor▌
borghei/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
The agent acts as a fractional CFO, providing financial strategy and operational finance guidance grounded in SaaS benchmarks, GAAP standards, and investor expectations.
CFO Advisor
The agent acts as a fractional CFO, providing financial strategy and operational finance guidance grounded in SaaS benchmarks, GAAP standards, and investor expectations.
Workflow
- Establish financial baseline -- Collect current ARR, burn rate, cash balance, and headcount. Calculate runway in months. Validate that the data is recent (within 30 days).
- Build unit economics -- Calculate CAC, LTV, CAC Payback, LTV:CAC ratio, NRR, and Burn Multiple using the formulas below. Flag any metric outside benchmark ranges.
- Construct financial model -- Build a 3-year model following the Revenue Build and Expense Build structures. Document all key assumptions explicitly.
- Design investor reporting -- Configure the Monthly Metrics Package template. Set up the Board Financial Presentation slide structure for quarterly use.
- Set up cash management -- Build the 13-week cash flow forecast. Establish the monthly rolling forecast. Verify minimum 6-month runway is maintained.
- Establish close cadence -- Implement the Month-End Timeline (Day 1-12). Assign owners to each quality checklist item.
- Assess risk posture -- Review market, credit, and operational risk categories. Confirm insurance coverage is adequate for company stage.
SaaS Unit Economics
CAC = (Sales + Marketing Spend) / New Customers
CAC Payback = CAC / (ARPU x Gross Margin)
LTV = ARPU x Gross Margin x Customer Lifetime
LTV:CAC Ratio = LTV / CAC Target: > 3:1
Logo Retention = (Customers End - New) / Customers Start
Net Revenue Retention = (MRR End - Churn + Expansion) / MRR Start
Burn Multiple
Burn Multiple = Net Burn / Net New ARR
< 1.0x Excellent efficiency
1.0-1.5x Good efficiency
1.5-2.0x Average
> 2.0x Needs improvement
Rule of 40
Rule of 40 = Revenue Growth % + Profit Margin %
> 40% Strong performance
20-40% Acceptable
< 20% Needs attention
Monthly Metrics Package
FINANCIAL HIGHLIGHTS
- Revenue: $X.XM (vs Plan: +/-Y%)
- Gross Margin: XX% (vs Plan: +/-Y%)
- Operating Loss: $X.XM (vs Plan: +/-Y%)
- Cash Balance: $X.XM
- Runway: XX months
REVENUE METRICS
- ARR: $X.XM (+Y% QoQ)
- Net New ARR: $XXK
- NRR: XXX%
- Logo Churn: X.X%
EFFICIENCY METRICS
- CAC: $X,XXX
- CAC Payback: XX months
- Burn Multiple: X.Xx
Board Financial Presentation
- Financial summary (1 slide)
- Revenue performance (1-2 slides)
- Expense breakdown (1 slide)
- Cash flow and runway (1 slide)
- Key metrics trends (1 slide)
- Forecast outlook (1 slide)
Revenue Build (Financial Model)
- Starting ARR / customers
- New logo assumptions (by segment)
- Expansion rate
- Churn rate
- Pricing changes
- Segment mix
Expense Build (Financial Model)
- Headcount plan (by department)
- Comp and benefits
- Contractors
- Software / tools
- Facilities
- Marketing programs
- Travel and events
Budget Categories
| Category | Line Items |
|---|---|
| Revenue | New business (by segment), expansion, renewals, professional services |
| Cost of Revenue | Hosting/infrastructure, support, PS delivery, payment processing |
| OpEx | Sales & Marketing, R&D, G&A |
Month-End Close Timeline
| Days | Activity |
|---|---|
| 1-3 | Transaction cutoff |
| 3-5 | Reconciliations |
| 5-7 | Accruals and adjustments |
| 7-10 | Management review |
| 10-12 | Final close |
Quality Checklist: Bank reconciliation, revenue recognition, expense accruals, prepaid amortization, deferred revenue, intercompany elimination, flux analysis.
Revenue Recognition (ASC 606)
- Identify the contract
- Identify performance obligations
- Determine transaction price
- Allocate price to obligations
- Recognize revenue when satisfied
SaaS considerations: Subscription vs usage revenue, implementation services, professional services, multi-year contracts, discounts and credits.
Cash Management
13-Week Cash Flow: Week-by-week projections of all known inflows/outflows. Review weekly. Maintain minimum cash buffer.
Monthly Rolling Forecast: 12-month forward view covering revenue collection timing, payroll, vendor payments, debt service, and CapEx.
Treasury Principles: Maintain 6+ months runway, preserve capital, optimize yield on idle cash, follow investment policy.
Cash Preservation Levers (when extending runway):
- Hiring freeze
- Vendor renegotiation
- Discretionary spend cuts
- Payment term extension
- Revenue acceleration
- Bridge financing
Due Diligence Data Room Checklist
Financial data:
- 3 years historical financials
- Monthly P&L by segment
- Balance sheet and cash flow
- ARR/MRR cohort analysis
- Customer unit economics
- Revenue recognition policy
- AR aging
- AP summary
Projections:
- 3-5 year financial model
- Key assumptions documented
- Sensitivity analysis
- Use of funds breakdown
- Path to profitability
Financial Risk Categories
| Risk Type | Key Concerns |
|---|---|
| Market | Interest rate exposure, FX exposure, customer concentration |
| Credit | Customer creditworthiness, AR aging, bad debt reserves |
| Operational | Internal controls, fraud prevention, systems reliability |
Example: Series-A SaaS Financial Snapshot
A Series-A company ($3M ARR, 35 employees, $12M raised) preparing for Series B:
Unit Economics:
CAC: $22K | LTV: $88K | LTV:CAC: 4.0x | CAC Payback: 16 months
NRR: 115% | Logo Retention: 90% | Gross Margin: 78%
Burn:
Monthly burn: $350K | Net new ARR/month: $180K
Burn Multiple: 1.9x (average -- needs improvement for Series B)
Cash: $5.2M | Runway: 15 months
Rule of 40:
Revenue growth: 95% YoY | Profit margin: -40%
Score: 55% (strong)
Board recommendation: Raise in 6 months at current trajectory.
Target metrics for raise: Burn Multiple < 1.5x, NRR > 120%.
Essential Insurance Policies
D&O, E&O, Cyber liability, General liability, Workers compensation, Key person insurance.
Scripts
# Unit economics calculator
python scripts/unit_economics.py --metrics data.csv
# Cash flow projector
python scripts/cash_forecast.py --actuals Q1.csv --assumptions model.yaml
# Financial model builder
python scripts/fin_model.py --template saas --output model.xlsx
# Investor metrics dashboard
python scripts/investor_metrics.py --period monthly
References
references/financial_modeling.md-- Model building guidereferences/saas_metrics.md-- SaaS metrics deep divereferences/accounting_policies.md-- Policy documentationreferences/audit_prep.md-- Audit readiness guide
Tool Reference
financial_health_scorer.py
Comprehensive SaaS financial health assessment: Rule of 40, burn multiple, LTV:CAC, CAC payback, NRR, magic number, and composite score with investor-readiness verdict.
# Run with demo data (Series A SaaS)
python scripts/financial_health_scorer.py
# Quick assessment with key metrics
python scripts/financial_health_scorer.py --arr 3000000 --revenue-growth 95 --profit-margin -40 --burn 350000 --cash 5200000 --nrr 115 --gross-margin 78 --headcount 35
# From JSON file
python scripts/financial_health_scorer.py --input financials.json
# JSON output
python scripts/financial_health_scorer.py --input financials.json --json
burn_rate_calculator.py
Models burn rate, runway under 5 scenarios (current, hiring freeze, 10% cut, 20% cut, revenue acceleration), generates 13-week cash flow forecast, and identifies action triggers.
# Run with demo data
python scripts/burn_rate_calculator.py
# Quick calculation
python scripts/burn_rate_calculator.py --cash 5200000 --revenue 250000 --expenses 600000 --headcount 35
# JSON output
python scripts/burn_rate_calculator.py --json
scenario_modeler.py
Three-scenario financial projection engine with probability weighting, sensitivity analysis, and decision triggers. Projects base, upside, and downside cases over 8 quarters.
# Run with demo data
python scripts/scenario_modeler.py
# Quick model from key inputs
python scripts/scenario_modeler.py --arr 3000000 --expenses 900000 --cash 5200000 --quarters 8
# From JSON with custom scenarios
python scripts/scenario_modeler.py --input scenarios.json
# JSON output
python scripts/scenario_modeler.py --json
Troubleshooting
| Problem | Likely Cause | Fix |
|---|---|---|
| Burn multiple shows > 3.0x | Spending significantly outpaces net new ARR | Audit S&M efficiency; consider hiring freeze; validate pipeline conversion rates |
| Rule of 40 score below 20% | Growth has slowed without corresponding margin improvement | Either re-accelerate growth or cut costs to improve margins -- cannot stay in the middle |
| CAC payback exceeds 24 months | Sales cycle too long, ACV too low, or S&M spend too high | Segment CAC by channel; cut underperforming channels; raise ACV through pricing |
| LTV:CAC ratio below 2.0x | Customer lifetime too short (churn) or acquisition too expensive | Address churn first (higher ROI); then optimize CAC by channel |
| NRR below 100% | Contraction and churn exceed expansion revenue | Build expansion playbook; segment churning customers; invest in customer success |
| Financial model assumptions questioned by board | Assumptions not documented or unrealistic | Document every assumption explicitly; show sensitivity analysis for key variables |
| Month-end close takes 15+ days | Manual processes, missing reconciliations, or unclear ownership | Implement the Day 1-12 close timeline; assign owners to each checklist item |
Success Criteria
- Financial health composite score above 65/100 (measured quarterly via financial_health_scorer.py)
- Rule of 40 score maintained above 40% for Series B+ companies
- Burn multiple below 2.0x (below 1.5x for Series B readiness)
- CAC payback under 18 months (under 12 months for top-quartile performance)
- Month-end close completed within 12 business days with zero material adjustments
- Board financial presentation completed 48+ hours before every board meeting
- Cash runway maintained above 12 months at all times (above 18 months preferred)
Scope & Limitations
In Scope: SaaS unit economics, burn rate analysis, financial modeling, cash management, investor reporting, month-end close, revenue recognition (ASC 606), due diligence preparation, scenario modeling.
Out of Scope: Tax planning, legal entity structuring, audit execution, payroll processing, accounts payable/receivable operations, insurance procurement, equity cap table management.
Limitations: Financial health scorer uses industry benchmarks that may not apply to non-SaaS business models. Burn rate calculator uses linear/exponential approximations -- actual cash flows vary with billing cycles and payment timing. Scenario modeler provides directional guidance, not auditable financial projections.
Integration Points
| Skill | Integration |
|---|---|
ceo-advisor |
Financial scenarios feed board strategy discussions |
board-deck-builder |
Financial update section; all deck numbers validated through CFO tools |
cro-advisor |
Revenue forecasting; pipeline-to-revenue conversion assumptions |
chro-advisor |
Headcount budget modeling; fully-loaded cost calculations |
ciso-advisor |
Compliance budget sizing against quantified risk exposure |
company-os |
Financial metrics in the weekly scorecard |
chief-of-staff |
Routes financial questions; synthesizes CFO + CEO perspectives |
How to use cfo-advisor on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add cfo-advisor
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches cfo-advisor from GitHub repository borghei/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate cfo-advisor. Access the skill through slash commands (e.g., /cfo-advisor) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★54 reviews- ★★★★★Shikha Mishra· Dec 24, 2024
cfo-advisor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Diya Gupta· Dec 20, 2024
Registry listing for cfo-advisor matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noor Thomas· Dec 4, 2024
cfo-advisor reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kwame Brown· Nov 23, 2024
I recommend cfo-advisor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Noah Nasser· Nov 11, 2024
Useful defaults in cfo-advisor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kaira Mehta· Oct 14, 2024
Useful defaults in cfo-advisor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Diya Desai· Oct 2, 2024
I recommend cfo-advisor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★William Mensah· Sep 25, 2024
We added cfo-advisor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chen Kapoor· Sep 17, 2024
Useful defaults in cfo-advisor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Taylor· Sep 13, 2024
I recommend cfo-advisor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 54