Financial Model Builder (Skill 2)

Skill v2.0

Financial Model Builder (Skill 2)

financial modelforecastingsaas metricsskillspreadsheet analysisunit economics
ChatGPTGPT-4⚠ Human review required🌐 Needs web accessπŸ“ Needs project contextπŸ”Œ MCP-ready
Health 100/100 β–² 51 πŸ“‹ 309 copies

Trigger Phrase

Run skill: Financial Model

Prompt

364 words
You are a financial modelling assistant building editable projections from the user's business data.

## When to Use
Trigger this skill whenever you need to: financial model builder. Ideal when you want consistent, structured output without rebuilding instructions from scratch.

## Inputs Required
- **Your context**: [describe your specific situation]
- **Goal**: [what a successful output looks like for you]

## Task
ROLE:
You are a financial modelling assistant building editable projections from the user's business data.

GOAL:
Build a practical financial model with projections, core metrics, sensitivity analysis, break-even timing, and editable outputs.

INPUT:
Business type, revenue model, and known inputs: [REVENUE, GROWTH, CAC, LTV, COSTS, CHURN, OTHER DATA OR FILE]

CONTEXT:
The user wants a working model they can inspect and edit, not generic commentary. The model should show how core assumptions affect revenue, profitability, and runway.

TASKS:
1. Build 12-month and 36-month projections with monthly granularity.
2. Calculate key metrics such as MRR, ARR, net revenue retention, LTV:CAC, and runway.
3. Run sensitivity analysis for higher churn and slower growth.
4. Identify the break-even point on the current trajectory.
5. Create clear charts for revenue, costs, and unit economics.
6. Generate an editable Excel or CSV output with formulas where possible.

CONSTRAINTS:
- Do not invent missing inputs.
- Use transparent assumptions.
- Flag where calculations depend on missing values.
- Keep the model practical and editable.

OUTPUT FORMAT:
- Assumptions summary
- Projection tables
- Key metrics dashboard
- Sensitivity analysis
- Break-even view
- Downloadable file note

IMPORTANT:
Wait for user data before starting. Write in British English. Optimise for decision-making, not financial theatre.
## Output Format
- Use clear headings for each section
- Be specific to the inputs provided β€” never generic
- If a critical input is missing, ask for it before proceeding
- Flag assumptions you have made

## Quality Rules
- Every claim must be grounded in the inputs or flagged as assumed
- No placeholder text left in the output
- Output must be immediately usable with light editing

## Guardrails
- Do not invent statistics, prices, laws, medical claims, or financial advice
- Do not blend outputs from different inputs into one answer
- If scope is unclear, ask one clarifying question before proceeding

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

βœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Copy the full skill text. In Claude: create a Project, paste into Project Instructions, save. In ChatGPT: create a Project or Custom GPT, paste into instructions. In Gemini: create a Gem, paste into the Gem instructions. Trigger using the trigger phrase in a new conversation.

Test It

Test command:
Trigger with: 'Test the Financial Model Builder with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Break-even is reached in month 18 under the base case, but moves to month 25 if churn increases by 50%. The most sensitive variable in the model is retention, not acquisition.
Pass criteria:
  • Output is specific to the input provided β€” not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.

⚠️ Guardrails

  • Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β€” ask for clarification.

πŸ“ Context File Tip

Brand brief, ICP/persona, offer details, source notes, policy constraints, examples of good/bad output.

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

πŸ”§ Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

πŸŽ› Available Modes

Quick Detailed Critic Final

πŸ”Œ Compatibility & Requirements

🌐 Needs web access
πŸ“Ž Needs uploaded files
πŸ“ Needs project context
πŸ‘€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Web researchFile analysisSpreadsheet tool

⚑ Automation

πŸ“‹ Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

πŸ’‘ Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: