Draft · Create · Writing & Content

Structured monthly investor update

A monthly investor update in a fixed JSON outline: an executive summary leading with numeric cash burn and runway, KPIs with actual vs predicted values, the five fixed accomplishment categories each populated, plans across three horizons, and a financing outlook, all structurally checked.

You receive: A JSON object { period, executive_summary: { cash_burn, runway_months, highlights:[..], lowlights:[..], key_metrics:[{name,actual,predicted}] }, details: { kpis:[{name,actual,predicted}], accomplishments:{sales,product,marketing,partners,staffing}, challenges:[{issue,plan}], plans:{next_month,next_quarter,next_year}, market_updates, next_financing }, asks:[..] }. The accomplishment keys (sales, product, marketing, partners, staffing) and plan keys (next_month, next_quarter, next_year) are fixed literals the validator requires to be present; extra keys are ignored.

Part of Launch Product, Pitch Investors

What's verified: STUD verifies structure and counts on the JSON update: it parses as a single JSON object no larger than 20,000 characters; the top-level period exactly equals your reporting period; executive_summary carries a numeric cash_burn and a numeric runway_months, at least your minimum count of non-empty highlights (default 2), a lowlights array (it may be empty), and a key_metrics array; details.kpis carries at least your minimum count of KPIs (default 2), each with a non-empty name and numeric actual and predicted values, and no duplicate KPI names; details.accomplishments contains each of the five fixed categories, the keys 'sales', 'product', 'marketing', 'partners', 'staffing', each with non-empty text (extra keys are ignored, not machine-blocked); details.plans contains each of the keys 'next_month', 'next_quarter', 'next_year', each non-empty (extra keys are ignored, not machine-blocked); details.challenges is an array where every entry names a non-empty issue, and, only when you set 'Every challenge must have a plan' to yes (default no), every challenge also carries a non-empty plan; details.next_financing is non-empty text; asks is an array. Your minimum-highlights setting must be 1 to 20 and minimum-KPIs 1 to 30 or the deliverable is rejected. STUD does NOT verify any arithmetic or numeric relationship: it does not check that runway_months is consistent with cash on hand divided by cash_burn, that KPI actuals reconcile to your books, or that any figure is true or plausible. STUD does NOT verify the quality, accuracy, or investor-readiness of the prose; lowlights, key_metrics, and asks entries beyond the array type checks; or market_updates at all. Your company name and period notes are operator context only and never affect the verdict.