Build · Assess & Decide · Ops & Automation
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.
You receive: A JSON object: { role_title, team_name, requisition_type (enum: new-role|backfill|reshape), strategic_goals[] (each {goal, required_capability}), current_team[] (each {member_label, key_skills[], aspiration}), gap_items[] (each {capability, gap_type enum: missing|thin|leaving, current_coverage_count, future_need_horizon enum: now|6mo|1-3yr, fills_structural_hole bool}), cultural_fit_traits[], overlap_risks[] (aspirations that already exist on the team), justification_summary_fields {hole_filled, why_not_internal} }.
Part of Lead Team
Example
A sample of what this play produces. Your result is generated for your inputs.
- Role title
- Founding growth engineer
- Team name
- STUD core (founder-operator)
- Requisition type
- new-role
Strategic goals
| Goal | Required capability |
|---|---|
| Reach the illustrative 200 launch signups through content-led acquisition (SEO, developer docs, launch communities) at the modeled $40 blended CAC (illustrative) | Content-led growth engineering: SEO instrumentation, landing experiments, launch-community distribution |
| Convert launch interest into 40 activated buyers in month 1 and 25 retained at month 3 (illustrative launch scenario) | Activation funnel analytics and lifecycle instrumentation |
| Keep the 265-play catalog compounding: every run's result feeds the next play, so retained buyers deepen usage | Product analytics on play usage and workspace-fact reuse |
Current team
- Member label
- Dan Schmitz (founder-operator)
- Key skills
- platform engineering (Next.js, Postgres)
- play catalog design and validator authoring
- judge and settlement architecture
- pricing and credit economics
- Aspiration
- Stay hands-on with the living-system platform: catalog quality, judge rigor, and workspace architecture
Gap items
| Capability | Gap type | Current coverage count | Future need horizon | Fills structural hole |
|---|---|---|---|---|
| Content-led growth engineering: SEO instrumentation, landing experiments, launch-community distribution | missing | 0 | now | true |
| Activation funnel analytics and lifecycle instrumentation | missing | 0 | now | true |
| Product analytics on play usage and workspace-fact reuse | thin | 1 | 6mo | false |
| Paid-fulfillment onboarding operations at concierge capacity (30 plays/week ceiling) | thin | 1 | 6mo | false |
| Marketplace supply-side partnerships for third-party operators | missing | 0 | 1-3yr | false |
Cultural fit traits
- Plain, factual communication (matches STUD's voice: no coax, no discount framing)
- Ships against a machine acceptance check without resenting the floor
- Comfortable as employee #1 alongside a solo founder, pre-seed and pre-revenue
Justification summary fields
- Hole filled
- STUD is a team of one: the founder covers platform, catalog, and judge work, and nobody owns demand. Growth engineering has zero current coverage (two 'missing' gaps at horizon 'now'), so the illustrative 200-signup launch target has no owner. This role fills that structural hole.
- Why not internal
- There is no internal candidate: the whole team is one founder-operator whose stated aspiration is the platform and catalog, not growth, and concierge capacity is already capped at 30 plays/week. Reassigning the founder to growth would starve the product that growth is meant to sell.
Opens soon
STUD opens runs for everyone soon, on every play at once.
Get early access to STUD the day it goes live.