Try 10 Premium Prompts Free

You are an expert in email marketing and copywriting with 10 years of experience optimizing onboarding sequences. Write a welcome email for [COMPANY_NAME] targeting [TARGET_PERSONA] who just signed up for [OFFER_OR_LIST].

Use the AIDA framework (Attention, Interest, Desire, Action) and follow these constraints:
- Subject line: max 45 characters, create curiosity without clickbait
- Preheader: 85 characters max, complements the subject line
- Body: 150-200 words, tone [TONE: warm/professional/casual]
- Include a clear promise of what [TARGET_PERSONA] will get
- One single CTA focused on [DESIRED_ACTION]
- Human signature with first name of [SENDER_NAME], [POSITION]

End with a P.S. that creates anticipation for the next email.

You are a successful newsletter writer with expertise in storytelling and content marketing. Write a complete edition of the [NEWSLETTER_NAME] newsletter for [COMPANY_NAME], targeting [AUDIENCE].

Topic for this edition: [MAIN_TOPIC].

Use the enriched "3-2-1" format:
- Opening hook (3-5 lines): anecdote, surprising statistic, or provocative question related to [MAIN_TOPIC]
- Main section "The Deep Dive" (250-350 words): expert analysis of the topic, opinionated point of view, no platitudes
- 2 recommended resources (tool, article, book, or podcast) with 1-line explanation of why it's useful for [AUDIENCE]
- 1 concrete action to apply this week ("The Move of the Week")
- Personal closing (3 lines): [EDITORIAL_TONE], with a question to encourage replies

Constraints: [EDITORIAL_TONE] tone, total length 500-650 words, zero unnecessary jargon, one promo max in P.S. if needed.

You are a professional communication expert. Write an email with these parameters:

- Recipient: [NAME AND ROLE, e.g., "Marie Dupont, Marketing Director"]
- My relationship: [e.g., "client for 2 years", "new prospect", "direct manager"]
- Email objective: [e.g., "propose a meeting", "follow up on a quote", "announce a delay"]
- Key context: [IMPORTANT CONTEXT THE AI NEEDS TO KNOW]
- Desired tone: [formal / semi-formal / friendly / direct]
- Length: [short (5 lines) / medium (10 lines) / detailed]

Constraints:
- A compelling subject line (not generic)
- A clear call-to-action at the end
- No filler phrases like "I hope this email finds you well"
- Provide 2 versions: one concise and one more detailed

You are an expert in product launches and direct response copywriting, trained in Jeff Walker's methods and advanced conversion techniques. Write the official launch email for [PRODUCT_NAME] for [COMPANY_NAME].

Product context:
- Product: [PRODUCT_NAME]  — [PRODUCT_DESCRIPTION]
- Price: [PRICE] (regular value: [REGULAR_VALUE])
- Target audience: [IDEAL_CUSTOMER]
- Main transformation: [BEFORE_STATE] → [AFTER_STATE]
- Social proof: [KEY_TESTIMONIAL_OR_STAT]

Email structure:
1. Subject line (3 options: curiosity, benefit, urgency) + preheader
2. Opening: Personal story or customer story that illustrates the problem (4-5 lines)
3. Bridge: How you discovered the solution
4. Product reveal: What it is + 3 key benefits (not features)
5. Social proof block: Testimonial + numbers
6. Objection handler: Address the #1 hesitation
7. Offer stack: List everything included with perceived value
8. Scarcity/urgency: Real reason to act now (not fake countdown)
9. CTA: Clear, specific, benefit-oriented button text
10. P.S.: Reinforce the guarantee or top benefit

Total: 400-600 words. Every sentence must earn its place.

You are a senior executive assistant specialized in strategic note-taking. Here are the raw notes from my meeting:

---
[PASTE YOUR RAW NOTES HERE]
---

Participants: [LIST OF PARTICIPANTS AND THEIR ROLES]
Context: [MAIN MEETING TOPIC]

Generate a professional meeting summary with this exact structure:

## Executive Summary (3 lines max)
## Decisions Made (numbered list)
## Action Items
| Action | Owner | Deadline | Priority |
## Open Items
## Immediate Next Step

Rules: be factual, no interpretation. If information is missing, flag it with [TO CLARIFY].

You are a senior analyst specializing in document synthesis. Summarize the following document using the Minto Pyramid Principle:

Document: [PASTE TEXT OR DESCRIBE THE DOCUMENT]
Document type: [ANNUAL REPORT / MARKET STUDY / AUDIT / WHITE PAPER / OTHER]
Target audience for summary: [C-SUITE / TECHNICAL TEAM / CLIENT / OTHER]
Desired length: [1 PAGE / 3 PARAGRAPHS / 5 BULLET POINTS]

Structure your synthesis as follows:
1. **Key message** (1 impactful sentence summarizing the main conclusion)
2. **3 major arguments** supporting this message
3. **Essential quantified data** (extract the 5-7 most important KPIs)
4. **Attention points / risks** identified
5. **Recommended actions** with priority (high/medium/low)
6. **What's missing** in the document (gaps, absent data)

Use bullet points, bold critical elements, and flag any inconsistencies detected in the document.

You are an expert in design patterns (GoF, GRASP, enterprise patterns, cloud patterns). I have the following design problem:

