Browse All Prompts

Optimize freemium to paid conversion funnel. Tactics: 1. Identify 'aha moment' and drive users to it quickly. 2. Set usage limits that encourage upgrade (seats, features, volume). 3. In-app upgrade prompts at high-intent moments. 4. Email nurture campaign highlighting premium value. 5. Limited-time offers and discounts. 6. Sales-assisted conversions for high-value users. Analyze conversion rates by cohort and channel. A/B test pricing and packaging. Target 2-5% free-to-paid conversion rate. Measure time-to-convert and LTV by segment.

Design a comprehensive event tracking plan. Framework: 1. Define key user actions (signup, feature use, purchase). 2. Create event taxonomy (object-action naming). 3. Specify event properties (user ID, timestamp, context). 4. Map events to product metrics. 5. Document in tracking plan spreadsheet. 6. Implement with analytics SDK (Segment, Mixpanel). 7. QA and validate data accuracy. Include user properties for segmentation. Set up funnels and cohorts. Review and update quarterly as product evolves.

Create a clickable prototype from wireframes to high-fidelity. Process: 1. Start with low-fidelity sketches (paper or Balsamiq). 2. Create mid-fidelity wireframes in Figma (structure, layout). 3. Add content and copy (real, not lorem ipsum). 4. Apply design system (colors, typography, components). 5. Add interactions and transitions. 6. Build clickable prototype with user flows. 7. Conduct usability testing with 5-8 users. Iterate based on feedback. Use for stakeholder buy-in and developer handoff.

Measure and validate product-market fit. Indicators: 1. Sean Ellis test (% users 'very disappointed' if product disappeared >40%). 2. Retention cohorts (flattening curve after initial drop). 3. Organic growth rate (word-of-mouth, low CAC). 4. NPS score (>50 is excellent). 5. Sales cycle length (decreasing over time). 6. Customer feedback themes (solving real pain). Conduct surveys and analyze usage data. If PMF not achieved, pivot or iterate. Document assumptions and validate continuously.

Design a rigorous A/B test for product optimization. Process: 1. Define hypothesis (changing X will increase Y by Z%). 2. Choose primary and secondary metrics. 3. Calculate required sample size for statistical power. 4. Determine test duration (minimum 1 week, 2 business cycles). 5. Randomize users (50/50 split). 6. Implement tracking and QA. 7. Monitor for novelty effects and external factors. Analyze results with statistical significance testing. Document learnings. Iterate based on insights.

Apply Jobs-to-be-Done framework for product strategy. Structure: 1. Identify the 'job' customers are hiring your product for. 2. Map functional, emotional, and social dimensions. 3. Understand the 'struggling moment' that triggers the job. 4. Analyze competing solutions (including non-consumption). 5. Define success criteria from customer perspective. 6. Uncover unmet needs and innovation opportunities. Conduct switch interviews to understand why customers switched to/from your product. Use insights to guide product development.

Comprehensive product launch checklist across teams. Categories: 1. Product (feature complete, tested, documented). 2. Engineering (deployed, monitored, rollback plan). 3. Design (UI polished, onboarding flow). 4. Marketing (landing page, blog post, email campaign). 5. Sales (pitch deck, demo, pricing). 6. Support (help docs, FAQs, training). 7. Legal (terms updated, compliance). Timeline: 4 weeks pre-launch to 2 weeks post-launch. Assign owners and deadlines. Track in project management tool.

Create a detailed competitive feature comparison. Matrix structure: 1. List 5-7 key competitors (rows). 2. Define 15-20 critical features (columns). 3. Score each: ✓ (has), ✗ (missing), ⚠ (partial). 4. Add pricing tier for each feature. 5. Highlight your product's unique features. 6. Identify feature gaps and opportunities. Use color coding for visual clarity. Include market positioning insights. Update quarterly. Use for product strategy and sales enablement.

