Build · Create · Writing & Content
Annotated story-spine beat map
I get my product's story told in the book's nine named beats (protagonist, struggle, conflict, value proposition, team, product with its how-it-works points, better than competition, traction and market, tagline reprise), each beat labeled and carrying its own prose block of at least my minimum word count, with at least one concrete number in the traction beat and my tagline repeated in the closing beat, so I can drop any beat into a website, an email, or a script.
You receive: A JSON object {productName, tagline, beats: [{beatId, label, prose}]} covering exactly the nine named beats in canonical order, with a productMechanics list of exactly your chosen number of points (default 3) under the product beat; the productName and tagline fields must match what you provide.
Part of Pitch Investors
Example
A sample of what this play produces. Your result is generated for your inputs.
Product Name
STUD.com
Tagline
STUD is a living system for your venture: it knows your business, does the work, and learns from every result.
Beats
- Beat Id
- protagonist
- Label
- The protagonist: the founder who stays small
- Prose
- Meet the solo founder or the three-person product team. They need marketing, finance, product, and engineering work done every week, and they intend to stay small while doing it. They are already reaching for AI, and they are exactly the person STUD was built to serve: someone with a venture worth knowing and no staff to carry it.
- Beat Id
- struggle
- Label
- The struggle: knowledge work by manual craft
- Prose
- AI can produce real knowledge work, but getting that work out of it is still manual craft. The founder has to know what to ask, phrase it well, re-explain the business in every session, and carry each output somewhere by hand before it goes stale. Every session starts from zero, so nothing they do with AI compounds.
- Beat Id
- conflict
- Label
- The conflict: the blank prompt box
- Prose
- The alternatives make the struggle worse, not better. General-purpose chat assistants hand the founder a blank prompt box and amnesia. Freelance marketplaces trade money for coordination overhead. Static documentation tools store knowledge that never does anything. Each one leaves the venture's knowledge inert, and the founder stays the integration layer holding everything together by hand.
- Beat Id
- value_proposition
- Label
- The value proposition: a living system
- Prose
- STUD is a living system for a venture: it knows your business, it does the work, and it learns from every result. A fact stated once flows into every run, results land structured and stay current, and each deliverable leaves the system knowing more than it did before. The venture's knowledge stops going stale in documents and starts doing work.
- Beat Id
- team
- Label
- The team: a founder-operator who dogfoods everything
- Prose
- STUD is built by founder Dan Schmitz, operating the platform on itself: every strategic artifact STUD ships, this beat map included, is produced by running STUD's own plays on STUD's own workspace facts. That dogfood loop is the team's working method, and it means the product is exercised on real venture work every single day before any buyer touches it.
- Beat Id
- product
- Label
- The product: plays, a workspace, and compounding results
- Prose
- The product is a workspace that holds what the business knows plus a catalog of 265 ready-made plays across 14 playbooks that AI agents run from a short intake. Pick a play, the intake fills itself from your workspace facts, an agent runs it, and the result lands as a structured deliverable that feeds the next play, with an acceptance check screening every deliverable before it lands.
- Product Mechanics
- Pick a play from the catalog: the short intake fills itself from your workspace facts, so you never re-explain your business.
- An AI agent runs the play and the result lands as a structured deliverable that stays current instead of rotting in a chat log.
- Every result feeds later runs and passes its play's acceptance check before it counts, so the system's knowledge of your venture compounds.
- Beat Id
- better_than_competition
- Label
- Better than the competition: memory that compounds
- Prose
- Chat assistants forget the venture between sessions; STUD remembers it by design. Marketplaces sell one-off labor; STUD's results feed the next run. Documentation tools store knowledge; STUD's workspace puts it to work. The differentiator is compounding: the more a founder runs, the more the system knows, and the less each subsequent run costs in explanation and rework.
- Beat Id
- traction_market
- Label
- Traction and market: a live catalog in a fast market
- Prose
- STUD is pre-seed and pre-revenue in soft launch, with a live catalog of 265 plays across 14 playbooks. Buyers will pay with prepaid credit packs from $20 for 500 credits, purchased credits never expire, and a play costs 250 to 1,000 credits ($10 to $40), most of them 500 credits ($20). The AI agents market is about $8B in 2025, growing at a cited 42 to 50 percent CAGR, and an illustrative launch scenario models 200 signups converting to 40 activated buyers in month 1.
- Beat Id
- tagline_reprise
- Label
- The reprise: back to the promise
- Prose
- So the founder who once re-explained the business to a blank prompt box now states a fact once and watches it reach everything they run, with every result leaving the system smarter. That is the whole promise, worth repeating exactly as it began: STUD is a living system for your venture: it knows your business, does the work, and learns from every result.
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the deliverable is a JSON object within a 100,000 character size bound, that your two settings sit inside disclosed guard rails (minimum words per beat 10 to 300, how-it-works points 1 to 10; a malformed setting falls back to its default), that the map's productName and tagline exactly match the product name and tagline you provide (after trimming surrounding whitespace), that the beats array contains exactly the nine named beats in the book's canonical order (protagonist, struggle, conflict, value_proposition, team, product, better_than_competition, traction_market, tagline_reprise), that every beat carries a non-empty label and a prose block of at least your minimum word count (default 40), that the product beat carries exactly your chosen number of non-empty how-it-works points (default 3), that the traction_market beat's prose contains at least one digit, and that the tagline_reprise beat's prose contains your tagline, matched ignoring letter case. STUD does NOT verify that the story is compelling, accurate, or persuasive: label checks are presence-only, the word floor measures length not quality, the digit check does not verify your traction numbers are real, and STUD cannot check that the prose actually reflects your product, customer, or problem. What the product does, who the customer is, the problem, and the traction facts you provide are context for the operator, not enforced acceptance criteria.
Get early access to STUD the day it goes live.