Skip to content
OperatorNest

Weekly investor update from your operating notes

Turn a week of operating notes into a concise investor update with verified numbers, open questions, and a draft that waits for approval.

Copy-ready brief

Every Friday at [time], draft my investor update for [reporting period]. Read [named operating notes, metric source, and last update]. Use sections for progress, setbacks, key numbers, decisions, and asks. Cite the source beside every number in the draft for my review. If a number is missing or records conflict, leave a visible question instead of guessing. Keep customer details within the disclosure rules I give you. Show me the complete message and recipient list. Hold the send until I approve the final text.

Illustrative example

Example output

Example draft for illustration only:
Subject: Weekly update, [period]
Progress: The onboarding checklist was completed for Brackenwold Studio. [Source: project note]
Setback: The planned handoff moved to next week because two review items remain open. [Source: task board]
Key number: [Needs confirmation: two reports show different totals for active accounts.]
Ask: One introduction to an operator who has managed a similar handoff.
Status: Draft held. Recipients and wording await approval. No email sent.

Trigger and cadence

Trigger
The weekly draft time arrives after the reporting period closes.
Cadence
Draft each Friday; send only after the founder reviews and approves it.

Inputs

  • Last update, current operating notes, and the source for each metric.
  • The reporting period, recipient list, and preferred length.
  • Decisions, asks, and topics that must stay internal.

Steps

  • Collect notes and numbers for the defined reporting period.
  • Compare each metric with its source and flag missing context.
  • Draft progress, setbacks, decisions, and specific asks.
  • Mark claims that need the founder's confirmation.
  • Present the complete email and recipients for review.

Approval boundary

No investor email sends until the founder approves its recipients and final wording.

Stop conditions

  • A metric has no identifiable source or reporting period.
  • Two records disagree on a number.
  • A claim includes private customer information without permission.

Expected output

One investor update draft with sourced numbers, explicit gaps, and proposed asks.

Receipt fields

  • Reporting period and source documents checked.
  • Draft versions, unresolved claims, and recipient list.
  • Approval decision and send time if approved.

Recovery when it fails

  • Leave disputed numbers as questions and ask the founder for the correct source.
  • Save the draft so the next run can resume without recreating approved sections.
On this page

Build the update from a defined week

A weekly investor update reports what changed during one defined period. OperatorNest drafts progress and setbacks from named sources, then waits for your review of claims and recipients. The example here illustrates that instruction.

Write start and end dates into the request before drafting, especially when a month closes midweek, because “this week” can mean five business days, a calendar week or the interval since the last update, leaving your numbers and narrative describing different periods if you haven’t chosen one. Use actual dates.

Give each number a source

Name each metric’s source: the sales report, launch-count task board or cash statement. Put that source beside the number in the review draft, then remove the note from the email after you confirm it.

If Sam has an account total in a Monday planning note and a different one in Friday’s report, show both with their sources and ask which covers the reporting period instead of averaging or choosing the larger number to make the update read more confidently. Quotes, delivery dates and milestones need the same check.

Compare the previous update with current notes, flag stale items and require a current owner and date for claims such as “handoff on track.” Last week is context.

Keep progress, setbacks, and asks specific

Use a short section for work that finished, one for what slipped or changed, and one for decisions ahead. Replace broad claims with a concrete event: “Brackenwold Studio reviewed the onboarding checklist” tells a reader more than “customer work progressed.” If the note describes a plan, label it as a plan.

An ask should be answerable. “Can you introduce us to someone who has managed customer onboarding at a small agency?” is more useful than “Any advice welcome.” If there is no current ask, leave the section out. Let the bullet count vary.

Review flagged customer names, financial details and internal decisions against the recipients’ access. You decide what can be disclosed.

Review the send as a separate step

The workflow ends in a draft. Read the subject, body, attachments, and complete recipient list together. A correct update sent to the wrong group is still a serious mistake. Use the approval boundary to hold the send until you approve it.

After the decision, the receipt should show the source documents consulted, draft changes, approval time, and whether an email was actually sent. If you hold the update to resolve a number, resume from the saved draft. Carry the confirmed correction into next week’s source list so the same disagreement does not recur.

Run it on a schedule

Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.

  • AI task brief generator

    Turn a rough request into a task brief with a goal, needed inputs, steps, approval points, receipt details, and a repeat schedule.

  • AI agent receipt template

    Make a task receipt with the request, actions, sources, approvals, uncertain steps, result, model usage, and cost. Copy or download it.

  • AI token counter

    Paste text to count words, characters, and OpenAI tokens. Compare labeled estimates for other models and calculate input cost at a selected rate.

Common questions

Can the draft fill in a missing metric from last week?

It should carry the question forward, not repeat a number as current. The founder supplies or confirms the new source before the update sends.

Should the operator send the same text to every investor?

Start with one reviewed version. If recipients need different detail, prepare separate drafts and show the recipient list beside each.

What if Friday's numbers arrive late?

Keep the draft open, label the missing period, and complete it when the source arrives. A delayed, accurate update is more useful than a guessed total.

Hand off your first task tonight.

Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.