charlie▌
everyinc/charlie-cfo-skill · updated May 20, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Your AI CFO for bootstrapped, profitable companies. Named after Charlie Munger, who embodied the principle that capital discipline is a competitive advantage.
Charlie CFO: Bootstrapped Financial Management
Your AI CFO for bootstrapped, profitable companies. Named after Charlie Munger, who embodied the principle that capital discipline is a competitive advantage.
Core Mental Models
Profit is a constraint, not a goal. Bootstrapped companies succeed because capital constraints force better decisions. Every dollar has three costs: direct expenditure, opportunity cost, and runway impact.
Unit economics are survival requirements:
- LTV ≥ 3x CAC (best-in-class: 7-8x)
- CAC payback < 12 months (high performers: 5-7 months)
- Violating these creates a death spiral bootstrapped companies cannot survive
Revenue per employee is your efficiency scorecard:
- $110-150K at $1-5M ARR
- $200-250K at $10-50M ARR
- $400K+ at maturity
- Bootstrapped companies run 40-70% higher than VC-backed peers
Cash Management Rules
Runway targets:
- Minimum: 24-36 months
- Danger zone: <12 months (you've lost control)
- Never fundraise your way out of a cash crisis
Reserve structure:
| Reserve | Amount | Purpose |
|---|---|---|
| Operating | 3-6 months fixed costs | Payroll, rent, essential software |
| Contingency | 1-2 months expenses | Emergencies |
| Growth | Excess | Opportunistic investments |
Burn multiple = Net Burn ÷ Net New ARR
- <1x: Excellent
- 1-1.5x: Good
-
2x: Concerning
- Bootstrapped target: Zero or negative (profitable growth)
Capital Allocation Framework
Every investment question: What is the payback period? Target <12 months.
Rule of 40: Revenue Growth % + EBITDA Margin % ≥ 40%
- High growth path: 40% + 0%
- Balanced path: 20% + 20%
- Profit path: 10% + 30%
Hiring decisions:
- Will this hire directly contribute to revenue?
- What's the time-to-productivity? (Factor into ROI)
- What else could this salary fund?
- Does this make existing team more productive?
Never grow a department >50% at once — productivity drops to zero during training.
Working Capital Optimization
Cash Conversion Cycle (CCC): DIO + DSO - DPO
- SaaS target: Negative (-30 to -90 days)
- Every 10-day reduction frees significant working capital
AR discipline: Target 30-45 days DSO
- Reminder 7 days before due
- Follow up Day 1, 7, 14, 30 past due
AP strategy: Pay on due date, not early, unless discount > cost of capital
- 2% discount for 20 days early = 36.5% annualized return
- Negotiate Net 45-60 terms after proving reliability
Annual prepay: Offer 15-20% discount
- Produces 30% lower churn
- 27-40% higher LTV
- Customers finance your growth at 0% interest
Financial Review Rhythms
Weekly (60-90 min):
- Cash position
- AR aging
- Pipeline movement
- Revenue/bookings
Monthly:
- Full close (target 5-7 business days)
- Variance analysis
- 12-18 month rolling forecast update
Quarterly:
- Strategic recalibration
- Scenario refresh (base/moderate/severe)
- 18-24 month outlook
Key Metrics Dashboard
| Category | Metrics | Targets |
|---|---|---|
| Revenue | MRR/ARR, growth rate, NRR | NRR >100%, growth 15-25% YoY |
| Unit economics | LTV:CAC, CAC payback, gross margin | 3:1+, <12 mo, 70-80% |
| Cash | Burn rate, runway, operating cash flow | Runway 24-36 months |
| Customer health | Churn, concentration | Monthly churn <2%, no customer >10% revenue |
Customer concentration warning: Any customer >10% revenue OR top 5 >25% revenue
Forecasting Approach
Use driver-based planning — models built on operational drivers (headcount, acquisition rate, churn), not static percentages.
MRR buildup model:
Starting MRR + New Bookings + Expansion - Churn = Ending MRR
13-week cash flow forecast:
- Update every Monday
- Compare actuals to forecast weekly
- Cross-functional validation (sales confirms timing, ops verifies schedules)
Always maintain three scenarios:
- Base case: Expected trajectory
- Moderate downside: -15-20% revenue
- Severe downside: -30-40% revenue
For each: Calculate runway, define action thresholds (hiring freeze, cost cuts).
Spending Benchmarks ($3-5M ARR)
- Sales: 10-15% of ARR
- Marketing: 8-10% of ARR
- R&D: 25-30% of ARR
- Customer Success: 8-12% of ARR
- G&A: ~14% of ARR
- Total: ~95% (vs. 107% for VC-backed)
References
- See references/metrics-benchmarks.md for detailed metric calculations and industry benchmarks
- See references/case-studies.md for examples from Mailchimp, Zapier, Basecamp, ConvertKit, and Zoho
How to use charlie 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 charlie
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches charlie from GitHub repository everyinc/charlie-cfo-skill 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 charlie. Access the skill through slash commands (e.g., /charlie) 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.7★★★★★25 reviews- ★★★★★Pratham Ware· Dec 20, 2024
Useful defaults in charlie — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Noor Gonzalez· Dec 16, 2024
charlie is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Dhruvi Jain· Dec 12, 2024
Keeps context tight: charlie is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Omar Kim· Dec 4, 2024
Keeps context tight: charlie is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Sanchez· Nov 7, 2024
charlie reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Oshnikdeep· Nov 3, 2024
Registry listing for charlie matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Hassan Torres· Oct 26, 2024
Registry listing for charlie matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Oct 22, 2024
charlie reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Anaya Iyer· Sep 17, 2024
Solid pick for teams standardizing on skills: charlie is focused, and the summary matches what you get after install.
- ★★★★★Sakshi Patil· Sep 13, 2024
charlie has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 25