Browse All Prompts

Build autonomous agents with AutoGPT. Architecture: 1. Goal-oriented task decomposition. 2. Self-critique and iteration. 3. Memory management (short/long-term). 4. Tool usage (web search, file ops). 5. Code execution capability. 6. Human-in-loop checkpoints. 7. Budget constraints for API calls. 8. Plugin system for extensions. Agents plan and execute multi-step tasks independently.

Engage multiple stakeholders in target accounts. Multi-threading definition: relationships with 3+ people in buying org. Why: single-threaded deals stall when champion leaves or loses political battle. Strategy: 1. Map org chart (LinkedIn, ZoomInfo). 2. Identify 5-7 key stakeholders. 3. Assign custom approach per person. Example: Economic Buyer (exec briefing, ROI focus), Champions (detailed demos, frequent touch), End Users (hands-on trial, training resources). Tactics: ask champion for intros ('Who else should evaluate this?'). Attend prospect events/conferences. Engage on LinkedIn. Send personalized gifts. Track relationship depth (0=unaware, 1=aware, 2=engaged, 3=advocate). Safeguard deals: if 1 person goes dark, others keep deal alive.

Debug LLM applications with LangSmith. Features: 1. Trace every LLM call. 2. View chain execution steps. 3. Latency and token analysis. 4. Error tracking and debugging. 5. Dataset creation from logs. 6. Evaluation and testing. 7. Feedback collection. 8. Cost monitoring. Essential for production LLM apps. Use to identify bottlenecks and optimize prompts.

Build AI apps with Vercel AI SDK. Features: 1. useChat hook for chat UI. 2. useCompletion for text generation. 3. Streaming responses with React Server Components. 4. Edge functions for low latency. 5. Multiple provider support (OpenAI, Anthropic). 6. Route handlers for API. 7. Streaming JSON for structured data. 8. Automatic loading states. Use streamText and implement function calling.

Organize a formal debate on the topic: 'Should the Electoral College be abolished?' Structure: Lincoln-Douglas or team-based format. Teams: Affirmative (pro-abolition) and Negative (con-abolition). Roles: speakers, researchers, rebuttal planners. Timeline: 1. Research (1 week): Teams gather evidence and prepare arguments. 2. Constructive Speeches (8 mins each team): Present initial arguments. 3. Cross-Examination (3 mins after each speech): Opposing team asks clarifying questions. 4. Rebuttal Speeches (5 mins each team): Address and refute opponents' arguments. 5. Closing Statements (3 mins each team): Summarize key points. Assessment: rubric based on strength of argument, use of evidence, rebuttal effectiveness, and public speaking skills. Teacher acts as moderator.

Structure effective use of breakout rooms in a synchronous online class. Strategy: 'Jigsaw' Activity. 1. Main Session: Introduce a complex topic with 4 sub-topics. 2. Expert Groups (10 mins): Assign students to breakout rooms, with each room focusing on one sub-topic. They become 'experts' on that piece. 3. Jigsaw Groups (15 mins): Re-assign students to new breakout rooms, with one 'expert' from each of the original groups. Each expert teaches their sub-topic to the new group. 4. Main Session (5 mins): Return to the main room for a whole-class debrief and Q&A. Best Practices: assign roles in each group (facilitator, note-taker), provide a shared document (Google Doc/Jamboard) for collaboration, visit rooms to monitor progress.

Access multiple LLMs via OpenRouter. Benefits: 1. Single API for 50+ models. 2. Cost comparison across models. 3. Fallback to alternative models. 4. Real-time model availability. 5. Usage analytics dashboard. 6. OpenAI-compatible API. 7. Free models available. 8. Model routing based on performance. Switch models without code changes. Monitor costs and reliability.

Get structured data from LLMs with Instructor. Pattern: 1. Define Pydantic models for output. 2. Use instructor.patch() on OpenAI client. 3. LLM returns validated objects. 4. Automatic retry on validation errors. 5. Partial streaming for progressive updates. 6. Union types for multiple formats. 7. Nested models for complex data. 8. Field descriptions guide LLM. Type-safe LLM outputs. Use for data extraction and classification.