**Context**: [TECHNICAL_CONTEXT_DESCRIPTION]
**Problem**: [PRECISE_PROBLEM_DESCRIPTION]
**Language/Framework**: [LANGUAGE_AND_FRAMEWORK]
**Constraints**: [PERFORMANCE_MAINTAINABILITY_TEAM_CONSTRAINTS]

Analyze my problem and recommend the appropriate pattern(s):

1. **Diagnosis**: Classify the problem (creational, structural, behavioral, concurrency, integration).
2. **Candidate patterns**: List 3 possible patterns, each with:
   - Name and category
   - Why it applies (matching forces)
   - Why it might not fit (weaknesses in this context)
   - Implementation complexity (1-5)
3. **Final recommendation**: The optimal pattern with detailed justification.
4. **Implementation**: Complete code of the chosen pattern adapted to my context, with:
   - ASCII UML diagram
   - Commented source code
   - Unit tests
   - Common pitfalls to avoid
5. **Alternatives**: If the problem evolves toward [POSSIBLE_EVOLUTION], which pattern to use instead.

You are a senior engineer specializing in debugging distributed systems. I have a complex bug affecting multiple services.

**Observed symptoms**:
- [SYMPTOM_1_WITH_FREQUENCY_AND_CONDITIONS]
- [SYMPTOM_2]
- [SYMPTOM_3]

**Architecture involved**:
- Services: [LIST_SERVICES_AND_THEIR_ROLES]
- Communication: [REST/gRPC/MESSAGE_QUEUE/EVENT_BUS]
- Databases: [DB_TYPES_AND_THEIR_ROLES]
- Infrastructure: [CLOUD/ON-PREM, ORCHESTRATION, LOAD_BALANCER]

**Already tried**: [LIST_OF_ATTEMPTED_FIXES]
**Available logs**: [PASTE_RELEVANT_LOG_EXCERPTS]

Conduct a systematic investigation:

1. **Triage**: Classify severity (P1-P4) and estimated blast radius
2. **Hypothesis tree**: Generate 5+ hypotheses ranked by probability, each with:
   - Description of the probable root cause
   - Which symptoms it explains (and which it doesn't)
   - Specific test to confirm or eliminate it
3. **Investigation plan**: Ordered steps with exact commands/queries to run
4. **Quick mitigations**: Temporary measures to reduce impact while investigating
5. **Root cause analysis**: Template for the post-mortem once resolved
6. **Prevention**: Monitoring/alerting to add to detect this class of issue earlier

Act as a senior business strategy consultant with 20 years of experience (McKinsey/BCG caliber). Build a complete, detailed Business Model Canvas for [COMPANY NAME], a [INDUSTRY] company offering [PRODUCT/SERVICE DESCRIPTION] targeting [PRIMARY CUSTOMER SEGMENT].

For each canvas block, provide:
1. **Customer Segments**: Identify 3-5 precise segments with demographic, psychographic, and behavioral characteristics. Indicate the priority segment and why.
2. **Value Propositions**: Formulate at least 2 unique value propositions (functional + emotional). Use the format "We help [WHO] to [DO WHAT] by [HOW] unlike [ALTERNATIVE]."
3. **Channels**: Detail acquisition, distribution, and communication channels. Rank by acquisition cost and estimated conversion rate.
4. **Customer Relationships**: Define the relationship type per segment (self-service, personal assistance, community, co-creation). Estimate the cost of service per customer.
5. **Revenue Streams**: List all possible revenue streams (subscription, transaction, license, commission, advertising). Estimate percentage distribution.
6. **Key Resources**: Identify critical physical, intellectual, human, and financial resources. Flag those constituting a defensible competitive advantage.
7. **Key Activities**: List the 5-7 critical activities that make the model work. Identify those that must remain in-house vs. outsourceable.
8. **Key Partners**: Identify strategic partnerships, critical suppliers, and necessary alliances. Assess dependency risk for each.
9. **Cost Structure**: Detail fixed and variable costs. Identify the main expense items and optimization levers.

Conclude with an overall canvas coherence analysis and 3 priority strategic recommendations.

Act as a Lean Startup methodology expert (Ash Maurya style). Create a complete Lean Canvas for [PROJECT NAME], a solution that solves [MAIN PROBLEM] for [TARGET USER] in the [SECTOR/MARKET] market.

Structure the canvas as follows:
1. **Problem**: List the 3 main problems your users face. For each, identify existing alternatives (direct and indirect competitors, workaround solutions).
2. **Customer Segments**: Define early adopters precisely (who are the people most desperate about this problem?). Give a detailed profile including segment size, accessibility, and willingness to pay.
3. **Unique Value Proposition (UVP)**: Write a single, clear, memorable sentence capturing why your solution is different and worth paying attention to. Format: "[End result] for [target] without [main friction]."
4. **Solution**: Describe the 3 minimum viable features that directly address each of the 3 listed problems. Stay minimalist.
5. **Channels**: Identify the 2-3 most effective free and paid channels to reach your early adopters. Estimate cost per lead.
6. **Key Metrics**: Define the 5 pirate metrics (AARRR) adapted to this project with quantified goals for the first 90 days.
7. **Unfair Advantage**: Identify what cannot be easily copied or bought (proprietary data, network, unique expertise, network effects).
8. **Cost Structure**: List fixed and variable costs for the first 6 months. Identify the break-even point.
9. **Revenue Streams**: Define the primary monetization model, target price, and estimated LTV.

Conclude with the 3 riskiest hypotheses to test first and propose a validation experiment for each (max 2 weeks duration, max [BUDGET] budget).