From founder notes to an update worth reading

Show what changed. Ask for useful help.

An investor update is a recurring, reviewed account of progress, setbacks and priorities, with consistent metric definitions and specific requests for help.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
A consistent comparison
Four teams completed onboarding versus three, using the same checklist—not a completion rate.
02
Close the loop honestly
The promised guide is available; its effect has not been measured.
03
Give help a clear shape
Ask for an introduction to someone with relevant B2B onboarding experience.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Your progress. Your agent. A specific ask.

Let readers see the comparison, the unresolved problem and how they can help without decoding a wall of founder notes.

Start with three things

Approved metrics with definitions and comparison periods.
The previous update, delivered commitments and unresolved setbacks.
Next priorities, a specific request and approved sharing boundaries.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the investor updateAsk your agent to keep definitions steady, separate delivered work from unmeasured effects, and make one concrete request easy to understand.

How can an AI agent help me write an investor update?

Give the agent approved metrics, the previous update, founder notes, and concrete requests. Ask it to preserve metric definitions, distinguish actual results from plans, and surface material changes. Review the figures and sensitive content before sharing a dated HTML update with the intended recipients.

What to give your agent

Approved metrics for this period and the comparison period, with exact definitions and calculation ownership.
The previous investor update, including commitments or questions that deserve a follow-up.
Founder notes covering wins, setbacks, priorities, and what remains uncertain or unconfirmed.
Specific requests and approved sharing boundaries for customer names, personnel details, financial information, and company plans.

Keep a stable reporting spine
Choose a small recurring set of measures and preserve their definitions across updates. Have the agent show the current period, comparison period, and explanatory notes together. If a definition changed, disclose it and avoid presenting the figures as directly comparable unless the earlier value has been restated appropriately.
Explain change without polishing it away
Pair each material movement with supported context. Separate outcomes already achieved from targets and expectations. Include the problem that needs attention, not just achievements. An agent can improve wording, but it should not convert uncertain founder notes into confident forecasts or explain a metric using an unverified cause.
Make requests easy to route
Replace broad asks such as 'introductions welcome' with the role, relevant experience, reason for the introduction, and a simple next step. Keep the request within approved disclosure boundaries. A recipient should be able to tell whether they can help without scheduling a meeting to decode the ask.
Review the report as sensitive communication
Generate a concise static HTML update in your saved style if available. Have the responsible people verify figures and any sensitive statements. Check recipient access before publishing, and use another approved channel if the page's sharing controls do not fit the material. This is a communication workflow, not investment or disclosure advice.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Draft an investor update for [period] from my approved metrics, previous update, and notes. Keep recurring metric definitions consistent and show comparison periods. Flag changed definitions, conflicting figures, and unsupported explanations. Distinguish actual results, estimates, targets, and plans; do not invent forecasts or imply investment outcomes. Lead with the most material changes, then progress, setbacks, next priorities, and specific asks. Follow up on commitments from the previous update. Write each ask with the relevant person or expertise, purpose, and next step. Produce concise static HTML using my saved artifact style if available, without scripts or live-data claims. Highlight financial, customer, and personnel information for review. Do not publish or change access until I approve the facts, wording, and intended recipients. Only if this is an authorized informal board read-ahead, separate information, discussion and decision requests. Preserve approved facts and confidentiality, and do not infer a resolution from circulation. Keep formal board papers, governance requirements, minutes and voting in the organization's qualified reviewed workflow.

Check before you shareAccuracy, clarity, and permission

Have the people responsible for the metrics verified values, definitions, period boundaries, and comparisons?
Are estimates and future plans clearly separated from achieved results, with no invented causal explanations?
Does the update address earlier commitments and make each current request specific enough to act on?
Are sensitive disclosures approved, and does the selected sharing method fit the intended recipient group?

When HTML fits

Use an HTML update for a readable, dated narrative with a consistent metric section and clear asks, when its access controls fit your communication needs. Keep an approved copy of each reporting period.