Win back lost opportunities. Lost deal classification: 1. Lost to competitor (know which one). 2. No decision/status quo. 3. Timing (not now). 4. Budget (couldn't afford). 5. Not a fit. Follow-up strategy by reason: Lost to competitor: Month 1: congratulate, stay in touch. Month 3: share customer win over that competitor. Month 6: 'How's it going with [competitor]?' Listen for dissatisfaction. No decision: Month 1: share new case study. Month 2: invite to webinar. Month 3: 'Checking in on [original pain point].' Timing: Month 3, 6, 9: 'Is now a better time?' Budget: Month 1: share ROI calculator. Quarter-end: 'We have flexibility this quarter.' Automation: add to nurture sequence in CRM. Personal touch: set reminder for rep to personally reach out quarterly. 10-20% of lost deals can be revived within 12 months. Track reactivation rate. Don't burn bridges.

Analyze images with GPT-4 Vision. Use cases: 1. Image description and captioning. 2. OCR and text extraction. 3. Object detection and counting. 4. Visual question answering. 5. Chart and graph interpretation. 6. UI/UX analysis. 7. Product identification. 8. Accessibility alt-text generation. Pass image URLs or base64. Combine with text for context-aware analysis.

Master Midjourney prompts for art. Techniques: 1. Descriptive subject and style. 2. Parameters (--ar, --v, --s, --q). 3. Multi-prompts with :: weights. 4. Image prompts for style reference. 5. Negative weights to exclude. 6. Chaos for variety. 7. Stylize for artistic interpretation. 8. Seeds for reproducibility. Use /imagine command and iterate with variations.

Create accurate user personas based on real customer data. Research methods: 1. User interviews (15-20 per segment): understand goals, frustrations, workflows. 2. Analytics analysis: usage patterns, feature adoption, churn triggers. 3. Support ticket analysis: common issues and requests. 4. Sales team insights: objections, competitive losses. Persona components: 1. Demographics: age, role, company size, location. 2. Goals: what they're trying to achieve (primary and secondary). 3. Pain points: current frustrations and blockers. 4. Behaviors: how they discover and evaluate solutions. 5. Quote: memorable statement capturing their mindset. Example: 'Sarah, Marketing Manager at 500-person SaaS company. Goal: prove marketing ROI to executives. Pain: too many tools, data scattered. Quote: I spend more time making reports than analyzing them.' Validation: test personas against new customer data quarterly. Use in product decisions: WWSD (What Would Sarah Do?).

Execute successful product launches with comprehensive checklist. Pre-launch (4 weeks): 1. Beta testing with select customers, gather feedback. 2. Documentation: user guides, FAQ, API docs if applicable. 3. Support training: brief customer success team on new features. 4. Marketing materials: landing pages, email campaigns, blog posts. 5. Analytics setup: tracking for new feature adoption. Launch week: 1. Feature flag rollout (gradual 1% → 10% → 50% → 100%). 2. Announcement email to existing users. 3. Social media posts with screenshots/videos. 4. Press outreach for major releases. 5. Monitor support channels for questions/issues. Post-launch (2 weeks): 1. Adoption metrics review. 2. User feedback collection and analysis. 3. Bug triage and hotfixes. 4. Success metrics evaluation vs. goals. 5. Retrospective with team on what worked/what didn't.

Systematically analyze competitors to inform product strategy. Analysis dimensions: 1. Core features (what they offer). 2. User experience (ease of use, design quality). 3. Pricing strategy (freemium, subscription, one-time). 4. Target market (enterprise vs. SMB vs. consumer). 5. Distribution channels (direct, partners, app stores). Research methods: 1. Hands-on product testing (sign up, use key features). 2. Review analysis (App Store, G2, TrustPilot). 3. Social listening (Reddit, Twitter mentions). 4. Traffic analysis (SimilarWeb, Ahrefs). 5. Job postings (what they're building). Deliverable: competitive matrix comparing features, pricing, strengths/weaknesses. Update quarterly. Strategic insights: identify white space opportunities, price positioning, feature gaps. Avoid copying directly; focus on customer jobs-to-be-done that competitors miss.

Segment images with SAM. Usage: 1. Load SAM model (ViT-B, ViT-L, ViT-H). 2. Input image and prompts (points, boxes). 3. Automatic mask generation. 4. Multiple object segmentation. 5. Interactive refinement. 6. Binary mask output. 7. Integration with labeling tools. 8. Fine-tuning for specific domains. Use for instance segmentation, background removal, or dataset creation.

Implement real-time detection with YOLO. Setup: 1. Choose YOLO version (v8, v9, v10). 2. Pre-trained COCO weights. 3. Inference on images/video. 4. Bounding box detection. 5. Class confidence scores. 6. Non-max suppression. 7. Custom dataset training. 8. Export to ONNX for deployment. Use Ultralytics library and implement tracking for video streams.

Personalize outbound emails efficiently. Research (2-3 mins per prospect): 1. Recent LinkedIn post or company news. 2. Mutual connections. 3. Technology they use (BuiltWith, SimilarWeb). 4. Recent job postings (indicates growth/pain). Personalization tiers: High-value accounts (custom per person): '[Name], saw your post about hiring 3 SDRs. Are you also scaling your sales tech stack?' Medium-value (templated with custom first line): 'Noticed [company] is using [tool]. How is that working for [specific pain point]?' Low-value (segment-based): '[Industry] companies typically face [challenge]. Curious if you're experiencing this?' Tools: Phantombuster for data enrichment, ChatGPT for variation generation, Instantly/Lemlist for sending. Batching: research 50 prospects, write custom lines, plug into sequence. Track: personalized emails get 3-5x reply rate vs generic. Test different personalization levels to find ROI sweet spot.

Conduct effective keyword research. Process: 1. Identify seed keywords for niche. 2. Use tools (Ahrefs, SEMrush, Google Keyword Planner). 3. Analyze search volume and difficulty. 4. Find long-tail opportunities. 5. Check competitor rankings. 6. Assess search intent (informational, transactional). 7. Group keywords into clusters. 8. Prioritize by ROI potential. Focus on relevance over volume. Target quick wins and long-term plays.

Optimize PPC campaigns for ROI. Strategy: 1. Keyword match types (exact, phrase, broad). 2. Negative keywords to reduce waste. 3. Ad group structure by theme. 4. Compelling ad copy with CTAs. 5. Landing page relevance and quality score. 6. Bid adjustments by device, location, time. 7. Ad extensions (sitelinks, callouts). 8. Conversion tracking and attribution. Use automated bidding strategies and A/B test ads continuously.

Develop optimal pricing strategy through research and testing. Pricing models: 1. Freemium: free tier + paid upgrades (good for viral/network effects). 2. Tiered: good/better/best packages (most common for SaaS). 3. Usage-based: pay per use/seat/transaction (aligns cost with value). 4. Flat rate: single price (simple but leaves money on table). Research methods: 1. Van Westendorp Price Sensitivity Meter (survey method). 2. Conjoint analysis: test feature/price combinations. 3. Competitor benchmarking: position relative to alternatives. 4. Customer interviews: value perception and willingness to pay. Testing approaches: 1. A/B testing: different prices to new customers. 2. Landing page tests: measure conversion at various price points. 3. Cohort analysis: retention by price paid. Optimization: raise prices annually for new customers, grandfather existing ones. Monitor churn rate changes after price increases.

Facilitate a low-tech makerspace project inspired by 'Caine's Arcade'. Challenge: 'Design and build an arcade game using only cardboard, recycled materials, and simple craft supplies.' Process (1 week): Day 1: Brainstorming and sketching game ideas. Day 2-3: Prototyping and building. Encourage iteration and problem-solving. Day 4: Peer testing and feedback. Students play each other's games and offer suggestions for improvement. Day 5: 'Arcade Day'. Invite another class to come play the games. Learning Objectives: engineering design process, creativity, collaboration, resilience (learning from failure). Connect to physics concepts like gravity and simple machines.

Master Facebook Ads targeting. Tactics: 1. Core audiences (demographics, interests, behaviors). 2. Custom audiences (website visitors, customer list). 3. Lookalike audiences from best customers. 4. Interest layering for precision. 5. Exclude converters to avoid waste. 6. Campaign Budget Optimization. 7. Creative testing with DCO. 8. Conversion API for accurate tracking. Use Advantage+ campaigns and implement retargeting funnels.

Build effective email automation. Workflows: 1. Welcome series for new subscribers. 2. Abandoned cart recovery. 3. Post-purchase follow-up. 4. Re-engagement for inactive users. 5. Birthday/anniversary campaigns. 6. Lead nurturing sequences. 7. Behavioral triggers based on actions. 8. Segmentation for personalization. Use ESPs like Klaviyo or Mailchimp. Monitor open rates, CTR, and conversions.

Shift from traditional to student-led conferences. Preparation: 1. Students compile a portfolio of their work (successes and challenges). 2. Students complete a self-reflection sheet on their progress, goals, and areas for improvement. 3. Students practice presenting their portfolio to peers. The Conference (20 mins): 1. Student welcomes parents and teacher. 2. Student presents their portfolio, explaining their work and learning process. 3. Student discusses their self-reflection and goals for the next quarter. 4. Parents and teacher ask questions and provide feedback. 5. All parties co-sign the goal-setting sheet. Benefits: increases student ownership and accountability, develops communication skills, provides parents with a more authentic view of their child's learning.

Develop content marketing strategy. Framework: 1. Audience personas and pain points. 2. Content pillars for expertise. 3. Editorial calendar with consistency. 4. SEO-optimized blog posts. 5. Internal linking structure. 6. Content upgrades and lead magnets. 7. Repurposing across channels. 8. Performance measurement and iteration. Focus on E-E-A-T. Aim for comprehensive, valuable content.

Create viral Instagram Reels. Formula: 1. Hook in first 1-2 seconds. 2. Trending audio for discovery. 3. Fast-paced editing. 4. Value-packed or entertaining. 5. Text overlays for sound-off viewing. 6. Clear CTA at end. 7. Hashtags (3-5 relevant). 8. Post timing for audience. Use vertical format and leverage carousel posts for longer content. Engage with comments quickly.

Measure and optimize product-led growth with key PLG metrics. Core PLG metrics: 1. Time-to-Value (TTV): speed of first meaningful experience. 2. Product Qualified Lead (PQL): user behavior indicating sales readiness. 3. Free-to-paid conversion rate: trial/freemium to paying customer. 4. Expansion revenue: upsells and seat expansion from existing accounts. 5. Viral coefficient: new users brought by existing users. Measurement framework: 1. Define activation milestone clearly (e.g., created first project). 2. Track user journey stages: signup → activation → habit formation → monetization. 3. Cohort analysis: retention and expansion over time. 4. Segmentation: analyze by traffic source, company size, use case. Growth levers: 1. Reduce friction in signup/trial. 2. Accelerate time-to-value. 3. Build in-product sharing/collaboration. 4. Usage-based upgrade prompts. Tools: Amplitude, Mixpanel for behavior tracking, ProfitWell for revenue metrics, Reforge for PLG benchmarks.

Run focused 5-day design sprints to solve big product challenges. Day 1 (Map): 1. Define long-term goal and sprint questions. 2. Map customer journey from start to finish. 3. Ask 'How Might We' questions and collect notes. 4. Target specific part of journey for sprint focus. Day 2 (Sketch): 1. Lightning demos of inspiring solutions. 2. Four-step sketching: notes, ideas, crazy 8s, solution sketch. Day 3 (Decide): 1. Present solution sketches anonymously. 2. Heat map voting and feedback. 3. Storyboard winning solution for prototype. Day 4 (Prototype): 1. Build realistic prototype (InVision, Figma). 2. Write realistic content, not lorem ipsum. Day 5 (Test): 1. 5 user interviews with prototype. 2. Document learnings and next steps. Team: 7 or fewer people, including decision maker. Outcome: validated or invalidated hypothesis with user evidence.

Design effective user onboarding to drive activation and retention. Onboarding success metrics: 1. Time-to-first-value (TTFV): how quickly users achieve core benefit. 2. Activation rate: percentage reaching 'aha moment'. 3. Day 1, 7, 30 retention: usage stickiness over time. Onboarding flow design: 1. Progressive disclosure: show features gradually, not all at once. 2. Interactive tutorials: hands-on vs. passive video watching. 3. Personalization: tailor experience to user role/use case. 4. Empty states: helpful content when users haven't added data yet. 5. Success celebrations: acknowledge user achievements. Optimization process: 1. Map current flow and identify drop-off points. 2. User testing: watch people go through onboarding. 3. A/B testing: test different approaches (tooltip vs. modal vs. guided tour). 4. Iterative improvements: make small changes, measure impact. Tools: Appcues, Pendo, WalkMe for guided experiences.

Systematically gather and analyze customer feedback for product insights. Collection channels: 1. In-app feedback widgets (Hotjar, UserVoice). 2. Post-interaction surveys (after support, purchase, feature use). 3. Regular customer interviews (monthly with different segments). 4. Feature request boards (public voting system). 5. Support ticket analysis (common themes and requests). 6. Social media monitoring (Twitter, Reddit mentions). Analysis framework: 1. Categorize feedback by theme (usability, feature requests, bugs). 2. Volume tracking: how often each issue appears. 3. Customer segment analysis: enterprise vs. SMB needs. 4. Urgency scoring: revenue impact + user frustration level. Tools: Airtable for tracking, sentiment analysis for social mentions, ProfitWell for cancellation reasons. Action loop: weekly feedback review → prioritization → roadmap updates → customer communication about fixes/features shipped.

Write comprehensive PRDs for complex product features. PRD structure: 1. Executive Summary (2-3 sentences): what you're building and why. 2. Problem Statement: user pain points with supporting data. 3. Success Metrics: how you'll measure success (leading and lagging indicators). 4. User Stories: core use cases with acceptance criteria. 5. Requirements: functional and non-functional (performance, security). 6. Design Mockups: wireframes or high-fidelity designs. 7. Technical Considerations: architecture, dependencies, risks. 8. Go-to-Market Plan: launch strategy and timeline. 9. Open Questions: items to resolve during development. Review process: stakeholder sign-off from engineering, design, marketing before development starts. Living document: update as requirements evolve, maintain change log. Tools: Confluence, Notion, Google Docs for collaboration. Template ensures nothing falls through cracks on complex projects.

Set and track Objectives and Key Results for product success. OKR structure: Objective (qualitative goal) + 3-5 Key Results (quantitative outcomes). Example: Objective: 'Improve user onboarding experience.' Key Results: 1. Increase DAU/MAU ratio from 15% to 25%. 2. Reduce time-to-first-value from 7 days to 3 days. 3. Achieve 70% completion rate for onboarding flow. Quarterly cycle: 1. Set OKRs at quarter start (team input + leadership alignment). 2. Weekly check-ins on progress. 3. Monthly OKR reviews with adjustments if needed. 4. Quarterly retrospective and grading (0-1.0 scale, 0.7 is good). Dashboard setup: automated tracking where possible, manual updates weekly. Leading vs. lagging indicators: track both activity metrics (features shipped) and outcome metrics (user satisfaction). Transparency: share OKRs across company for alignment.

Grow on TikTok strategically. Algorithm tactics: 1. Understand For You Page mechanics. 2. Complete video views matter most. 3. Watch time and rewatches. 4. Strong hook to prevent scrolling. 5. Trending sounds and effects. 6. Niche content for specific audience. 7. Posting frequency (1-3x daily). 8. Duets and stitches for engagement. Comment on your own video. Use analytics to identify best content types.

Generate B2B leads on LinkedIn. Strategy: 1. Optimize profile for searchability. 2. Content that demonstrates expertise. 3. Engage with target audience posts. 4. LinkedIn articles for thought leadership. 5. Video content for higher engagement. 6. Strategic connection requests. 7. InMail campaigns for outreach. 8. LinkedIn Ads for targeting. Use Sales Navigator for prospecting. Build relationships before pitching.

Qualify opportunities with MEDDIC. Metrics: quantifiable business impact ('20% faster processing'). Economic Buyer: identify and engage decision maker who controls budget. Decision Criteria: understand evaluation process, scoring matrix, must-haves. Decision Process: map timeline, stakeholders involved, approval steps. Identify Pain: technical and business pain points, implications if unsolved. Champion: find internal advocate who sells on your behalf. Score each element 0-10. Deals below 40/60 need more qualification. Update after every call. Forecast only MEDDIC-qualified deals. Prevents wasted time on unwinnable deals.

Optimize videos for YouTube search. SEO factors: 1. Keyword-rich titles (front-loaded). 2. Detailed descriptions (200+ words). 3. Tags (mix of broad and specific). 4. Custom thumbnails with text. 5. Closed captions and transcripts. 6. Cards and end screens. 7. Playlists for session time. 8. Engagement signals (likes, comments, shares). Use TubeBuddy or VidIQ. Focus on CTR and watch time.

Improve conversions with CRO. Testing framework: 1. Analyze user behavior (heatmaps, recordings). 2. Identify friction points. 3. Form hypothesis for improvement. 4. A/B test one variable at a time. 5. Statistical significance before conclusions. 6. Test headlines, CTAs, images, layouts. 7. Mobile vs desktop optimization. 8. Continuous iteration cycle. Use tools like Optimizely or VWO. Prioritize high-traffic pages.

Develop a school improvement plan based on data analysis. Data Sources: 1. Academic: standardized test scores, graduation rates, course failure rates. 2. Culture/Climate: student and staff survey results (e.g., Panorama), attendance data, discipline referrals. Process: 1. Data Dig: Leadership team analyzes data to identify 2-3 priority areas (e.g., '9th-grade math proficiency is low', 'student sense of belonging is declining'). 2. Root Cause Analysis: Use a 'Fishbone Diagram' to brainstorm potential causes for each problem. 3. Goal Setting: Create SMART goals for each priority area (e.g., 'Increase 9th-grade math proficiency by 10% by May'). 4. Action Plan: Define specific strategies, person responsible, timeline, and required resources. 5. Monitor Progress: Review progress toward goals at monthly leadership meetings.

Navigate executive assistants to reach decision makers. Mindset shift: EA is valuable ally, not obstacle. Respectful approaches: 1. Befriend EA: 'I'm trying to reach [Executive] about [specific topic]. Can you help me understand the best way to get on their calendar?' 2. Be specific: vague requests get blocked. 'I'd like 15 minutes to discuss [specific value prop].' 3. Provide context: 'We work with [similar companies] on [problem]. Is this something [Executive] handles?' 4. Ask for guidance: 'What's the best time/way to reach them?' 5. Reference trigger event: 'I saw [company news]. Wanted to discuss implications.' Alternative routes: LinkedIn message (EA may not monitor), attend industry events, mutual connection introduction. EA intelligence: ask EA about priorities, org changes, budget cycles. Send thank you note to EA. If stonewalled repeatedly: respect it, try different contact at company. Never antagonize EA - they control calendar and influence opinion.

Design high-converting landing pages. Best practices: 1. Single clear goal/CTA. 2. Attention-grabbing headline. 3. Compelling subheadline. 4. Hero image or video. 5. Benefits over features. 6. Social proof (testimonials, logos). 7. Urgency or scarcity elements. 8. Mobile-responsive design. Remove navigation to reduce exits. Use contrasting CTA buttons. Keep forms short.

Run successful influencer campaigns. Process: 1. Define goals and KPIs. 2. Identify relevant influencers (micro, macro, mega). 3. Vet for authentic engagement. 4. Negotiate terms and deliverables. 5. Provide creative freedom with guidelines. 6. Track with UTM links and promo codes. 7. Measure ROI (engagement, reach, conversions). 8. Build long-term relationships. Use platforms like AspireIQ. Focus on brand alignment.

Build repeatable referral system. Best timing: 1. After successful implementation. 2. After positive review/NPS score. 3. During quarterly business review. The ask: 'I'm glad you're seeing results. Who else in your network faces similar challenges?' Be specific: 'Do you know any [job title] at [company size] in [industry]?' Offer value exchange: refer them clients too, provide introduction template, offer referee incentive (Amazon gift card, discount). Process: 1. Identify top 20 happy customers. 2. Reach out personally (not bulk email). 3. Make ask easy ('Just reply with 2-3 names and I'll handle outreach'). 4. Send update when contact is made. 5. Report results back to referrer. Track referral source in CRM. Calculate referral conversion rate (typically 30-50% higher than cold). Incentivize reps: SPIF for most referrals monthly.

Launch affiliate marketing program. Setup: 1. Choose platform (Impact, ShareASale, custom). 2. Define commission structure. 3. Create affiliate resources (links, banners). 4. Recruit affiliates in niche. 5. Provide promotional materials. 6. Track conversions and payouts. 7. Communicate regularly with affiliates. 8. Optimize based on performance. Set clear terms and conditions. Incentivize top performers.

Build viral referral programs. Mechanics: 1. Dual-sided incentives (referrer + referee). 2. Easy sharing mechanisms. 3. Trackable referral links. 4. In-product prompts at key moments. 5. Email campaigns to encourage sharing. 6. Gamification with tiers or leaderboards. 7. Social proof of referral success. 8. Fraud detection. Use tools like Viral Loops or ReferralCandy. Make rewarding feel instant.

Balance new features with technical debt reduction effectively. Technical debt assessment: 1. Code quality metrics: cyclomatic complexity, test coverage, duplication. 2. Performance impact: page load times, API response times. 3. Developer productivity: time to implement new features. 4. Bug frequency: hotfixes and customer-impacting issues. 5. Security vulnerabilities: outdated dependencies, known exploits. Debt categorization: 1. Critical: security issues, major performance problems (fix immediately). 2. Important: impacts developer velocity significantly (plan in next sprint). 3. Nice-to-have: code cleanliness, minor optimizations (backlog). Resource allocation: allocate 15-25% of development capacity to debt reduction. Stakeholder communication: explain debt in business terms (slower features, more bugs, security risk). Tools: SonarQube for code analysis, New Relic for performance monitoring. Prevent future debt: code reviews, architecture decisions documentation, regular refactoring.

Plan a Tier 2 reading intervention for a small group of 3rd graders. Target Skill: Reading fluency. Group Size: 4-5 students. Frequency: 3 times a week for 30 minutes. Structure: 1. Warm-up (5 mins): Practice sight words with flashcards. 2. Modeling (5 mins): Teacher models fluent reading of a short, instructional-level passage, emphasizing prosody and pacing. 3. Choral Reading (5 mins): Teacher and students read the passage aloud together. 4. Partner Reading (10 mins): Students take turns reading the passage to a partner. Teacher provides feedback. 5. Progress Monitoring (5 mins): Once a week, conduct a 1-minute timed reading of a new passage to track words correct per minute (WCPM). Graph progress to show growth. Intervention should be systematic and data-driven.

Design a 1-hour workshop for parents of early elementary students. Agenda: 1. Welcome & Icebreaker (10 mins): 'Share a favorite book from your childhood.' 2. The Science of Reading (15 mins): Briefly explain the importance of phonics and phonemic awareness in a parent-friendly way. 3. Practical Strategies (20 mins): Model simple, fun activities parents can do at home. (e.g., 'I Spy' with letter sounds, using magnetic letters on the fridge, asking 'who, what, where, why' questions during read-alouds). 4. Resource Share (10 mins): Provide a handout with recommended book lists, websites (e.g., Starfall), and local library information. 5. Q&A (5 mins). Provide childcare and snacks to increase attendance. Offer in multiple languages if possible.

Execute impactful product launches. Campaign phases: 1. Pre-launch (teasers, waitlist). 2. Launch day (coordinated announcements). 3. Post-launch (sustained momentum). 4. Multi-channel approach (email, social, PR). 5. Influencer and partner activation. 6. Limited-time offers for urgency. 7. Product demo content. 8. Collect and showcase early reviews. Use Product Hunt for tech products. Create FOMO.

Define strong brand positioning. Framework: 1. Target audience identification. 2. Competitor analysis and differentiation. 3. Unique value proposition. 4. Brand personality and voice. 5. Key messaging pillars. 6. Visual identity alignment. 7. Positioning statement. 8. Consistency across touchpoints. Use perceptual mapping. Focus on specific niche. Own a word in customer's mind.

Equip sales team with competitive intelligence. Battlecard structure per competitor: 1. Company overview (size, funding, target market). 2. Strengths (what they do well, when they win). 3. Weaknesses (gaps, common complaints). 4. Differentiation (why you win against them). 5. Objection traps (questions to ask that expose weaknesses). 6. Proof points (case studies where you won against them). 7. Pricing comparison. Research sources: G2 reviews, Reddit discussions, sales calls (ask 'who else are you evaluating?'), competitor websites, former employees. Update quarterly. Make easily accessible (Wiki, PDF with search). Train reps on delivery: never bash competitor, focus on your strengths. Landmine questions: 'How important is [feature they lack] to you?'