Build · Create · Ops & Automation

Financing-round closing checklist

A structured closing checklist that echoes your frozen round stage, close date, and raise amounts, covers every closing step you require (a canonical six-step sequence by default), and enforces the minimum-commitment and wire-sequencing gates arithmetically.

You receive: A JSON object { round_stage, close_date, min_raise, max_raise, committed_amount, steps: [ { id, name, status, owner } ] } that echoes your frozen stage, date, and amounts, where every status is one of not_started, in_progress, done, blocked and the step names cover your required closing steps (default: lead_secured, terms_agreed, term_sheet_signed, definitive_docs_signed, min_commitments_met, wires_received).

Part of Launch Product, Pitch Investors

What's verified: STUD verifies the checklist mechanically against your frozen intake: the deliverable parses as a single JSON object of at most 100,000 characters; round_stage is exactly one of seed, series-a, series-b, series-c and matches your selected stage; close_date is in YYYY-MM-DD format and equals your frozen target close date; min_raise, max_raise, and committed_amount are numbers that equal the amounts frozen at intake, with min_raise no greater than max_raise and committed_amount at least 0; steps is a non-empty array in which every step has a non-empty id, name, status, and owner; every status is exactly one of not_started, in_progress, done, blocked; step ids are unique; every required step you list appears among the step names, matched case- and punctuation-insensitively (the default required list is exactly lead_secured, terms_agreed, term_sheet_signed, definitive_docs_signed, min_commitments_met, wires_received); and two arithmetic gates hold: min_commitments_met may be marked done only if committed_amount is at least min_raise (your frozen floor, or the document's own min_raise if no usable floor was frozen), and wires_received may be marked done only if min_commitments_met is done. That is the only arithmetic checked. STUD does NOT verify any other math (no per-investor commitment sums, no allocation, dilution, or valuation arithmetic), does NOT verify that statuses, owners, dates, or amounts reflect reality, does NOT verify legal completeness of the closing beyond the named step list, and does NOT check the company name or use-of-funds fields, which are operator context only. If a frozen value is unusable (a stage outside the four options, a non YYYY-MM-DD date, an empty step list), the validator falls back to the membership, format, or default-list check instead of failing your deliverable. Your frozen money inputs get no such fallback: if min_raise is not positive, if min_raise exceeds max_raise, if committed_amount is negative, or if you list more than 40 required steps, the validator rejects the deliverable outright (params_in_range) before any other check of the document runs.