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.
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.
Opens soon
Cost20 credits
ProtectionHeld until verified delivery
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
Product Name
Fieldnote
Tagline
Notes that turn into next steps.
Beats
Beat Idprotagonist
LabelMeet the protagonist
ProseMaria Alvarez spent nine years running field inspections for a regional utility company, driving from substation to substation with a clipboard, a voice recorder, and a stack of carbon-copy forms. She trained a dozen new inspectors during that time and watched nearly every one of them stall out on the same problem during their very first week on the job: turning a messy stack of handwritten notes into a clean list of repairs the crew back at the office could actually act on.
Beat Idstruggle
LabelThe daily struggle
ProseEvery evening after her last site visit, Maria sat in her truck for another forty minutes typing up the day's notes before she could drive home, because if she waited until morning half the details were already gone from memory. The other inspectors on her crew did the same thing, some of them staying at the office past seven most nights just to keep the paperwork from piling up into an unmanageable backlog that nobody wanted to touch on a Friday.
Beat Idconflict
LabelThe breaking point
ProseThe breaking point came the week a transformer failure got missed because the handwritten note describing it sat buried on page six of a field notebook that never made it into the work order queue until eleven days later. The utility took an unplanned outage that cost real money, and Maria's manager asked her, in front of the whole team, why a company running on nine-year-old paper processes was still trusted with critical infrastructure at all.
Beat Idvalue_proposition
LabelThe value proposition
ProseMaria decided the fix could not be another form or another app that asked field workers to type more than they already did, so she built Fieldnote around the one thing every inspector already carries: their own voice. Speak the note in plain language while still standing at the panel, and Fieldnote turns that recording into a structured, assignable task before the truck even leaves the site, cutting the gap between observation and action down to seconds instead of days.
Beat Idteam
LabelThe team behind it
ProseMaria left the utility and brought two people with her: Devon Park, a mobile engineer who had spent six years building offline-first apps for construction crews, and Priya Nair, a former field supervisor who understood exactly which parts of an inspection report actually mattered to the people reading it later. The three of them spent the first four months of Fieldnote riding along on real inspections instead of sitting in an office writing specs nobody in the field had asked for.
Beat Idproduct
LabelThe product
ProseFieldnote is a mobile app that an inspector opens once at the start of a shift and barely touches again until the drive home. It listens while they talk, tags each spoken observation with the site, the asset, and the timestamp, and turns the recording into a short list of next-step tasks that a dispatcher can assign before the inspector has even reached the parking lot, closing the loop between what was seen and what gets done about it.
Product Mechanics
Voice-to-text capture that transcribes field notes in real time from the phone's microphone, even with intermittent signal
Automatic task extraction that turns a transcribed note into a checklist of next-step actions, each tagged to a site and asset
A sync layer that pushes generated tasks straight into existing work order systems like ServiceTitan and Salesforce Field Service
Beat Idbetter_than_competition
LabelBetter than the alternatives
ProseThe inspectors had already tried the alternatives: generic dictation apps that produced a wall of unstructured text nobody wanted to read, and inspection checklist software that was so rigid it could not capture the one odd detail that actually mattered on a given day. Fieldnote sits between those two failures, structured enough that a task lands in the right person's queue automatically, and loose enough that an inspector can still say exactly what they saw in their own words.
Beat Idtraction_market
LabelTraction and market
ProseEighteen months after Maria, Devon, and Priya shipped the first version, Fieldnote is running with 47 utility and municipal inspection crews across 6 states, processing roughly 12,000 voice notes a month and cutting the average time between a site observation and an assigned work order from three days down to under four hours. Three regional utilities have signed multi-year contracts, and two more are running pilots that started this quarter.
Beat Idtagline_reprise
LabelBack to the tagline
ProseMaria still remembers typing up notes alone in her truck at seven at night, and that memory is why Fieldnote's onboarding screen still opens with the same line the three of them argued over for a week before launch: notes that turn into next steps. It is not just a tagline anymore, it is the actual measure the team uses internally to decide whether a new feature belongs in the product or not.