Build · Create · Data & Research
Sources & Uses of Funds Statement
The founder has a fully reconciled sources-and-uses statement that maps every dollar of the raise to a milestone, task, owner, and funding source.
You receive: A JSON object { raiseAmount, milestones[], uses[], sources[], totals{totalUses, totalSources} } where milestones[] = { milestoneId, name }, uses[] = { taskId, milestoneId, task, owner, cost }, sources[] = { sourceName, type (enum: equity_raise|sales_revenue|grant|debt|founder_capital|other), amount }
Part of Pitch Investors
What's verified: STUD verifies the statement reconciles (uses = sources = raise within tolerance), every task ties to a real milestone with an owner and positive cost, and source types are valid. STUD does NOT judge whether the cost estimates are realistic or the milestones are the right ones.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"milestoneNames",
"raiseAmount",
"tieOutTolerance"
],
"checkNames": [
"format_parses",
"milestones_present",
"tasks_per_milestone",
"task_refs_valid",
"task_fields",
"source_enum",
"source_amounts",
"uses_total",
"sources_total",
"balanced",
"ids_unique"
],
"constants": {},
"deliverableLabel": "sources_and_uses_of_funds_statement",
"documentKeys": [
"amount",
"cost",
"milestoneId",
"milestones",
"name",
"owner",
"sources",
"task",
"taskId",
"totalSources",
"totalUses",
"totals",
"type",
"uses"
],
"enumLiterals": [
[
"equity_raise",
"sales_revenue",
"grant",
"debt",
"founder_capital",
"other"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.