Choose what to get done
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.
Model router that sends each query to the right LLM
A routing function that dispatches each query to the right model by its type, normalizing case and falling back to a default for any unlisted type.
One-sentence description of what I'm building and why
One clear sentence (8 to 40 words, no buzzwords) that states what you are building, for whom, and why it matters.
Online-presence audit for demand, trust, and journey impact
I get a structured audit of my online presence: each page or surface across the four categories rated on create-demand, build-trust, and potential-impact using fixed enums, with negatives flagged so I know what is hurting the journey.
OpenAPI endpoint reference
A complete, well-formed reference for one endpoint: method, path, parameters (with every path placeholder covered), the required status codes, and a consistent request body.
Partner contribution map of bricks supplied to the buyer journey
I get a structured map of which bricks each partner (reseller, distributor, agency) contributes to my Yellow Brick Road, tied to specific milestones, so I can see where the partner ecosystem strengthens or leaves gaps in the journey.
Pre-requisition team gap register
A defensible record of WHY this role exists and the specific gap it fills on the team, completed before any job description is written.
Pre/Post-Money Cap Table With Option Pool
The founder has a fully-reconciled pre- and post-money cap table, with the option pool shuffle baked in, ready to attach to a term sheet.
Press release with every element a reporter needs
A complete, structurally-correct release: headline and subhead, a dated dateline, a strong lead, attributed quotes, a stat in the body, a boilerplate, a contact, and a media-kit link, all under the length cap.
Privacy-by-design seven-principles AI register
A JSON register with one entry per PbD principle passes validation: all seven canonical principles are present with correct slugs, each has an implementation note of minimum length, a status from the allowed enum, an assigned owner, and no principle is duplicated.
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.
You are not what you make. You are the one who can make it.
Opens soon. Get early access the day it goes live.