Most people use AI wrong. They type a vague question and get a vague answer. Then they blame the tool.
The problem isn't the AI. It's the prompt.
Bad Prompt vs. Good Prompt
Bad: "Write me a marketing email"
Good: "You are a B2B email copywriter specializing in SaaS companies. Write a cold outreach email to a VP of Engineering at a 200-person fintech company. The goal is to book a 15-minute discovery call about AI automation. Tone: direct, no fluff, one specific data point. Length: under 150 words. Include a PS with a relevant case study reference."
The output quality difference: 10x.
The 5-Layer Framework
Layer 1: Role
Tell the AI WHO it is.
- "You are a senior data analyst..."
- "You are a B2B copywriter with 10 years of experience..."
- "You are a Python developer who specializes in automation..."
Why it works: The role activates the most relevant knowledge and writing patterns. A "senior consultant" writes differently than a "junior copywriter."
Layer 2: Audience
Tell the AI WHO this is for.
- "...writing for marketing agency owners (15-50 employees)"
- "...explaining to a non-technical CEO"
- "...presenting to a board of directors"
Why it works: Audience determines vocabulary, depth, and assumptions.
Layer 3: Task
Tell the AI WHAT to produce.
Be specific about:
- Format (email, report, code, analysis)
- Length (150 words, 3 pages, 2000 tokens)
- Structure (bullet points, numbered list, sections with headers)
Layer 4: Constraints
Tell the AI the RULES.
- "No buzzwords"
- "Include at least 3 data points"
- "Tone: confident but not arrogant"
- "Must include a CTA"
- "Maximum 3 paragraphs"
Layer 5: Context
Give the AI BACKGROUND.
- Paste relevant data
- Include examples of what good looks like
- Reference previous work
- Provide industry-specific terminology
Real Examples
Marketing Email
Role: B2B email copywriter for SaaS companies
Audience: VP of Engineering at mid-market fintech (200-500 employees)
Task: Cold outreach email to book a 15-min discovery call about AI automation
Constraints: Under 150 words, one data point, direct tone, include PS
Context: Our automation saved a similar company 22 hrs/week. Their VP said
"I wish we'd started 6 months earlier."
Financial Report
Role: CFO-level financial analyst
Audience: Board of directors (non-technical)
Task: Quarterly AI investment ROI report, 2 pages max
Constraints: Include ROI percentage, payback period, comparison to industry
benchmarks. No technical jargon. Traffic-light status for each initiative.
Context: [paste quarterly data]
Code Review
Role: Senior Python developer with security expertise
Audience: Junior developer who wrote this code
Task: Code review with specific improvement suggestions
Constraints: Focus on security, performance, and readability.
Rate each area 1-5. Provide fixed code for any rating below 3.
Context: [paste code]
The Difference in Numbers
I tested 100 prompts with and without the 5-layer framework:
| Metric | Without Framework | With Framework |
|---|---|---|
| Usable on first try | 23% | 87% |
| Revision rounds needed | 3.2 | 0.4 |
| Time to final output | 12 min | 3 min |
| Client-ready quality | 15% | 72% |
535 Production-Ready Prompts
I've built a library of 535 prompts organized by business function:
- Sales (75 prompts)
- Marketing (75)
- Operations (75)
- Finance (50)
- HR (50)
- Legal (50)
- Customer Service (50)
- Strategy (50)
- Product (25)
- Custom templates (35)
Every prompt uses the 5-layer framework. Every one has been tested in real business contexts.
What's your biggest frustration with AI outputs? Drop it in the comments — I'll write you a 5-layer prompt for it.
Top comments (0)