Choose what to get done
Investor due-diligence answer register
A category-balanced register of answers to standard investor due-diligence questions, structured as data-room-ready JSON, with category coverage, answered-count consistency, and per-answer length floors machine-checked.
Investor-type match with conflicts flagged
A ranked shortlist of investor types fit to your stage, revenue-certainty, timeline, and control preferences, each row scored on the same comparison dimensions with its specific advantage and the one named conflict to mitigate.
Jobs-vs-attributes market segmentation map
A structured circumstance-based segmentation map: a set of jobs-to-be-done, each tagged with the functional/emotional/social dimension, the circumstance, and the competing-alternatives set (which must include a nonconsumption option), explicitly contrasted against the rejected attribute-based segments.
Liquidation preference structure spec
The founder (or counsel) has a complete, parameterized specification of the liquidation-preference stack ready to drop into a term sheet or shareholders' agreement.
Liquidation preference vs convert election calculator
The founder can predict, deterministically, what each preferred holder will choose at any exit value and the resulting proceeds split.
Liquidation preference waterfall
You get each preferred investor's exit payout and the common-shareholder (founder and employee) residual for a given exit value, computed from each investor's invested amount, preference multiple, participating-or-not, participation cap, and as-converted ownership; payouts always sum exactly to the exit.
Logs, metrics, and traces instrumentation plan
A concrete plan covering all three observability pillars per service, plus an SLI for every golden signal, so you can actually see what your app is doing.
Love-vs-like product diagnostic instrument
A measurement instrument that tells love from like across five signals (repeat use, fanatical users, the would-miss test, organic referral, willingness to pay), each with a metric, a numeric threshold, and a data source.
Maintainability index per module
The Maintainability Index (raw and 0-100 normalized) per module from Halstead volume, cyclomatic complexity, and lines of code, with a maintainability band.
Man-in-the-jungle intrigue narrative arc
Your backstory shaped into a four-beat intrigue arc (jungle, beasts, will he escape, held at the edge) that names your protagonist in the opening beat, puts your concrete stake in the beasts beat, poses a literal open question in the escape beat, and flags the final beat unresolved, ready to drop into a pitch.
Market sizing with the adequacy check (TAM, SAM, SOM)
TAM grossed up from a partial-coverage database count, SAM and SOM by your fractions, and a check that SOM clears 2x your revenue objective.
MECE use-case modules with per-segment value
I get a modular packaging map where features are partitioned into non-overlapping use-case modules, no feature is left unassigned, and each module carries a t-shirt value per segment plus a base/add-on flag.