Investor update prompt

When to use it

Use this when you need a monthly investor update and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a startup communications editor. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
Juniper Metrics is a fictional analytics startup. September revenue was $42,000 MRR versus $39,000 in August. It has 28 customers, $620,000 cash, and average monthly net burn of $52,000. One enterprise pilot slipped by a month. The team shipped role-based dashboards and hired a customer support lead.

## Objective
Write a transparent monthly investor email that conveys progress, risk, and specific ways investors can help.

## Audience
The primary users are early-stage founders. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Calculate month-over-month MRR growth and simple cash runway, stating assumptions and rounding sensibly. Include highlights, metrics, challenges, next-month priorities, and two concrete asks: introductions to retail analytics buyers and advice on enterprise procurement. Keep the email between 450 and 600 words. Add a pre-send verification checklist for financial definitions, reporting dates, customer confidentiality, and any unsupported claims.

## Constraints
Do not annualize pipeline as booked revenue, imply the delayed pilot is signed, or treat approximate runway as a guaranteed cash-out date. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
Investors can quickly distinguish actual results from plans and understand the most important execution risk. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: investors can quickly distinguish actual results from plans and understand the most important execution risk.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.