Choose what to get done
Influencer pay ceiling
A value-based pay ceiling per influencer (from order value, margin, and conversion rate), with a within-budget verdict.
Integration adoption rate with a build-next ranking
Per-integration adoption rate over the overlapping base it can actually serve, health-flagged, plus a build-next ranking by addressable market.
Interview panel coverage plan
A structured interview-loop plan mapping interviewers to competencies, sized per the research, with a dissenter assigned.
Investor due-diligence answer register
A complete, category-balanced register of answers to the standard investor due-diligence questions, ready to drop into a data room.
Job requisition spec
A complete requisition: responsibilities with success metrics, a must-have skills list capped to avoid the unicorn trap, a valid comp range, and a clean biased-language screen.
Letter of intent for an enterprise customer to sign before I build
An unsigned letter of intent the customer can sign: intent-to-purchase language, commercial terms, conditions, an explicit non-binding clause, and two signature blocks.
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.
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.
Map a price waterfall from list to pocket price and flag leakage
I get a price waterfall that ties my pocket price back to my list price through named, quantified leaks, so I can see exactly where realized revenue is lost.
Map product features to 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.
Market sizing (TAM / SAM / SOM) with the adequacy check
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.
You are not what you make. You are the one who can make it.
Opens soon. Get early access the day it goes live.