When another format fits better

Do not use a broadly shareable page for confidential information that requires tighter controls. Keep formal financial reporting, regulated disclosures, and fundraising documents in their appropriate reviewed workflows.

What we started withThe same facts, as an email

Fictional project email

Pilot update — setup progress and a specific introduction

This fictional founder update was prepared September 22, 2026, not a reporting-period boundary. It is intended to illustrate a reviewed update for an approved investor recipient; no actual company, investor or customer is represented.

Four pilot teams completed onboarding this period, compared with three last period, using the same agreed onboarding checklist. The detailed checklist, calendar boundaries, period lengths, eligible-team totals and overlap are not supplied. These are counts, not a completion rate, established growth trend, paid-customer or revenue result, or investment outcome.

There are two additional teams that have not completed setup. Their outstanding steps are being reviewed; the cause is not yet confirmed. No owner, completion date or customer-level details are supplied.

The last update promised a revised setup guide. It is now available to the pilot teams, but its effect has not yet been measured. The next reporting period will focus on understanding incomplete setup and testing the guide. Those are future priorities, not completed work or a forecast; no test result, staffing commitment or date is supplied.

An introduction to a customer-success leader who has designed onboarding for small B2B teams would help the founder review this process. The requested next step is an introduction, not an endorsement or investment commitment. No recipient name, contact channel, booking link or response deadline is supplied.

For a real update, the responsible company owner must verify figures, definitions, sensitive disclosures and intended recipients before sharing. Keep formal financial reporting, regulated disclosures and fundraising documents in their appropriate reviewed processes. This static example does not send updates, authorize disclosure or refresh metrics automatically.

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Pilot update · Progress and a specific ask</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f5f1e7;color:#24312a;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,60px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(34px,5vw,62px)/1.08 Georgia,serif;letter-spacing:-.03em;overflow-wrap:anywhere}h2{font:500 28px/1.25 Georgia,serif}h3{font-size:19px}.label{font-size:12px;font-weight:700;letter-spacing:.1em;text-transform:uppercase}.intro{font-size:20px}.comparison{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:20px;border-top:1px solid #87998b;border-bottom:1px solid #87998b;padding:28px 0;margin:28px 0}.count{display:block;font:500 clamp(38px,7vw,76px)/1.1 Georgia,serif;margin:12px 0}.current{color:#20513c}.note{font-size:14px;color:#465a4c}.open{border-left:5px solid #956118;padding-left:22px}.thread{border-top:1px solid #b3bfae;padding-top:22px}.ask{background:#20513c;color:white;padding:clamp(20px,4vw,36px)}section{margin:38px 0}footer{border-top:1px solid #87998b;padding-top:24px;font-size:14px}p:last-child{margin-bottom:0}@media(max-width:360px){.comparison{gap:12px}.count{font-size:36px}}@media print{body{background:white}.comparison,.ask{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main>
<header><p class="label">Fictional founder update / Prepared September 22, 2026</p><h1>More teams through setup.<br>Two still need attention.</h1><p class="intro">A pilot update with one delivered promise, an open question and a specific way to help.</p></header>
<section><h2>The comparison keeps its definition.</h2><div class="comparison"><div><p class="label">Last period</p><strong class="count">3 teams</strong><p>Completed onboarding</p></div><div class="current"><p class="label">This period</p><strong class="count">4 teams</strong><p>Completed onboarding</p></div></div><p>Both counts use the <strong>same agreed onboarding checklist</strong>.</p><p class="note">Source M1. Calendar boundaries, period lengths, eligible-team totals and overlap are not supplied. These are counts—not a completion rate, an established growth trend or an investment outcome.</p></section>
<section class="open"><p class="label">Setback · unresolved</p><h2>2 additional teams have not completed setup.</h2><p>The outstanding steps are being reviewed; the cause is not yet confirmed. No completion date or owner is supplied.</p><p class="note">Source S1. No customer identities or unsupported explanation are added.</p></section>
<section class="thread"><p class="label">Closing the loop · previous commitment</p><h2>The revised setup guide is now available.</h2><p>The last update promised the guide. Pilot teams can now use it; its effect has not yet been measured.</p><p class="note">Source C1. Delivered guidance is not proof of improved onboarding.</p></section>
<section class="thread"><p class="label">Next period · planned focus</p><h2>Understand the blockers. Test the guide.</h2><p>The next reporting period will focus on understanding incomplete setup and testing the revised guide. No result, staffing commitment or date is supplied.</p><p class="note">Source P1. These are priorities, not completed work or a forecast.</p></section>
<section class="ask"><p class="label">One specific ask</p><h2>Know a customer-success leader who has built onboarding for small B2B teams?</h2><p>An introduction would help the founder review this process. That is the requested next step—not an endorsement or an investment commitment.</p><p>No contact channel or response deadline is supplied in this fictional example. Source A1.</p></section>
<section><h2>Before a real update is shared</h2><p>The responsible company owner must verify figures, definitions, sensitive disclosures and intended recipients. Keep formal financial reporting, regulated disclosures and fundraising documents in their appropriate reviewed processes.</p><p class="note">This example is communication design, not investment advice. The preparation date is not a reporting-period boundary.</p></section>
<footer>Fictional worked example by share/artifacts. All facts are invented for demonstration from the accompanying source bundle. Static snapshot; no live data or automatic updates. This page does not send an update or authorize disclosure.</footer>
</main></body></html>

