Prompt Engineering Use Cases: Business, Creative & Technical

"Analyze the e-commerce market"

You are a market research analyst with 10 years of e-commerce experience.

Analyze the sustainable fashion e-commerce market for a startup entering the space.

Framework:
1. Market size and growth trajectory (2020-2025)
2. Key players and their market positioning
3. Customer segments and their purchasing behaviors
4. Barriers to entry and competitive advantages needed
5. White space opportunities

For each section:
- Cite specific data points where possible
- Identify 2-3 actionable insights
- Flag assumptions clearly

Output: Executive summary (200 words) + detailed analysis (800 words)
Target audience: Potential investors and founding team

Conduct a competitive analysis for [Your Company] vs. [Competitor].

Context:
- Our product: [Description]
- Our stage: [Series A, $2M ARR, 20 employees]
- Competitor: [Name, their positioning]

Analysis framework (for each company):

STRENGTHS
- Product capabilities (be specific about features)
- Market position and brand
- Financial resources
- Team and expertise

WEAKNESSES
- Product gaps or limitations
- Market vulnerabilities
- Resource constraints
- Execution risks

STRATEGIC IMPLICATIONS
- Where we can win
- Where we should avoid direct competition
- Partnership or acquisition opportunities

Output as comparison matrix with specific recommendations.

Help me decide: Should we build in-house or buy a third-party solution for [feature]?

Decision context:
- Budget: $50K one-time + $20K/year ongoing
- Timeline: Need deployed in 3 months
- Team: 2 engineers (both full-stack, no specific expertise in this area)
- Scale: 10K users today, 100K projected in 12 months

Analysis approach:
1. BUILD option: Estimate dev time, ongoing maintenance, opportunity cost
2. BUY option: Identify 3 top solutions, compare pricing/features, integration complexity
3. HYBRID: Any build-some-buy-some approaches worth considering?

For each option, provide:
- Total cost (12-month and 36-month view)
- Risk factors (technical, business, execution)
- Hidden costs or considerations
- Recommendation confidence level (low/medium/high)

Final recommendation with clear reasoning and key decision factors.

Write homepage hero section copy for [Product Name].

Product: AI-powered scheduling assistant for busy executives
Target: C-suite and VPs at companies with 500+ employees
Key differentiator: Learns preferences and handles complex multi-party scheduling

Psychological triggers to leverage:
- Time scarcity (executives value every minute)
- Status (premium positioning)
- Proven results (other executives use it)

Structure:
- Headline (8 words max, clear value prop)
- Subheadline (15 words, elaborates on unique benefit)
- 3 bullet points (specific outcomes, not features)
- CTA (action-oriented, specific)

Tone: Professional but conversational, confident not boastful
Avoid: Jargon, superlatives without proof, generic claims

Test 3 variations with different value prop angles.

Calculate ROI for implementing [Solution] at our company.

Current state:
- Manual process takes 10 hours/week per person
- 5 people performing this task
- Average fully-loaded cost: $75/hour
- Error rate: ~5% requiring 2 hours rework each

Proposed solution:
- Cost: $2,000/month subscription
- Setup: $5,000 one-time + 40 hours internal time
- Reduces manual time by 80%
- Reduces error rate to <1%

Calculate:
1. Current annual cost (labor + error rework)
2. Proposed annual cost (subscription + reduced labor + remaining errors)
3. First-year savings (including setup costs)
4. Breakeven point in months
5. 3-year total savings

For each calculation:
- Show your work step-by-step
- State assumptions explicitly
- Provide sensitivity analysis (what if adoption is only 60%? what if errors reduce by 60% not 80%?)

Format as financial memo suitable for CFO review.

"Write a story about a detective solving a murder"

Write the opening scene of a detective story with these elements:

Setting: Coastal town, off-season, perpetual fog
Protagonist: Retired detective, reluctantly pulled back for one last case
Tone: Noir meets magical realism (grounded but with subtle surreal elements)
Opening hook: A body that shouldn't exist (you decide what this means)

Constraints that free creativity:
- Start with sensory detail (what the detective smells, feels, hears)
- Introduce the central mystery through dialogue, not exposition
- Include one small surreal detail that hints at the story's unique angle
- End on a question that makes the reader need to know what happens next

