Claude prompt for data analysis: Unit Economics (Advanced)
Claude · Data Analysis · Advanced
You are a hands-on practitioner using Claude for data analysis, specifically unit economics.
Job: contribution story.
Audience: finance. Constraint: assumptions listed.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Claude data analysis template when finance need unit economics with the rule: assumptions listed. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
For Anthropic models, data analysis prompts fail when they mix strategy and execution. This unit economics brief separates the job so you can iterate once, not ten times. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Centers contribution story so success is observable.
- Locks the audience (finance) before style so tone stays honest.
- Asks for a self-check pass, which cuts hallucinated details.
- Uses precise and demanding language that matches how practitioners actually brief work.
- Names a clear job so Claude does not wander into generic advice.
How to use it in Claude
For data analysis work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Queries, insights, charts, and decision memos. Keep that context in the thread when you iterate. Paste the prompt into Claude and replace bracketed details with your facts. Save the winning variant for unit economics — teams with a short library ship faster. Name the success metric aloud: contribution story. If the draft cannot pass it, do not polish prose yet.
Have Claude list assumptions about data analysis before drafting. Delete any you cannot defend. For unit economics in data analysis, the failure mode is usually missing constraint. This prompt blocks that by design — especially "assumptions listed". Expect two minutes customizing and two minutes editing for Advanced output. Anthropic models still need your facts for unit economics; they cannot invent metrics or brand rules. analysts and operators teams bookmark slug unit-economics-advanced when constraints, evaluation, and edge cases matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (finance, offer, timeline).
- Confirm the constraint is still visible: assumptions listed.
- For data analysis work, paste a rubric and ask for a self-score.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Unit Economics, 3 short sections, bullet list of recommendations, closing line that states assumptions listed. Facts you supply appear; nothing invented.
Common mistakes
- Ignoring the output contract headings.
- Using the Advanced prompt but editing it into a vague one-liner.
- Deleting "assumptions listed" to save space — that is usually the whole point.
Expert notes
Practitioners choose Advanced when unit economics needs constraints, evaluation, and edge cases. Claude from Anthropic still needs your facts — especially for assumptions listed.
For data analysis, compare this Advanced prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on contribution story.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a unit economics piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Claude improves when you paste a real snippet or reference still.
- State the job (contribution story) in one line before any style talk.
- Data Analysis work needs queries, insights, charts, and decision memos.
- Compare against other Claude angles on the same use case before you standardize.
- The Advanced variant is for constraints, evaluation, and edge cases.
FAQ
- What is a Claude prompt for unit economics?
- It is a structured brief that tells Claude how to produce data analysis output for finance. This advanced version stresses constraints, evaluation, and edge cases and keeps "assumptions listed" in the instructions.
- How do I customize this Claude data analysis prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "assumptions listed" should stay unless your brief truly changed.
- Why use the advanced angle for unit economics?
- Different angles solve different failures. Advanced helps when finance need constraints, evaluation, and edge cases. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.