Build · Create · Data & Research
Sources and 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, with the totals machine-checked to tie out.
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, amount }, type one of exactly: equity_raise, sales_revenue, grant, debt, founder_capital, other, and raiseAmount equal to the raise you entered.
Part of Pitch Investors
Example
A sample of what this play produces. Your result is generated for your inputs.
- Raise Amount
- 1000000
Milestones
| Milestone Id | Name |
|---|---|
| M1 | Open paid fulfillment |
| M2 | Scale the play catalog and acceptance coverage |
| M3 | Content-led demand engine |
| M4 | Team and 18-month runway |
Uses
| Task Id | Milestone Id | Task | Owner | Cost |
|---|---|---|---|---|
| T1 | M1 | Entity formation and counsel review of the money and legal plays before paid fulfillment opens | Contract counsel | 30000 |
| T2 | M1 | Stripe billing, production auth hardening, and the judge worker deployed to production | Founding engineer | 110000 |
| T3 | M1 | Independent security review of the judge sandbox and settlement path before real money settles | Contract security reviewer | 40000 |
| T4 | M2 | Grow the catalog from 265 plays toward 500, each with a paired independent audit | Dan Schmitz (founder) | 140000 |
| T5 | M2 | Harden acceptance checks so every deliverable settles against a machine-checkable contract | Founding engineer | 100000 |
| T6 | M2 | Workspace fact propagation: a fact stated once flows into every later run | Founding engineer | 80000 |
| T7 | M3 | SEO content engine across play pages and playbooks (illustrative blended CAC about $40) | Content lead (contract) | 120000 |
| T8 | M3 | Developer-docs and launch-community distribution toward 200 launch signups | Dan Schmitz (founder) | 80000 |
| T9 | M3 | Case-study pipeline that turns accepted runs into publishable proof | Content lead (contract) | 60000 |
| T10 | M4 | Founder-operator salary for 18 months of concierge capacity (30 plays per week) | Dan Schmitz (founder) | 150000 |
| T11 | M4 | Cloud hosting, inference, and judge compute for the run pipeline | Founding engineer | 60000 |
| T12 | M4 | Accounting, insurance, and ongoing legal | Contract counsel | 30000 |
Sources
| Source Name | Type | Amount |
|---|---|---|
| Pre-seed equity round (illustrative $1,000,000 target, not a committed raise) | equity_raise | 1000000 |
Totals
- Total Uses
- 1000000
- Total Sources
- 1000000
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the arithmetic: totals.totalUses equals the sum of every use cost, totals.totalSources equals the sum of every source amount, and totalUses, totalSources, and the document's raiseAmount all equal the raise amount you enter, each within your rounding tolerance (default $0.01). STUD also verifies the milestone names you enter appear exactly (no missing or extra milestones), every milestone has at least your minimum number of tasks (default 1), every use row references a real milestone and has a non-empty task, a non-empty owner, and a cost greater than zero, every source has a non-empty sourceName, an amount greater than zero, and a type from the exact list: equity_raise, sales_revenue, grant, debt, founder_capital, other, all milestoneId and taskId values are present and unique, and the submission is valid JSON under 200,000 characters. STUD does NOT verify that the cost estimates are realistic, that the milestones or tasks are the right ones for your business, or that any funding source is real or committed. The company description and stage fields are operator context only and are never checked.
Get early access to STUD the day it goes live.