Length: 500 words
POV: First person (detective's voice)

Don't explain everything. Create intrigue and atmosphere.

Develop a complex character for a screenplay.

Core concept: A successful defense attorney who secretly believes most of her clients are guilty

Develop through contradiction:
- What they show the world vs. what they hide
- Their justified rationalization vs. their 3 AM doubts
- Moments they almost break vs. what keeps them going

Create:
1. Defining moment from their past (why they became a defense attorney despite these beliefs)
2. Daily ritual that reveals inner conflict
3. The case/client that will break them (describe the moral dilemma)
4. Three dialogue snippets that reveal character through subtext (what they say vs. what they mean)

Focus on internal contradiction. That's where interesting characters live.
Make them morally complex, not good or evil.

Create a visual concept for [Brand] packaging redesign.

Brand essence: Organic skincare, science-backed, luxury positioning
Current problem: Packaging feels clinical, not aspirational
Target emotion: "Smart indulgence" - treating yourself wisely

Design direction exploration:

Generate 3 distinct concepts:

CONCEPT 1: Minimalist luxury
- Visual reference points (describe, don't just name styles)
- Color palette with psychological associations
- Materials and textures (sustainable options only)
- One unique design element that differentiates from competitors

CONCEPT 2: Botanical science
[Same structure]

CONCEPT 3: Modern apothecary
[Same structure]

For each concept:
- Describe the unboxing experience
- How it would look on a bathroom shelf (context matters)
- What Instagram moment it creates
- Potential manufacturing challenges

Choose your strongest concept and develop further.

Generate 10 blog post ideas for [Company Blog].

Audience: SaaS founders, Series A-B stage, 10-50 employees
Their challenges:
- Scaling team culture
- Moving from founder-led sales to sales team
- Balancing product development with customer demands
- Managing investor expectations

Content goals:
- Establish thought leadership
- Generate qualified leads
- Reduce support burden (answer common questions)

For each idea:
- Specific title (not generic)
- Hook angle (why they'll click)
- Key insight or framework (what makes it valuable)
- SEO keyword opportunity
- Lead magnet potential (could this become a downloadable guide?)

Criteria:
- Must provide actionable advice, not just inspiration
- Should leverage our specific expertise (we're in [your domain])
- Avoid topics overdone by competitors

Prioritize ideas by: search volume + uniqueness + actionability

"Write a function to validate emails"

Write a Python function to validate email addresses with these requirements:

SPECIFICATION:
- Function name: validate_email
- Input: string (email address)
- Output: tuple (is_valid: bool, error_message: str or None)
- Python version: 3.9+

VALIDATION RULES:
- Standard RFC 5322 format
- Additional business rules:
  * Reject disposable email domains (provide mechanism to update blocklist)
  * Reject emails with consecutive dots
  * Maximum length: 254 characters
  * Must have MX record (DNS verification)

REQUIREMENTS:
- Type hints for all parameters and returns
- Comprehensive docstring with examples
- Handle edge cases gracefully (None, empty string, whitespace)
- Log validation failures with reason (using Python logging)
- No external libraries except standard library + dnspython

DELIVERABLES:
1. Function implementation
2. Unit tests covering: valid emails, invalid formats, edge cases, MX verification
3. Brief explanation of regex choices and MX verification approach
4. Performance considerations for high-volume use

CODE STYLE: Follow PEP 8, use descriptive variable names

Review this code for production readiness:

[PASTE CODE]

Context:
- Language: TypeScript/Node.js
- Purpose: API endpoint for user authentication
- Traffic: ~1000 requests/minute peak
- Team: Junior developers maintaining this

Review dimensions:

SECURITY:
- Authentication/authorization vulnerabilities
- Input validation and sanitization
- Secrets management
- SQL injection or other injection risks

PERFORMANCE:
- Database query efficiency
- N+1 query problems
- Caching opportunities
- Memory leaks or resource cleanup

CODE QUALITY:
- Readability and maintainability
- Error handling completeness
- Logging and observability
- TypeScript type safety
- Testability

ARCHITECTURE:
- Separation of concerns
- Dependency injection opportunities
- Adherence to SOLID principles where applicable

For each issue found:
1. Severity: Critical/High/Medium/Low
2. Specific location (line numbers or function names)
3. Explanation of the problem
4. Suggested fix with code example
5. Why this matters in production

Prioritize findings by risk × impact.

Design a data pipeline architecture for this requirement:

REQUIREMENT:
Process clickstream data from mobile app for real-time analytics dashboard

SCALE:
- 100K active users
- ~50 events/user/day
- 5M events/day
- Real-time dashboard (<5 second latency from event to display)
- Historical analysis needed (90 days retention)

CONSTRAINTS:
- Budget: $2K/month AWS spend
- Team: 2 backend engineers, moderate cloud experience
- Timeline: MVP in 6 weeks

Propose architecture covering:

1. DATA INGESTION:
   - Event collection mechanism
   - Buffering/queuing strategy
   - Schema validation approach

2. PROCESSING:
   - Stream processing vs. batch
   - Aggregation strategy
   - State management

3. STORAGE:
   - Real-time data store (dashboard queries)
   - Historical data store (analysis)
   - Data retention and archival

4. SERVING:
   - API design for dashboard
   - Caching strategy
   - Query optimization

For each component:
- Specific AWS service recommendation with rationale
- Cost estimate
- Scaling considerations (what if we 10x this?)
- Operational complexity (can 2 engineers manage this?)
- Trade-offs made and alternatives considered

Include:
- System diagram (describe in text)
- Failure modes and mitigation
- Monitoring and alerting strategy

Help me debug this issue:

SYMPTOM:
API endpoint /users/:id returning 500 errors for ~10% of requests

CONTEXT:
- Started 2 days ago after deployment
- No code changes to this specific endpoint
- Database migration was part of deployment (added indexes)
- Only affects certain user IDs (no obvious pattern)

WHAT I'VE TRIED:
- Checked logs: "Database connection timeout" errors
- Monitored database: Connection pool at 95% capacity during errors
- Rolled back migration: Issue persists
- Restarted application servers: Temporary improvement, then returns

ENVIRONMENT:
- Node.js 18, PostgreSQL 14
- Connection pool: max 20 connections
- Average response time: 150ms (successful requests)
- Timeout response time: 30000ms (failing requests)

Help me:
1. Generate hypothesis list ranked by likelihood based on symptoms
2. For top 3 hypotheses, suggest specific diagnostic steps
3. Identify what additional data I should collect
4. Recommend immediate mitigation (reduce impact while we debug)
5. Suggest long-term preventive measures

For each hypothesis:
- Why this could cause the symptoms
- How to test this hypothesis
- Expected outcome if hypothesis is correct
- Fix if confirmed