Write · Create · Writing & Content
Problem definition document
A problem definition document with the market, buyer roles, and per-problem definition, metrics, prior solutions, buying authority, and a 1-10 severity.
You receive: A structured PDD (one block per problem) that passes the completeness checks.
Part of Validate Demand
Example
A sample of what this play produces. Your result is generated for your inputs.
Industry
AI agents and agent-delivered knowledge work
Market size
AI agents market approximately $8B in 2025, growing 42-50% CAGR (cited external estimate)
Buyer roles
- Solo founder
- Early-stage founder
- Small product team lead
- Ops lead adopting agents
- Engineering lead adopting agents
Problems
- Definition
- Getting real work out of AI is still manual craft: every task needs an expert prompt, the business context re-supplied by hand, and the output carried into the right place afterward. The hours the intelligence saves get spent operating it, and on a small team that operator is the founder.
- Metrics
- Minutes of prompting, context-supplying, and rework per finished artifact
- Share of AI sessions that restate company facts already written down elsewhere
- Percent of AI output used as delivered, without manual reshaping
- Prior solutions
- Prompt libraries and saved system prompts
- Custom GPTs and per-tool instruction files
- Hiring a consultant or operator to run the tools
- Copy-paste pipelines between chat tools and documents
- Buyer authority
- The founder or budget-holding team lead approves the spend directly; on solo and early-stage teams the economic buyer and the user are the same person.
- Rating
- 9
- Definition
- A venture's knowledge goes stale the moment it is written down. Facts live scattered across chat threads, decks, and planning docs; when one changes, nothing downstream updates, so the venture's own materials quietly diverge from reality and every new piece of work starts from an out-of-date picture.
- Metrics
- Age of the oldest business fact still being pasted into new work
- Number of places the same fact is maintained by hand
- Share of documents contradicting a current fact at any given audit
- Prior solutions
- Wikis and knowledge bases maintained by hand
- Quarterly document review rituals
- A single operating doc that one person keeps current
- Buyer authority
- Scope decisions sit with the founder or the commissioning lead, the same person who holds the budget and owns the venture's source-of-truth documents.
- Rating
- 7
- Definition
- Buyers with a fuzzy outcome in mind cannot turn it into a well-scoped, checkable unit of work. Scoping is a skill; without it the buyer either over-specifies and pays for rigidity, or under-specifies and gets work that misses the intent.
- Metrics
- Time from first stated outcome to an agreed, checkable spec
- Share of inbound requests abandoned before any work is commissioned
- Percent of delivered work rejected for missing the intent rather than failing the spec
- Prior solutions
- Engaging a consultant or agency to scope the work first
- Templated brief and spec generators
- Trial-and-error prompting until the output looks right
- Buyer authority
- The commissioning lead scopes and approves; for a run paid from credits already held in a prepaid pack the same person can act without a second approval.
- Rating
- 6
Opens soon
Cost50 credits
ProtectionSpent when the run starts · returned only if STUD is at fault
STUD opens runs for everyone soon, on every play at once.
Get early access to STUD the day it goes live.