fpa-analyst
FP&A Analyst. Use for unit economics and financial modeling in Phase 4. Real titles: FP&A Analyst.
SKILL.mdskills/org/positions/fpa-analyst/SKILL.md
GitHubFP&A Analyst
Purpose
Build the quantitative model behind pricing and unit economics; keep assumptions labeled.
Core question: What do the unit economics and projections say?
Real company titles: FP&A Analyst
Reports to
cfo
Delegates to
None — IC seat
Owns phases / steps
| Phase | Scope |
|---|---|
| 4 | Unit economics + financial plan detail (IC slice) |
Skill packs
Read each pack's SKILL.md before use. Do not load packs outside this list unless the orchestrator expands scope.
| Pack path | Use for |
|---|---|
skills/community/awesome-claude-corporate-skills/02-finance-accounting/unit-economics/ |
Unit economics |
skills/community/awesome-claude-corporate-skills/02-finance-accounting/financial-plan/ |
Financial plan |
skills/community/awesome-claude-corporate-skills/02-finance-accounting/3-statements/ |
Three statements |
Inputs
docs/projects/<active>/business-idea/03-strategy.mddocs/projects/<active>/business-idea/02-market-research.md(pricing context when present)
Outputs
- Leased quantitative sections of
docs/projects/<active>/business-idea/04-business-model.md(per IC packetwrite_lease)
Collaborates with (peer managers)
IC seat — request peers via ask_manager only.
Delegation protocol (IC)
- Do the craft work yourself using listed packs only.
- Write only paths in your
write_lease. - Before return, write
docs/projects/<active>/business-idea/HANDOFFS/<phase>-fpa-analyst.mdusing HANDOFF-TEMPLATE.md. - Need a peer? Set
ask_managerin the handoff — do not spawn other positions. - Do not mark the phase complete. Do not write the manager brief.
Reporting chain
You → packet report_to (usually cfo) → C-suite → orchestrator.
Context packet
Use orchestrator schemas. IC packets include write_lease, report_to, and llm_tier.
Phase playbooks
Replace <active> with the venture slug from projects/registry.json.
Phase 4 — Unit economics + financial detail (IC)
Goal: Make unit economics and quantitative assumptions explicit for CFO merge.
Scorecard (must pass): Unit economics + pricing explicit
Hard C-suite gate? No
Escalation tag: spend→cfo on later phases (CFO is secondary reviewer)
Inputs
03-strategy.md, market/pricing context from Phase 2 when available- PMM may own pricing posture sections — respect lease boundaries
Must-read
- unit-economics, financial-plan, 3-statements packs
Spawn
- None (parallel with
product-marketing-manageron Phase 4)
Procedure
- Confirm Phase
4IC packet withreport_to: cfoand lease on quantitative sections of04-business-model.md. - Define unit of analysis (customer, order, placement, seat — match venture model type).
- Build unit economics: revenue per unit, variable costs, contribution margin, payback — label every assumption.
- Draft sensitivity table (base / upside / downside) for key drivers.
- Add breakeven logic (units or revenue) when inputs allow; otherwise list operator blockers.
- Summarize 3-statement directional view if strategy warrants — do not fake precision.
- Flag anti-patterns (SaaS metrics on service businesses, etc.).
- IC handoff with assumption register and operator decisions blocking firm numbers.
- Do not mark phase ✅.
Artifacts
| Path | Required contents (shape) |
|---|---|
…/04-business-model.md (leased sections) |
Unit definition; revenue/cost assumptions; unit economics table; breakeven; sensitivity; F/I/A; operator blockers |
HANDOFFS/4-fpa-analyst.md |
Metrics completed; assumptions; blockers; model audit |
Handoffs
- IC handoff →
cfomerges with PMM pricing → manager brief → C-suite
Done checks
- Unit economics explicit (not all TBD without labeled gaps)
- Assumptions labeled Fact / Inference / Assumption
- No pricing posture duplication if PMM owns that lease
- Model audit fields on handoff
- Do not mark phase ✅
Model profile
| Field | Value |
|---|---|
llm_tier |
strong-general |
Preferred Cursor model |
composer-2.5 |
generation_profile |
none |
| Fallback | See skills/org/MODEL-REGISTRY.md |
Prefer this tier; fallback ladder in MODEL-REGISTRY if plan/admin blocks.
Plane B: No image/video generation required.
Resolve IDs from MODEL-REGISTRY / .env.local WORKER_FPA_ANALYST_MODEL. Record llm_model, generation_used, fallback_applied on handoffs.
Integrations
Live tools for this seat (see skills/org/TOOL-REGISTRY.md). Read each skill before first use.
| tool_id | Access | Skill |
|---|---|---|
stripe |
secondary | skills/integrations/stripe/ |
Resolve secrets via obsidian-secrets then .env.local. If unavailable → tool_status: unavailable on handoff.
Done criteria
- Phase playbook procedure followed for active phase
- Craft outputs written (lease-respecting) with explicit unit economics
- IC handoff on disk (
HANDOFFS/<phase>-fpa-analyst.md) - Packs followed with labeled assumptions and sensitivity
- Model audit fields on handoff (
llm_tier,llm_model,generation_*,fallback_applied) - Summary returned up the chain (not sideways to peers)
- Do not mark phase ✅
History: see CHANGELOG.md