Working entrepreneurs who need investor update emails drafted fast. Copy these prompts into ChatGPT, fill in your variables, and get professional updates ready to send in under a minute.
These prompts pair well with Jasper AI for Entrepreneurs-specific tone control, or Copy.ai for fast iteration.
Monthly Performance Updates
You are a startup founder writing a monthly investor update email.
Company: {company_name} Month/Quarter: {time_period} Revenue this period: {revenue_figure} Revenue growth: {growth_percentage} Key metrics: {metric_1}: {value_1}, {metric_2}: {value_2}, {metric_3}: {value_3} Major wins: {three_wins_bullet_format} Current challenges: {two_challenges} Team updates: {hiring_or_departures} Cash runway: {months_remaining} Next month priorities: {three_priorities}
Write a 400 to 500 word investor update email. Start with a one-sentence summary of the month. Present metrics in a clean format. Frame challenges as problems you’re solving, not failures. Close with specific asks if you need investor help.
When to use it: Every month-end when you’re sending regular updates to your investor group and need to present mixed results professionally.
Pro tip: Always lead with your strongest metric, even if it’s not revenue. Investor attention drops after the first paragraph.
You are a SaaS founder writing a quarterly investor update focused on strong growth.
Company: {company_name} Quarter: {q1_q2_q3_q4} {year} ARR: {annual_recurring_revenue} Net revenue retention: {nrr_percentage} Customer count: {total_customers} New enterprise deals: {number_of_deals} Product milestones: {two_product_achievements} Team size: {current_headcount} Burn rate: {monthly_burn} Runway: {months_cash_remaining} Market opportunity update: {market_insight}
Write a 350 to 450 word update email that celebrates growth while staying credible. Open with the headline numbers. Include one forward-looking statement about market opportunity. Keep the tone confident but not overconfident.
When to use it: After a strong quarter when you want to reinforce investor confidence and potentially set up conversations about next fundraising.
Pro tip: Include one small concern or challenge even in good updates. Pure positivity makes sophisticated investors suspicious.
You are a hardware startup founder updating investors after a difficult manufacturing month.
Company: {company_name} Manufacturing issue: {specific_problem} Impact on delivery: {delay_timeline} Units produced this month: {actual_vs_target} Resolution plan: {three_step_action_plan} Additional costs: {cost_impact} Customer communication status: {how_customers_informed} Supply chain changes: {vendor_or_process_changes} Revised timeline: {new_delivery_date} Cash impact: {runway_change}
Write a 300 to 400 word update that addresses the manufacturing setback directly. Lead with accountability, not excuses. Detail your resolution plan with specific dates. End with reassurance about long-term trajectory.
When to use it: When manufacturing delays or quality issues force you to reset expectations with investors.
Pro tip: Give investors the bad news first, then the plan. Never bury manufacturing problems in the middle of updates.
You are an early-stage founder writing your first investor update after closing seed funding.
Company: {company_name} Funding amount: {round_size} Lead investor: {lead_investor_name} Months since funding: {time_since_close} Initial traction: {early_customer_or_revenue_metric} Team hires: {new_team_members_and_roles} Product development: {development_milestones} Early customer feedback: {key_insight_from_customers} Burn rate: {monthly_spending} Runway: {months_remaining} Next quarter goals: {three_specific_objectives}
Write a 250 to 350 word update email that shows momentum without overpromising. Focus on early execution and learning. Keep the tone enthusiastic but grounded. Include specific metrics even if they’re small.
When to use it: 30 to 90 days after seed funding when investors want to see initial execution on your fundraising promises.
Pro tip: Early updates should emphasize learning and iteration speed over absolute numbers. Investors expect small metrics but fast progress.
You are a B2B marketplace founder updating investors on a pivot decision.
Company: {company_name} Original model: {previous_business_model} Pivot decision: {new_direction} Data that drove pivot: {key_metrics_or_insights} Customer research findings: {validation_for_new_direction} Timeline for transition: {pivot_timeline} Resource requirements: {team_or_technology_needs} Impact on runway: {cash_implications} Early validation: {initial_traction_new_model} Risk mitigation: {backup_plan}
Write a 400 to 500 word email explaining the pivot with confidence. Lead with the business case, not the struggle. Show this is strategic, not reactive. Include early validation of the new direction and clear timeline.
When to use it: When you’ve made a significant business model change and need to maintain investor confidence through the transition.
Pro tip: Frame pivots as “capturing a bigger opportunity” rather than “fixing what didn’t work.” Same facts, better narrative.
Milestone and Achievement Updates
You are a fintech founder announcing a major partnership to investors.
Company: {company_name} Partner: {partner_company_name} Partnership type: {integration_distribution_or_joint_venture} Revenue impact: {expected_revenue_or_customer_growth} Timeline to launch: {go_live_date} Integration requirements: {technical_or_resource_needs} Market access: {new_customer_segment_or_geography} Competitive advantage: {how_this_differentiates_you} Implementation team: {who_is_leading_internally} Success metrics: {how_you_will_measure_success}
Write a 250 to 300 word announcement email that conveys the partnership’s significance without overselling. Lead with the business impact. Include concrete next steps and timeline. Keep the tone professional and factual.
When to use it: Within 48 hours of signing a significant partnership that materially impacts your business trajectory.
Pro tip: Focus on revenue or customer impact, not brand recognition. Investors care about business outcomes, not logo collecting.
You are a consumer app founder updating investors on viral growth.
App: {app_name} Growth trigger: {what_caused_viral_moment} User growth: {new_users_this_week} Total users: {current_user_base} Engagement metrics: {daily_active_users_or_retention_rate} Revenue impact: {monetization_during_growth} Infrastructure scaling: {technical_challenges_overcome} Marketing spend: {organic_vs_paid_breakdown} Sustainability plan: {how_you_will_maintain_growth} Next phase strategy: {capitalizing_on_momentum}
Write a 350 to 400 word update that captures excitement while acknowledging the challenge of sustaining viral growth. Include specific engagement metrics. Address scalability and long-term retention strategy.
When to use it: During unexpected viral growth when investors need context on sustainability and your plan to capitalize.
Pro tip: Viral moments are temporary. Investors want to see your plan for converting viral users into engaged, retained customers.
You are a deep-tech founder announcing successful pilot program completion.
Company: {company_name} Pilot partner: {customer_company_name} Pilot duration: {timeline} Success metrics achieved: {quantified_outcomes} Cost savings delivered: {dollar_amount_or_percentage} Performance vs benchmarks: {comparison_to_existing_solutions} Customer feedback: {key_quote_or_insight} Commercial terms negotiated: {contract_value_or_structure} Expansion opportunity: {additional_use_cases_or_departments} Next customer pipeline: {other_prospects_interested}
Write a 300 to 400 word email that demonstrates commercial viability. Lead with quantified customer outcomes. Include direct customer feedback. Close with pipeline implications for scaling.
When to use it: After completing a paid pilot that validates your technology’s commercial value and sets up larger contract discussions.
Pro tip: Include the customer’s internal success metrics, not just your technology’s performance. Investors want proof of business value.
You are a marketplace founder updating investors on crossing a key liquidity threshold.
Marketplace: {platform_name} Liquidity milestone: {specific_metric_achieved} Supply side growth: {seller_merchant_or_provider_count} Demand side growth: {buyer_or_user_count} Transaction volume: {gmv_or_transaction_count} Take rate: {marketplace_commission_percentage} Network effects evidence: {how_growth_accelerates_growth} Market penetration: {percentage_of_addressable_market} Competitive position: {advantage_over_alternatives} Expansion plans: {new_categories_or_geographies}
Write a 350 to 450 word email explaining why this milestone matters for marketplace dynamics. Focus on network effects and competitive moats. Include data showing accelerating growth patterns.
When to use it: When your two-sided marketplace hits the inflection point where network effects drive organic growth acceleration.
Pro tip: Show how each new participant makes the platform more valuable for existing users. That’s the network effect investors want to see.
You are a biotech founder announcing positive trial results to investors.
Company: {company_name} Trial phase: {phase_1_2_or_3} Patient count: {participants_in_trial} Primary endpoint: {main_success_metric} Results summary: {efficacy_outcome} Safety profile: {adverse_events_summary} Statistical significance: {p_value_or_confidence_interval} Regulatory pathway: {next_fda_steps} Timeline to next milestone: {regulatory_timeline} Commercialization impact: {market_opportunity_validation}
Write a 400 to 500 word announcement that balances scientific rigor with business implications. Lead with clinical significance. Include regulatory context. Address commercial timeline and market opportunity.
When to use it: Within 24 hours of receiving positive clinical trial data that advances your regulatory timeline.
Pro tip: Always include the regulatory pathway and timeline. Biotech investors need to understand the path to commercialization, not just efficacy.
Challenge and Recovery Updates
You are a startup founder addressing a significant customer churn event.
Company: {company_name} Churn event: {what_happened} Customers lost: {number_or_percentage} Revenue impact: {monthly_or_annual_revenue_lost} Root cause analysis: {underlying_problem_identified} Immediate actions taken: {crisis_response_steps} Process improvements: {systemic_changes_implemented} Customer retention plan: {proactive_measures_for_remaining_customers} Recovery timeline: {when_you_expect_stabilization} Learning integration: {how_this_prevents_future_churn}
Write a 350 to 400 word email that takes ownership of the churn event and demonstrates learning. Lead with accountability. Detail your systematic response. Show how this makes you stronger long-term.
When to use it: When you lose multiple customers due to product issues, service problems, or competitive pressure and need to address investor concerns.
Pro tip: Frame customer churn as expensive but valuable learning. Investors respect founders who extract maximum insight from setbacks.
You are a founder addressing a key team member departure.
Company: {company_name} Departing team member: {person_role_not_name} Departure reason: {why_they_are_leaving} Business impact: {projects_or_relationships_affected} Transition plan: {knowledge_transfer_timeline} Replacement strategy: {internal_promotion_or_external_hire} Interim coverage: {who_handles_responsibilities} Retention review: {actions_to_prevent_future_departures} Culture assessment: {team_morale_check} Timeline to stability: {when_replacement_will_be_effective}
Write a 250 to 350 word email that addresses the departure professionally. Avoid personal details. Focus on business continuity and organizational learning. Show proactive retention thinking.
When to use it: When a co-founder, key engineer, or critical team member leaves and investors need reassurance about business continuity.
Pro tip: Never criticize departing team members to investors. Professional transitions happen. Focus on continuity and succession planning.
You are a hardware founder explaining supply chain disruption recovery.
Company: {company_name} Supply chain issue: {specific_disruption} Production impact: {units_delayed_or_cost_increase} Customer delivery delays: {timeline_impact} Alternative supplier research: {backup_options_evaluated} Diversification strategy: {new_supplier_relationships} Inventory buffer plan: {safety_stock_strategy} Cost implications: {unit_economics_impact} Customer communication: {how_customers_were_informed} Future resilience: {supply_chain_risk_mitigation}
Write a 300 to 400 word recovery update that shows supply chain learning. Detail your diversification strategy. Include specific timeline for resolution. Address cost impact honestly.
When to use it: After resolving a supply chain crisis when you need to update investors on lessons learned and prevention measures.
Pro tip: Hardware investors expect supply chain problems. They want to see how you build anti-fragile operations, not perfect ones.
You are a SaaS founder addressing a security incident with investors.
Company: {company_name} Incident type: {data_breach_or_system_compromise} Discovery date: {when_you_found_the_issue} Scope of impact: {data_or_systems_affected} Customer notification: {communication_timeline_and_method} Immediate response: {incident_response_actions} External support: {security_firms_or_consultants_engaged} Regulatory compliance: {gdpr_hipaa_or_other_requirements} Prevention measures: {new_security_infrastructure} Business impact: {customer_retention_and_revenue_effects}
Write a 400 to 500 word incident update that demonstrates crisis management competence. Lead with customer impact mitigation. Detail your systematic response. Show long-term security improvements.
When to use it: After containing a security incident when investors need full context on customer impact, regulatory compliance, and prevention measures.
Pro tip: Security incidents test leadership under pressure. Show investors you handled customer communication, compliance, and prevention systematically.
You are a marketplace founder explaining how you handled a trust and safety crisis.
Platform: {platform_name} Safety incident: {type_of_problem_without_details} Platform response time: {how_quickly_you_acted} Affected users: {scope_without_identifying_information} Immediate actions: {crisis_response_measures} Policy updates: {new_community_guidelines_or_verification} Technology improvements: {automated_detection_or_prevention_tools} User communication: {how_you_addressed_community_concerns}