Build a comprehensive product metrics dashboard. Key metrics: 1. Acquisition (signups, activation rate). 2. Engagement (DAU/MAU, feature adoption). 3. Retention (cohort analysis, churn rate). 4. Revenue (MRR, ARPU, LTV). 5. Referral (viral coefficient, NPS). Use AARRR (Pirate Metrics) framework. Create separate views for different stakeholders. Include trend lines and targets. Set up automated alerts for anomalies. Use tools like Mixpanel, Amplitude, or custom SQL dashboards.

Design a comprehensive user research interview protocol. Structure: 1. Introduction and rapport building (5 min). 2. Background questions (user context, current workflow). 3. Behavioral questions (tell me about a time...). 4. Pain point exploration (what frustrates you?). 5. Solution validation (prototype feedback). 6. Wrap-up and thank you. Use open-ended questions. Avoid leading questions. Practice active listening. Record with permission. Aim for 30-45 min interviews. Synthesize findings into insights and themes.

Prioritize product features using RICE scoring. Methodology: 1. Reach (how many users affected per quarter). 2. Impact (how much it improves user experience, 0.25-3 scale). 3. Confidence (certainty in estimates, 0-100%). 4. Effort (person-months required). Calculate RICE score: (Reach × Impact × Confidence) / Effort. Rank features by score. Include qualitative factors (strategic fit, technical debt). Create prioritization matrix visualization. Involve cross-functional stakeholders in scoring.

Create a strategic product roadmap for the next 3 quarters. Framework: 1. Theme-based organization (not feature list). 2. Now/Next/Later timeline visualization. 3. Strategic initiatives aligned to company OKRs. 4. Customer impact and business value scoring. 5. Resource allocation and dependencies. 6. Success metrics for each initiative. Use tools like ProductPlan or Aha!. Balance innovation vs maintenance. Include stakeholder communication plan. Update monthly based on learnings.

Facilitate a user story mapping session for product planning. Process: 1. Define user personas and their goals. 2. Map user activities (horizontal backbone). 3. Break down activities into tasks (vertical stories). 4. Prioritize stories into releases (MVP, V2, V3). 5. Identify dependencies and risks. 6. Estimate effort and value. Use collaborative tools (Miro, Mural). Output: visual story map with clear release plan. Include acceptance criteria for each story. Align team on product vision and roadmap.

Conduct cloud infrastructure cost optimization. Analysis areas: 1. Right-sizing over-provisioned instances. 2. Reserved instances and savings plans. 3. Spot instances for non-critical workloads. 4. Unused resources (idle instances, unattached volumes). 5. Data transfer costs optimization. 6. Storage lifecycle policies. 7. Auto-scaling policies review. Use tools like AWS Cost Explorer, CloudHealth. Provide recommendations with estimated savings. Implement FinOps practices with cost allocation tags and budgets. Target 20-40% cost reduction.

Deploy Istio service mesh on Kubernetes. Features: 1. Automatic sidecar injection for traffic management. 2. Mutual TLS for service-to-service encryption. 3. Traffic routing (canary deployments, A/B testing). 4. Circuit breaking and retry policies. 5. Distributed tracing with Jaeger. 6. Service-level metrics and dashboards. 7. Ingress gateway for external traffic. Configure virtual services and destination rules. Use Kiali for visualization. Include performance impact analysis and troubleshooting guide.

Design a comprehensive database backup strategy. Components: 1. Automated daily full backups. 2. Incremental backups every 6 hours. 3. Point-in-time recovery capability. 4. Offsite backup storage (S3 Glacier). 5. Encryption at rest and in transit. 6. Backup verification and integrity checks. 7. Documented restore procedures with RTO/RPO. Test restore process monthly. Use tools like pg_dump, mysqldump, or cloud-native solutions. Include retention policies (7 daily, 4 weekly, 12 monthly).

