Claude prompt for data analysis: Unit Economics (Starter)
Claude · Data Analysis · Starter
You are a hands-on practitioner using Claude for data analysis, specifically unit economics.
Job: contribution story.
Audience: finance. Constraint: assumptions listed.
Working style: plain and encouraging. Optimize for first successful run with safe defaults.
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.Looking for a Claude prompt for unit economics? Start here — the starter angle focuses on first successful run with safe defaults. Teams report saving 15–30 minutes per task when prompts include constraints up front. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
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
- Asks for a self-check pass, which cuts hallucinated details.
- Repeats the hard constraint: assumptions listed.
- The starter angle adds first successful run with safe defaults without extra fluff.
- Names a clear job so Claude does not wander into generic advice.
- Centers contribution story so success is observable.
How to use it in Claude
Use plain and encouraging follow-ups only — mixing tones mid-thread confuses Anthropic models. Save the winning variant for unit economics — teams with a short library ship faster. Ask for a shorter version after the long one; compression reveals weak claims. Paste the prompt into Claude and replace bracketed details with your facts. If the first answer is vague, reply with the constraint again: assumptions listed.
Swap the audience once. If the unit economics piece still works, the core is solid. 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 Starter 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-starter when first successful run with safe defaults 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.
- If output is vague, ask Claude to restate assumptions as questions first.
- 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 Starter prompt but editing it into a vague one-liner.
- Deleting "assumptions listed" to save space — that is usually the whole point.
Expert notes
Slug unit-economics-starter: a analysts and operators-oriented data analysis brief. Queries, insights, charts, and decision memos. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if assumptions listed no longer matches policy.
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
- Ship a draft, then tighten. Do not chase a perfect first token.
- Data Analysis work needs queries, insights, charts, and decision memos.
- State the job (contribution story) in one line before any style talk.
- If text output drifts, re-anchor with assumptions listed.
- Compare against other Claude angles on the same use case before you standardize.
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 starter version stresses first successful run with safe defaults 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 starter angle for unit economics?
- Different angles solve different failures. Starter helps when finance need first successful run with safe defaults. 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.