Choose what to get done
Partner data-sharing rules mapped to tiers and risk
A complete, partner-tier-by-population data-sharing rule spec: for each tier and population the chosen match condition and exact fields to expose, with PII handling and hard-excluded accounts spelled out, so sharing is configured consistently.
Performance-overshoot and basis-of-competition register
A structured overshoot register: one row per market tier recording demanded vs delivered performance, an overshoot verdict, and the predicted next basis of competition, structured by the producer from the buyer's description of the tiers and checked by STUD for internal logical consistency.
Plan-B survival plan
A structured survival-plan document that names the fundraise (Plan A) assumption, the dated switch trigger, the specific cost-cut and revenue actions of Plan B, and the resulting runway, so the team has a written fallback instead of vague optimism.
Pre-build letter of intent for an enterprise customer
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.
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.
Preferred-stock redemption schedule
A structured JSON redemption schedule listing each anniversary, the fraction of preferred redeemed, and the per-tranche redemption amount, with the fractions summing to 100%.
Presentation segment-and-quiz coverage map
A presentation map where every segment carries an audience-value takeaway and at least one quiz question that references that segment, with the segment count and per-segment quiz minimum enforced.
Press list of reporters to pitch
A deduplicated press contact list built to your brief: every row carries a reporter name, a publication, a valid-format email address, and a sample-article link, with duplicate emails and single-source padding screened out.
Press release with every element a reporter needs
A complete, structurally-checked release: a headline that names your company, a distinct subhead, a dateline matching your city and date, a lead of at least 25 words, your requested number of attributed quotes, a number or statistic in the body, a boilerplate that names your company, your media contact email, and your media-kit link, all within the word cap.
Price fences that separate willingness-to-pay segments
I get a set of price fences that keep my higher and lower willingness-to-pay segments in their own tiers, so a low-value buyer cannot cheaply access the high-value price.
Price-increase message with a fairness rationale
I get a price-increase message that carries a genuine rationale, fair notice, and a disclosed magnitude, so customers read it as fair rather than opportunistic.
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.