Create a Jenkins declarative pipeline for Java application. Stages: 1. Checkout code from Git. 2. Build with Maven. 3. Run unit tests and code coverage (JaCoCo). 4. Static code analysis (SonarQube). 5. Build Docker image. 6. Push to container registry. 7. Deploy to Kubernetes. 8. Run smoke tests. Use parallel stages for efficiency. Implement pipeline as code (Jenkinsfile). Include credential management, artifact archiving, and email notifications on failure.

Implement HashiCorp Vault for secrets management. Configuration: 1. Initialize and unseal Vault cluster. 2. Enable authentication methods (AppRole, Kubernetes). 3. Create policies for least-privilege access. 4. Store secrets (database credentials, API keys). 5. Dynamic secrets for databases (auto-rotation). 6. Encryption as a service for sensitive data. 7. Audit logging for compliance. Integrate with CI/CD pipelines and applications. Use auto-unseal with cloud KMS. Include backup and disaster recovery procedures.

Configure Nginx as a high-performance reverse proxy. Features: 1. Load balancing across backend servers (round-robin, least-conn). 2. SSL/TLS termination with Let's Encrypt. 3. HTTP/2 and gzip compression. 4. Rate limiting and DDoS protection. 5. Caching static assets. 6. WebSocket support. 7. Custom error pages and logging. Include security headers (HSTS, CSP, X-Frame-Options). Use upstream health checks and failover. Optimize for 10k+ concurrent connections.

Build centralized logging with ELK stack (Elasticsearch, Logstash, Kibana). Pipeline: 1. Filebeat agents on application servers. 2. Logstash for log parsing and enrichment. 3. Elasticsearch cluster for storage and indexing. 4. Kibana for visualization and search. 5. Index lifecycle management for retention. 6. Alerting on error patterns. 7. Log correlation across services. Use structured logging (JSON). Include security (authentication, encryption) and performance tuning (sharding, replicas).

Implement GitOps workflow using ArgoCD. Setup: 1. Install ArgoCD on Kubernetes cluster. 2. Connect Git repository as source of truth. 3. Create Application manifests for each microservice. 4. Configure automated sync policies. 5. Set up health checks and sync waves. 6. Implement progressive delivery with Argo Rollouts (canary, blue-green). 7. RBAC for team access control. Use separate repos for app code and manifests. Include rollback procedures and disaster recovery plan.

Design a serverless application on AWS. Architecture: 1. API Gateway for HTTP endpoints. 2. Lambda functions for business logic (Node.js/Python). 3. DynamoDB for NoSQL storage. 4. S3 for file uploads with presigned URLs. 5. EventBridge for scheduled tasks. 6. SQS for async processing. 7. CloudWatch for logs and metrics. Use SAM or Serverless Framework for deployment. Implement proper error handling, retries, and dead-letter queues. Include cost optimization strategies (provisioned concurrency, reserved capacity).

Automate server provisioning with Ansible playbooks. Tasks: 1. Install and configure Nginx with SSL. 2. Set up firewall rules (UFW). 3. Configure automatic security updates. 4. Deploy application from Git repository. 5. Set up log rotation and monitoring agents. 6. Create system users with SSH keys. 7. Harden SSH configuration. Use roles for modularity, variables for environment-specific configs, and vault for secrets. Include inventory management and idempotency checks.

Optimize Docker images using multi-stage builds. Techniques: 1. Separate build and runtime stages. 2. Use slim base images (alpine, distroless). 3. Leverage layer caching with proper ordering. 4. Copy only necessary artifacts to final stage. 5. Use .dockerignore to exclude files. 6. Run as non-root user for security. 7. Scan for vulnerabilities with Trivy. Example for Node.js app: reduce image from 1GB to 150MB. Include CI integration and registry best practices.

Set up comprehensive monitoring with Prometheus and Grafana. Components: 1. Prometheus server with service discovery. 2. Node Exporter for system metrics. 3. Application instrumentation with custom metrics. 4. Alertmanager for notifications (PagerDuty, Slack). 5. Grafana dashboards for visualization (RED metrics, resource usage). 6. Recording rules for aggregations. 7. Alert rules for SLO violations. Use Docker Compose for local setup. Include retention policies and high-availability configuration.

