Claude prompt for data analysis: Unit Economics (Workflow)
Claude · Data Analysis · Workflow
You are a hands-on practitioner using Claude for data analysis, specifically unit economics.
Job: contribution story.
Audience: finance. Constraint: assumptions listed.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
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.A strong Claude data analysis unit economics prompt names the job, audience, and finish line. This page does that for finance. Teams report saving 15–30 minutes per task when prompts include constraints up front. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
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
- Forces an output contract: headings, examples, and a final version.
- Names a clear job so Claude does not wander into generic advice.
- Repeats the hard constraint: assumptions listed.
- Uses operational language that matches how practitioners actually brief work.
- Asks for a self-check pass, which cuts hallucinated details.
How to use it in Claude
Save the winning variant for unit economics — teams with a short library ship faster. Queries, insights, charts, and decision memos. Keep that context in the thread when you iterate. Name the success metric aloud: contribution story. If the draft cannot pass it, do not polish prose yet. When finance review output, they should see step order, checkpoints, and handoffs without hunting for it. Ask for a shorter version after the long one; compression reveals weak claims.
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 Workflow 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-workflow when step order, checkpoints, and handoffs 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 Workflow prompt but editing it into a vague one-liner.
- Deleting "assumptions listed" to save space — that is usually the whole point.
Expert notes
Anthropic users working on unit economics in data analysis should treat "assumptions listed" as non-negotiable. Queries, insights, charts, and decision memos. When finance run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste assumptions listed as the first follow-up message — do not rewrite the whole prompt.
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
- Document what changed when you customized slug unit-economics-workflow.
- Claude improves when you paste a real snippet or reference still.
- Compare against other Claude angles on the same use case before you standardize.
- If text output drifts, re-anchor with assumptions listed.
- State the job (contribution story) in one line before any style talk.
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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for unit economics?
- Different angles solve different failures. Workflow helps when finance need step order, checkpoints, and handoffs. 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.