Build · Assess & Decide · Writing & Content
Build Notes-vs-Priced Financing Decision Register
A structured decision register that scores convertible-note versus priced-round across every required factor (default: cost, speed, resolution, investor protections, misalignment, confusion, control, investor preference) plus the two easy-case flags (family-and-friends, bridge to finish an in-progress round), ending in a single recommended instrument that follows the weighted tally, with a rationale per factor.
You receive: A JSON object {factors:[{factor, favors, weight, rationale}], easyCaseFlags:{familyAndFriends, bridgeToFinishRound}, recommendation, recommendationRationale}. Enforced literals: factor tokens default to cost, speed, resolution, investor_protections, misalignment, confusion, control, investor_preference; favors must be note, priced, or neutral; recommendation must be note or priced; easyCaseFlags values must be JSON booleans.
Part of Choose Business Model, Pitch Investors
What's verified: STUD verifies the register parses as a single JSON object no larger than 20,000 characters, that factors covers exactly your required factor set (the default set is these exact tokens: cost, speed, resolution, investor_protections, misalignment, confusion, control, investor_preference), that each factor's favors is exactly one of the literals note, priced, or neutral, that each weight is an integer from 1 to 5, that each factor rationale and the recommendation rationale meet the minimum length (default 20 characters) and no two factor rationales are duplicates, that easyCaseFlags echoes your family-and-friends and bridge answers as booleans, that recommendation is exactly the literal note or priced, that a yes on either easy-case flag forces a note recommendation, and that otherwise the recommendation matches the weighted tally of favors (on an exact tie, either is accepted). The minimum rationale length setting must be between 1 and 500 or the submission is rejected. Length and non-duplication are the only content checks on rationales: STUD does NOT verify that any rationale is true or well reasoned, and it does NOT decide whether a note or a priced round is genuinely better for your company, nor validate any legal terms. Company name, stage, raise amount, and round context are operator context only; they are never checked by the validator.
Opens soon
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
Factors
| Factor | Favors | Weight | Rationale |
|---|---|---|---|
| cost | note | 4 | STUD is pre-seed with no legal budget for negotiated priced-round docs, so a note's light-touch paperwork favors it on cost. |
| speed | note | 3 | STUD has a single founder-operator running the soft launch, so closing a note in days beats a multi-week valuation negotiation. |
| resolution | note | 3 | STUD is pre-revenue with no priced comps yet, so deferring the valuation question to a later round favors the note. |
| investor_protections | note | 2 | A discount and a cap give early check-writers real downside protection without a full priced-round term set. |
| misalignment | priced | 3 | Stacking several notes ahead of an eventual round risks mismatched caps and discounts, which favors pricing it now. |
| confusion | priced | 2 | One priced cap table is easier to explain to future investors than several notes with different conversion terms. |
| control | priced | 2 | A priced round sets board and voting terms immediately, which matters once STUD adds a second decision-maker. |
| investor_preference | priced | 2 | Some check-writers prefer governance and equity rights now rather than waiting for a note to convert later. |
Easy Case Flags
Get early access to STUD the day it goes live.