Provision AWS infrastructure using Terraform. Resources to create: 1. VPC with public and private subnets across 3 AZs. 2. ECS Fargate cluster for containerized apps. 3. RDS PostgreSQL with Multi-AZ and automated backups. 4. Application Load Balancer with SSL certificate. 5. S3 bucket for static assets with CloudFront CDN. 6. IAM roles and security groups with least privilege. Use modules for reusability, remote state in S3, and workspaces for environments. Include cost estimation and tagging strategy.

Create production-ready Kubernetes manifests for a microservice. Resources: 1. Deployment with rolling update strategy and resource limits. 2. Service (ClusterIP) for internal communication. 3. Ingress with TLS termination. 4. ConfigMap for environment variables. 5. Secret for sensitive data. 6. HorizontalPodAutoscaler for auto-scaling. 7. PodDisruptionBudget for availability. Use namespaces, labels, and health checks (liveness/readiness probes). Include Helm chart structure for templating.

Build a production-grade CI/CD pipeline using GitHub Actions. Workflow: 1. Trigger on push to main and pull requests. 2. Run linting and unit tests in parallel. 3. Build Docker image with caching. 4. Run integration tests against test environment. 5. Deploy to staging on main branch merge. 6. Manual approval gate for production deployment. 7. Rollback mechanism on failure. Use secrets management, matrix builds for multiple Node versions, and status badges. Include deployment notifications to Slack.

Develop a comprehensive risk management framework. Process: 1. Risk identification (brainstorm all potential risks). 2. Risk assessment (probability × impact matrix). 3. Risk prioritization (high/medium/low). 4. Mitigation strategies (avoid, reduce, transfer, accept). 5. Contingency plans for top risks. 6. Risk owners and monitoring cadence. Categories to cover: market, financial, operational, technical, regulatory, reputational. Create risk register with status tracking. Update quarterly in leadership reviews.

Build an ROI calculator for B2B sales enablement. Inputs: 1. Current state costs (manual processes, errors, time). 2. Implementation costs (software, training, migration). 3. Expected benefits (time savings, error reduction, revenue increase). 4. Timeframe for realization. Outputs: 1. Total cost of ownership (TCO). 2. Net present value (NPV) with discount rate. 3. Payback period in months. 4. 3-year ROI percentage. Create interactive web calculator with shareable results. Include industry benchmarks for credibility.

Create a Lean Canvas for rapid business planning. Nine sections: 1. Problem (top 3 customer problems). 2. Customer Segments (target users). 3. Unique Value Proposition (single clear message). 4. Solution (top 3 features). 5. Channels (path to customers). 6. Revenue Streams (pricing model). 7. Cost Structure (key costs). 8. Key Metrics (measurable success). 9. Unfair Advantage (competitive moat). Fill out in 20 minutes. Iterate based on customer feedback. Use as living document for startup validation.

Conduct stakeholder analysis for change management. Framework: 1. Identify all stakeholders (internal and external). 2. Assess power/influence and interest levels. 3. Plot on 2x2 matrix (Manage Closely, Keep Satisfied, Keep Informed, Monitor). 4. Develop engagement strategy for each quadrant. 5. Create communication plan with frequency and channels. 6. Track sentiment and concerns over time. Use for product launches, org changes, or strategic initiatives. Include RACI matrix for decision-making clarity.

Calculate market size using TAM/SAM/SOM framework. Methodology: 1. TAM (Total Addressable Market) - top-down using industry reports. 2. SAM (Serviceable Addressable Market) - segment you can realistically target. 3. SOM (Serviceable Obtainable Market) - realistic market share in 3-5 years. Use multiple approaches: top-down (market research), bottom-up (unit economics), and value theory. Show calculations with clear assumptions. Visualize as nested circles or funnel. Include growth rate projections and market trends analysis.

