Choose what to get done
Fundraising Objection Coverage Register
The founder walks into the meeting with a complete pre-pitch register: a written, evidenced rebuttal row for every required VC objection category, and, under the default setting, no row left as an open gap.
GenAI IP risk contract checklist validator
A JSON clause register covering all five canonical GenAI IP risk categories passes validation: every category is present exactly once, each has a clause excerpt of minimum length, a contract reference, and a status from the allowed enum; no category is misspelled or duplicated.
In-House Build-vs-Buy Tendency Scorer
A founder weighing whether to sell an AI capability as a service gets a 0-6 in-house-tendency score and a build/buy verdict per the book's exact criteria, flagging capabilities customers will just build themselves.
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 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.
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.
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.
One-sentence description of what I'm building and why
One plain-language sentence that states what you are building, for whom, and why it matters, machine-checked against the published rules: exactly one sentence, inside the published word band, a purpose connective present, no banned buzzwords, no em or en dashes.
Online-presence audit for demand, trust, and journey impact
I get a structured audit of my online presence: each surface, across website, branded search, social media, and review sites, rated on create-demand, build-trust, and potential-impact using fixed scales, with a short written note per surface and every negative-impact surface flagged.
Partner contribution map of bricks supplied to the buyer journey
I get a structured map of which bricks each partner (reseller, distributor, dealer, agency, consultant, or sales agent) contributes to my Yellow Brick Road, with each brick tied to a specific milestone 1 to 5 and rated on whether it creates demand and builds trust, so I can see where the partner ecosystem supports the journey and which milestones have no partner brick at all.