Build · Create · Writing & Content

Build a Six-Frame Innovation Storyboard

I get a single structured storyboard document with all six narrative frames filled in (customer, insight, problem, value proposition, how it works, competitive context), each checked against a structural rule (presence, a 40-character content floor, and required phrasing), so my product story is complete in shape and ready to turn into a pitch.

You receive: A JSON object {productName, oneLineVision, frames: [{frame, content, ...frame-specific subfields}]} with exactly the six named frames. Frame-specific subfields: the insight frame carries a whys list (at least your minimum count), the problem frame a howMightWe question (exactly one 'How might we ...?' while the default toggle is on), the value-proposition frame a nowICan statement starting with 'Now I can', the how-it-works frame a steps list of exactly your chosen length, and the competitive-context frame a non-empty currentAlternative and differentiator.

Part of Pitch Investors

What's verified: STUD verifies structure against your frozen inputs: the submission parses as a JSON object and stays under 20,000 characters, exactly the six named frames are present (customer, insight, problem, value proposition, how it works, competitive context) with no duplicates or extras, every frame's content field is at least 40 characters after trimming (a length floor, not a quality read), productName and oneLineVision exactly match the values you provide (or must simply be non-empty if you leave either blank), the insight frame carries at least your minimum number of non-empty why levels, the value-proposition frame has a nowICan statement that starts with 'Now I can' and is at least 20 characters, the how-it-works frame has exactly your chosen number of non-empty steps, and the competitive-context frame names a non-empty current alternative and differentiator. The 'exactly one How might we ...?' problem-statement rule is enforced only while the single-problem-statement toggle is on (it is on by default; when off, any non-empty howMightWe passes). Both count settings must be between 1 and 9 or the submission is rejected. STUD does NOT verify substance or truth: not whether the customer is the right protagonist, whether the insight or its whys are true, whether the value proposition is compelling, or whether the story will resonate with any audience. The target customer, core problem, solution summary, and current-alternatives fields in the intake are context for the operator only and are never checked against the deliverable.