Create a quarterly board meeting presentation. Agenda: 1. Executive Summary (highlights and lowlights). 2. Financial Performance (revenue, expenses, cash position). 3. Key Metrics Dashboard (growth, retention, efficiency). 4. Product Updates (launches, roadmap). 5. Go-to-Market Progress (pipeline, wins, losses). 6. Team and Culture (hiring, org changes). 7. Strategic Initiatives and Risks. 8. Ask of the Board (decisions needed). Keep to 20-30 slides. Use appendix for detailed data. Focus on trends and insights, not just numbers.

Develop a data-driven pricing strategy. Approaches to evaluate: 1. Cost-plus pricing (margin-based). 2. Value-based pricing (willingness to pay). 3. Competitive pricing (market benchmarking). 4. Freemium vs tiered models. 5. Usage-based vs flat-rate. Conduct price sensitivity analysis using Van Westendorp method. Test pricing with A/B experiments. Create pricing page with psychological anchoring. Include revenue impact projections for each strategy. Recommend optimal approach with rationale.

Facilitate a customer journey mapping workshop. Process: 1. Define persona and scenario. 2. Map stages (Awareness, Consideration, Purchase, Retention, Advocacy). 3. Identify touchpoints at each stage (website, email, support). 4. Document customer actions, thoughts, and emotions. 5. Highlight pain points and opportunities. 6. Assign ownership for improvements. Use collaborative tools (Miro, FigJam). Include pre-work template and post-workshop action plan. Deliver journey map as visual artifact.

Build a break-even analysis tool for business planning. Calculations: 1. Fixed costs (rent, salaries, software). 2. Variable costs per unit (COGS, commissions). 3. Price per unit and contribution margin. 4. Break-even point in units and revenue. 5. Margin of safety percentage. 6. Profit/loss at different volume scenarios. Create interactive calculator with charts showing break-even point visually. Include what-if analysis for pricing and cost changes. Provide interpretation guide for non-financial users.

Design a compelling 15-slide investor pitch deck. Slide sequence: 1. Cover (company name, tagline). 2. Problem (market pain point). 3. Solution (your product). 4. Market Opportunity (TAM/SAM/SOM). 5. Product Demo (screenshots/video). 6. Business Model (revenue streams). 7. Traction (growth metrics). 8. Competition (positioning). 9. Go-to-Market Strategy. 10. Team (founders and advisors). 11. Financials (3-year projections). 12. Funding Ask (use of funds). 13. Vision (long-term impact). Use clean design, minimal text, strong visuals.

Create a comprehensive Business Model Canvas. Nine building blocks: 1. Customer Segments (target personas). 2. Value Propositions (unique benefits). 3. Channels (distribution and sales). 4. Customer Relationships (acquisition and retention). 5. Revenue Streams (pricing models). 6. Key Resources (assets required). 7. Key Activities (core operations). 8. Key Partnerships (strategic alliances). 9. Cost Structure (fixed and variable costs). Use visual layout with sticky-note style. Validate each block with customer interviews.

Perform in-depth competitive analysis for market positioning. Research areas: 1. Competitor identification and categorization (direct, indirect, emerging). 2. Feature comparison matrix across 10+ dimensions. 3. Pricing strategy analysis (tiers, discounts, packaging). 4. Marketing positioning and messaging audit. 5. Customer review sentiment analysis. 6. Market share estimation and growth trends. Deliver actionable insights on differentiation opportunities and competitive gaps to exploit.

Design quarterly OKRs (Objectives and Key Results) for a product team. Structure: 1. Company-level objectives (3-5 ambitious goals). 2. Team-level objectives aligned to company goals. 3. Key Results for each objective (2-4 measurable outcomes). 4. Confidence scores and ownership assignments. 5. Weekly check-in template for progress tracking. Follow best practices: objectives are qualitative and inspiring, key results are quantitative and time-bound. Include grading rubric (0-1.0 scale).