The original worked scenarioThe source scenario, step by step

An update that closes the loop

An illustrative founder is reporting a product pilot. All details are fictional, and the example deliberately avoids implying any investment outcome.

The original notes

Strong momentum. Customers are excited. We are improving onboarding and would love useful introductions.

Result

Four pilot teams completed onboarding this period; last period, three did. 'Completed' uses the same agreed onboarding checklist in both periods.

Setback

Two additional teams have not completed setup. Their outstanding steps are being reviewed; the cause is not yet confirmed.

Follow-through

Last update promised a revised setup guide. The guide is now available to the pilot teams; its effect has not yet been measured.

Priority

The next reporting period will focus on understanding incomplete setup and testing the revised guide.

Ask

An introduction to a customer-success leader who has designed onboarding for small B2B teams would help us review the process.

Consistency makes change legible. A specific ask makes the update something recipients can act on, not just acknowledge.

Questions, adaptations & sourcesGo deeper when you need to

Should every investor update use the same structure?

Keep recurring metrics and core sections consistent so readers can compare periods. Add a focused section when something material changes. Consistency should support understanding, not force significant news into an unsuitable template or hide it beneath routine content.

What should I do if a metric definition changes?

Explain what changed, why, and which periods are affected. Ask the metric owner whether earlier figures can be restated. If they cannot, say the values are not directly comparable instead of presenting a growth calculation that implies otherwise.

Can the agent choose what is safe to disclose?

It can flag likely sensitive material, but it should not make that decision for you. Have the appropriate company owner review the content and sharing method, and obtain qualified advice where the communication requires it.

An informal board read-ahead

For an already-approved informal read-ahead, make it clear whether each item is for information, discussion or decision. This is not a formal board pack, governance advice, a voting system or a minutes record; use the organization's required reviewed process for those.

Fictional inputs: Fictional approved operating update: four pilot teams completed the same onboarding checklist this period versus three last period. Two teams remain incomplete; cause unknown. Leadership wants a capacity discussion and proposes a further pilot. The proposed pilot is not approved.

A clearer result: Information: four teams completed onboarding versus three, with definitions unchanged. Discussion: two teams remain incomplete and capacity needs review. Decision requested: consider the further pilot; circulation of the reading page is not a resolution or authorization.