Prompt Library
A comprehensive collection of tested, ready-to-use prompts organized by role and function. Copy, customize, and deploy these templates to accelerate your work.
How to Use This Library
- Find the prompt category that matches your need
- Copy the template
- Customize by replacing [bracketed] placeholders with your specifics
- Paste into Schatzi AI and send
- Refine based on results
- Save successful variations for reuse
Building Your Personal Library
As you use and refine these templates, save your best versions in a dedicated document or note-taking app for quick access.
CEO / Executive Prompts
Strategic Analysis
You are a Swiss business strategy consultant.
Analyze [situation/market/opportunity/threat] for a Swiss [industry] company.
Context:
- Company size: [employees/revenue]
- Current position: [market description]
- Key challenge: [specific challenge]
- Strategic goal: [objective]
Provide:
1. Situation assessment (SWOT if relevant)
2. Strategic options (3-5 alternatives)
3. Recommendation with rationale
4. Implementation considerations
5. Risk factors
Format: Executive summary + detailed analysis
Length: 2-3 pages
Tone: Strategic, data-driven, actionable
Board Report Preparation
Create an executive board report from these materials.
[Upload: Financial data, operational metrics, strategic initiative updates]
Board Composition: [e.g., 5 members, mix of financial and industry expertise]
Meeting Focus: [Quarterly review / Strategic decision / Crisis update]
Report Structure:
1. Executive Summary (half page - key messages only)
2. Financial Performance (1 page)
3. Operational Highlights (1 page)
4. Strategic Initiatives Progress (1 page)
5. Key Decisions Required (half page)
6. Forward Look & Risks (half page)
Tone: Professional, balanced, decision-oriented
Length: 4-5 pages maximum
Include: Specific metrics, year-over-year comparisons, vs-budget analysis
Market Opportunity Assessment
Evaluate this market opportunity for Swiss market entry/expansion.
Opportunity: [Description]
Market: [Geographic/segment details]
Our capabilities: [Strengths and resources]
Timeline consideration: [Urgency/constraints]
Analysis needed:
1. Market size and growth potential
2. Competitive landscape
3. Entry barriers and requirements
4. Resource requirements (capital, team, time)
5. Risk assessment
6. Go/No-Go recommendation
Include:
- Financial projections (high-level)
- Critical success factors
- Key assumptions
- Decision timeline
Format: Strategic memo, 3 pages
Audience: Executive team
CFO / Finance Prompts
Financial Variance Analysis
You are a Swiss financial analyst.
Analyze financial variances from budget/forecast.
[Attach: P&L statement, budget comparison, prior period data]
Focus on variances >10% in:
- Revenue by line
- Operating expenses by category
- Gross margin and operating margin
- Cash flow components
For each significant variance:
1. Amount and percentage deviation
2. Likely root cause
3. Whether recurring or one-time
4. Action required (if any)
5. Impact on full-year forecast
Format: Executive summary + detailed variance table + commentary
Highlight items requiring immediate management attention.
Cash Flow Forecasting
Create a 90-day cash flow forecast.
[Attach: Current cash position, AR aging, AP schedule, payroll calendar]
Assumptions:
- Collection patterns: [historical average or specific timing]
- Payment terms: [AP payment policy]
- Planned capex: [major purchases planned]
- Seasonal factors: [if applicable]
Produce:
1. Weekly cash flow projection (12 weeks)
2. Minimum cash balance date and amount
3. Financing needs (if any)
4. Risk factors to monitor
5. Recommendations for cash management
Format: Weekly projection table + executive summary + risk assessment
Budget Preparation Support
Help prepare annual budget for [Department/Function].
Historical data: [Attach prior 2-3 years]
Strategic initiatives: [New programs/changes planned]
Constraints: [Budget limitations, headcount freeze, etc.]
Create:
1. Department budget template
2. Line-item explanations
3. Year-over-year variance analysis
4. Strategic initiative costings
5. Sensitivity analysis (best/base/worst scenarios)
Organize by:
- Personnel costs
- Operating expenses
- Capital expenditures
- Revenue/income (if applicable)
Swiss context: Include social charges, VAT, typical Swiss business costs
Asset Manager / Wealth Management Prompts
Portfolio Risk Screening
You are a Swiss wealth management risk analyst.
Screen this portfolio for concentration and ESG risks.
[Attach: Portfolio holdings CSV with: security, asset class, sector, geography, %portfolio, ESG rating]
Analyze:
1. Concentration Risks:
- Single position >10%
- Sector >25%
- Geography >40%
- Currency exposure
2. ESG Risks:
- Holdings with ESG rating below B
- Controversial industries
- Carbon-intensive exposures
- Regulatory risks
3. Compliance Check:
- Swiss institutional guidelines
- Client mandate restrictions
- Diversification requirements
For each risk:
- Flag: High / Medium / Low
- Specific recommendation
- Target remediation
Market Commentary Draft
Draft weekly market commentary for private banking clients.
Target audience: Conservative Swiss wealth management clients
Focus: [Swiss equities / Global balanced / Fixed income / Multi-asset]
Tone: Professional, reassuring, educational
This week's key developments:
- [Market movement 1]
- [Economic data 2]
- [Policy development 3]
Structure:
1. Market Summary (one paragraph - what happened)
2. What It Means (two paragraphs - interpretation and implications)
3. Portfolio Positioning (one paragraph - how we're positioned)
4. Outlook (one paragraph - forward view)
Length: 400-500 words
Avoid: Jargon, excessive optimism/pessimism, market timing predictions
Include: Specific data points (index levels, yields, FX rates)
HR / People Operations Prompts
Job Description Creation
Create a job description for [Position Title].
Company: [Industry, size, location]
Department: [Team/function]
Reports to: [Role]
Team size: [Direct reports if applicable]
Role purpose: [Why this position exists]
Key responsibilities: [3-5 main duties]
Required qualifications: [Education, experience, skills]
Preferred qualifications: [Nice-to-haves]
Include:
- Role overview (2-3 sentences)
- Key responsibilities (5-7 bullets)
- Required qualifications
- Preferred qualifications
- What we offer (benefits, culture, growth)
- Swiss employment context (work permit requirements if relevant)
Tone: Professional, appealing, clear
Length: 1 page
Format: Standard job posting structure
Performance Review Preparation
Help prepare performance review for [Employee Name/Role].
Review period: [Dates]
Employee role: [Title and main responsibilities]
Performance data:
- Goals set: [List or attach]
- Achievements: [Key accomplishments]
- Challenges: [Areas of difficulty]
- Peer feedback: [Summary if available]
- Metrics: [Quantitative performance data]
Create:
1. Performance summary (overall assessment)
2. Goals achievement review (each goal individually)
3. Strengths demonstrated
4. Areas for development
5. Goals for next period
6. Development plan recommendations
Tone: Constructive, balanced, specific
Focus: Behavior and results, not personality
Include: Specific examples for each point
Sales / Business Development Prompts
Prospect Research Brief
Create a prospect research brief for sales meeting.
Prospect: [Company name]
Industry: [Sector]
Meeting with: [Contact name and title]
Our solution: [What we're selling]
Meeting objective: [Discovery / Demo / Proposal / Close]
Research and provide:
1. Company overview (size, structure, recent news)
2. Industry context and challenges
3. Likely pain points our solution addresses
4. Competitive landscape (who they might use now)
5. Key talking points for meeting
6. Potential objections and responses
7. Questions to ask in discovery
Format: One-page brief for quick pre-meeting review
Include: Conversation starters, recent company news to reference
Proposal Follow-up Email
Draft follow-up email after proposal submission.
Proposal: [Brief description]
Submitted: [Date]
Decision maker: [Name and title]
Relationship: [New prospect / Existing relationship / Warm intro]
Proposal value: [Amount]
Next step: [What we want - meeting, decision, clarification]
Email should:
- Reference proposal briefly
- Provide value (not just "checking in")
- Suggest specific next action
- Include soft deadline
- Maintain professional but warm tone
Length: 100-150 words
Tone: Helpful, professional, not pushy
Include: Clear call-to-action
Legal / Compliance Prompts
Contract Clause Drafting
Draft a [type of clause] for Swiss law contract.
Contract type: [NDA / Service Agreement / Partnership / etc.]
Parties: [Describe parties]
Jurisdiction: Swiss law
Specific requirements: [What clause must accomplish]
Draft clause covering:
- [Specific requirement 1]
- [Specific requirement 2]
- [Specific requirement 3]
Swiss law compliance:
- FADP requirements (if data processing involved)
- Swiss contract law principles
- Industry-specific regulations [if applicable]
Provide:
1. Draft clause text
2. Explanation of key provisions
3. Optional variations (if choices to be made)
4. Related clauses that should be included
Note: This is a draft for review by qualified legal counsel.
Regulatory Update Summary
Summarize this regulatory change for affected stakeholders.
[Attach: Regulation text, official announcement, analysis]
Regulation: [Name and reference]
Effective date: [Date]
Affected parties: [Who in our organization]
Industry: [Sector]
Create summary covering:
1. What changed (key provisions)
2. Who is affected and how
3. Compliance requirements
4. Implementation timeline
5. Action items by department
6. Risks of non-compliance
7. Recommended next steps
Format: Memo for distribution to management
Length: 2 pages
Tone: Clear, authoritative, actionable
Include: Specific deadlines and requirements
IT / Technology Prompts
Technical Documentation
Create user documentation for [system/feature/process].
Target audience: [End users / Administrators / Developers]
Technical level: [Non-technical / Moderate / Advanced]
System: [Name and purpose]
Document should cover:
- Purpose and overview
- Step-by-step instructions
- Screenshots description (where to take them)
- Troubleshooting common issues
- FAQs
- Support contact information
Format: [User guide / Quick reference / Technical manual]
Style: Clear, concise, jargon-free (or with explanations)
Include: Examples, warnings, tips
System Incident Report
Create incident report for [system/service] outage.
Incident: [Brief description]
Date/Time: [When it occurred]
Duration: [How long]
Impact: [Systems/users affected]
Root cause: [What caused it - if known]
Resolution: [How it was fixed]
Report should include:
1. Executive Summary (what happened, impact, resolution)
2. Timeline (chronological events)
3. Root Cause Analysis
4. Impact Assessment (users affected, business impact)
5. Resolution Steps Taken
6. Preventive Measures (how to avoid recurrence)
7. Action Items with owners and deadlines
Audience: [IT management / Executives / All staff]
Format: Professional incident report
Tone: Factual, accountable, forward-looking
Marketing / Communications Prompts
Social Media Content Series
Create a 5-post social media series about [topic/product/service].
Platform: [LinkedIn / Instagram / Twitter / Facebook]
Brand voice: [Professional / Friendly / Educational / Inspirational]
Target audience: [Demographics and interests]
Campaign goal: [Awareness / Engagement / Lead generation]
Swiss context: [Multilingual if needed, local references]
For each post create:
1. Main copy (appropriate length for platform)
2. Hashtag recommendations (5-7 relevant tags)
3. Call-to-action
4. Image/visual suggestion
5. Posting time recommendation
Tone: [Specify brand voice guidelines]
Format: Ready to post (no editing needed)
Include: Engagement hooks, questions, value-add content
Press Release Draft
Draft press release for [announcement/news].
Company: [Name and brief description]
News: [What you're announcing]
Significance: [Why it matters]
Quote source: [Who will be quoted - name and title]
Target media: [Swiss business press / Tech media / General news / etc.]
Press release structure:
1. Headline (attention-grabbing, newsworthy)
2. Subheadline (additional context)
3. Dateline and lead paragraph (who, what, when, where, why)
4. Body paragraphs (details, context, significance)
5. Quote from company leader
6. Background paragraph (about the company)
7. Contact information
Length: 400-600 words
Tone: Newsworthy, factual, professional
Swiss context: Available in [DE/FR/IT/EN] if needed
Operations / Project Management Prompts
Project Status Report
Create weekly project status report.
Project: [Name]
Project manager: [Name]
Phase: [Current phase]
Report week: [Date range]
Data to include:
- Milestones achieved this week
- Upcoming milestones
- Budget status
- Resource utilization
- Risks and issues
- Decisions needed
Format:
1. Overall Status (Red/Yellow/Green with brief explanation)
2. Progress This Week (accomplishments)
3. Planned Next Week (commitments)
4. Issues & Risks (current blockers and concerns)
5. Decisions Required (from stakeholders)
6. Metrics Dashboard (schedule, budget, quality)
Audience: [Steering committee / Sponsor / Team / All stakeholders]
Length: 1-2 pages
Tone: Factual, transparent, solution-oriented
Process Documentation
Document this business process: [Process name]
Process purpose: [What it accomplishes]
Frequency: [How often it occurs]
Owner: [Role responsible]
Participants: [Who is involved]
Document should include:
1. Process Overview (purpose and scope)
2. Inputs (what's needed to start)
3. Step-by-Step Procedure (detailed steps)
4. Decision Points (where choices are made)
5. Outputs (what the process produces)
6. Quality Checks (how to verify correctness)
7. Exception Handling (what to do when things go wrong)
8. Metrics (how to measure effectiveness)
Format: Process documentation standard
Style: Clear, sequential, actionable
Include: Flowchart description, roles matrix, form templates needed
Cross-Functional Prompts
Meeting Agenda Creation
Create meeting agenda for [meeting type/purpose].
Meeting: [Title]
Date/Time: [When]
Duration: [Length]
Attendees: [Roles, number]
Objective: [What needs to be accomplished]
Previous context: [Relevant background]
Agenda should include:
1. Meeting objective (stated clearly)
2. Agenda items (with time allocations)
3. Pre-work required (if any)
4. Materials needed
5. Expected outcomes
6. Parking lot (for off-agenda items)
Format: Professional meeting agenda
Include: Time management, clear ownership of topics
Ensure: Adequate time for discussion, decisions, and action items
Multilingual Translation
Translate this [document type] into [target language(s)].
[Paste or upload content]
Source language: [Original language]
Target language(s): [German (Swiss) / French (Swiss) / Italian / English]
Document type: [Email / Letter / Report / Marketing / Website / etc.]
Tone: [Professional / Friendly / Formal / Casual]
Requirements:
- Culturally appropriate for Swiss [German/French/Italian] audience
- Industry terminology for [sector] correctly translated
- Maintain tone and intent of original
- Flag any idioms or phrases that don't translate well
- Provide alternatives for culturally-specific references
For each target language, provide:
1. Full translation
2. Notes on any translation choices made
3. Alternative phrasings (if applicable)
Using This Library Effectively
Customization Best Practices
1. Replace ALL Placeholders
- Don't leave [brackets] in your prompts
- Fill in every detail requested
- Add context beyond minimum requirements
2. Adapt to Your Situation
- Modify tone for your brand
- Adjust length requirements
- Add industry-specific context
3. Refine Based on Results
- If output is too generic, add more context
- If output is too long, specify tighter length
- If missing key points, list them explicitly
Building Your Organization's Library
1. Create Shared Repository
- Centralized location (Notion, Confluence, SharePoint)
- Organized by department and function
- Include examples of good outputs
2. Version Control
- Date your templates
- Note what was changed and why
- Keep version history
3. Share Learnings
- What prompts work best for different models
- Which phrasings get better results
- Common pitfalls to avoid
4. Regular Review
- Update templates as AI models improve
- Incorporate new use cases
- Remove outdated approaches
Contributing Your Prompts
Have a prompt that works incredibly well? We'd love to add it to the library!
To contribute:
- Use the prompt successfully multiple times
- Document the context and results
- Generalize it (remove company-specific details)
- Submit to: support@schatziai.ch
Your contribution helps the entire Swiss Schatzi AI community!
Related Resources
- Prompt Engineering Guide: Learn the principles behind effective prompts
- Industry-Specific Prompts: Deep-dive templates by industry
- Sample Workflows: See these prompts in action
Download This Library
Bookmark this page or save it offline for quick reference. These templates are designed to be copied and customized for your daily work.