Conduct a comprehensive SWOT analysis for strategic planning. Framework: 1. Strengths (internal capabilities and competitive advantages). 2. Weaknesses (internal limitations and gaps). 3. Opportunities (external market trends and growth areas). 4. Threats (competitive pressures and market risks). For each quadrant, provide 5-7 specific, actionable items. Create a 2x2 matrix visualization. Follow with strategic initiatives that leverage strengths and opportunities while addressing weaknesses and threats.

Build a 5-year financial projection model for Series A fundraising. Components: 1. Revenue forecast with multiple growth scenarios (conservative, base, aggressive). 2. Unit economics (CAC, LTV, payback period). 3. Operating expenses breakdown (headcount, marketing, infrastructure). 4. Cash flow statement and runway calculation. 5. Key metrics dashboard (burn rate, MRR growth, gross margin). Use Excel/Google Sheets with clear assumptions tab. Include sensitivity analysis for key variables.

Craft a persuasive executive business proposal. Structure: 1. Cover page with company logos and date. 2. Executive Summary (problem, solution, value in 1 page). 3. Situational Analysis (current state challenges). 4. Proposed Solution (detailed approach and deliverables). 5. Implementation Timeline (phases and milestones). 6. Investment and ROI Analysis. 7. Team and Credentials. 8. Terms and Next Steps. Use professional formatting with charts and visuals. Tailor language to C-suite audience.

Write helpful, human UX microcopy for common scenarios. Examples: 1. Form validation errors (specific, actionable). 2. Empty states (encouraging, with clear next steps). 3. Loading messages (reassuring, branded). 4. Success confirmations (celebratory but brief). 5. 404 pages (helpful navigation options). Follow principles: be clear, be concise, be human. Avoid technical jargon and blame. Provide solutions, not just problems. Include tone of voice guidelines for consistency.

Create comprehensive podcast show notes for SEO and listener value. Sections: 1. Episode title and number with guest name. 2. Brief summary (2-3 sentences). 3. Key takeaways (bulleted list). 4. Timestamped topics for easy navigation. 5. Guest bio and social links. 6. Resources mentioned in episode. 7. Transcript or key quotes. 8. Call-to-action (subscribe, review, join community). Optimize for search with episode keywords and long-tail phrases.

Write user-friendly changelog and release notes. Format: 1. Version number and release date. 2. Categorize changes (New Features, Improvements, Bug Fixes, Breaking Changes). 3. Use plain language, not technical jargon. 4. Link to relevant documentation or tutorials. 5. Acknowledge community contributors. 6. Migration guide for breaking changes. Follow Keep a Changelog format. Use emojis for visual scanning (✨ New, 🐛 Fix, ⚠️ Breaking). Keep entries concise and actionable.

Build a 30-day social media content calendar. Framework: 1. Content pillars (Educational 40%, Promotional 20%, Engagement 30%, Curated 10%). 2. Platform-specific formatting (Twitter: threads, LinkedIn: long-form, Instagram: carousel). 3. Hashtag strategy with branded and trending tags. 4. Posting schedule optimized by platform (best times). 5. Campaign themes tied to business goals. Include caption templates, visual guidelines, and performance tracking metrics. Batch-create content for efficiency.

Author an authoritative white paper for thought leadership. Outline: 1. Executive Summary (key findings in 1 page). 2. Introduction (industry context and research question). 3. Methodology (data sources, sample size, approach). 4. Findings (organized by themes with charts/graphs). 5. Analysis and Implications. 6. Recommendations and Best Practices. 7. Conclusion and Future Research. Use formal academic tone with citations. Length: 3000-5000 words. Include downloadable PDF design.

Draft a newsworthy press release for a product launch. Format: 1. Attention-grabbing headline (10-12 words). 2. Dateline and lead paragraph (who, what, when, where, why). 3. Quote from CEO or executive. 4. Supporting details and benefits. 5. Second quote from customer or partner. 6. Boilerplate company description. 7. Media contact information. Follow AP style. Keep to 400-500 words. Include multimedia assets note. Optimize for journalist pickup and wire distribution.