Choose what to get done
Problem definition document
A problem definition document with the market, buyer roles, and per-problem definition, metrics, prior solutions, buying authority, and a 1-10 severity.
Product requirements document (PRD)
A complete PRD: the named sections, a quantified business context, a measurable success metric, and acceptance criteria with a clear out-of-scope fence.
Protective-provisions and board-approval consent register
A structured JSON register enumerating each protected corporate action, the approving class, and the consent threshold, covering the required protective-provision items with valid thresholds.
Revenue Zone understandings, beliefs, and readiness gates
I get a structured definition of my Revenue Zone for one product: exactly three understandings and three beliefs (each mapped to demand or trust) plus the budget and impending-event readiness questions, so my team and partners share one bar for 'ready to buy'.
Romance-the-problem stakes anchor
I get a structured stakes anchor with exactly one magnitude statistic (value, unit, claim, and a cited source unless I turn sourcing off), a hook of a type I allow, and a consequence-if-unsolved line that meets my minimum word count, so I can romance the problem without drowning the audience in numbers.
Sales enablement asset register
A sales enablement asset register that, for each asset (one-sheet, case study, battlecard, demo video, ROI calculator, etc.), records the buyer question it answers, the funnel stage to send it, its format, and a valid link, so sellers know exactly which asset to send and when.
Sales objection handling register
A register of recurring sales objections surfaced from a fixed document set, each categorized, counted by occurrence, and paired with a suggested rebuttal, so a rep can prep before the next meeting.
Scannable pitch deck on a fixed section spine
A scannable deck spec: the required sections in order, your company named in the deck, one idea per slide, and a three-sentence elevator pitch.
Scored brickyard inventory of demand-and-trust touchpoints
I get a structured brickyard: every brick sorted into the five areas (online presence, content, offerings, ecosystem, internal team), scored on the three fixed dimensions, with a ready/cracked/missing status per brick and per-area counts that match the bricks, ready to assemble into a journey.
SDR and AE specialization with ramp
I get an SDR and AE role split where each role owns distinct responsibilities, carries a ramp period and a full-ramp quota, and hands off leads on explicit criteria.
Seven-sentence investor elevator pitch
A canonical seven-sentence investor elevator pitch (introduction, problem and solution, competitors, market opportunity, business model, achievements, funding ask), one checked sentence per slot within your word cap, naming your startup and founder, with the market-size and funding-ask sentences cross-checked against the pitch's own 16-slot fact sheet.
Six-frame innovation storyboard
I get a single structured storyboard document with all six narrative frames filled in (customer, insight, problem, value proposition, how it works, competitive context), each checked against a structural rule (presence, a 40-character content floor, and required phrasing), so my product story is complete in shape and ready to turn into a pitch.