Draft · Create · Writing & Content
'Who desperately needs this' target-user statement
A specific target-user statement: the segment, their acute pain, how often it bites, today's workaround, and why now.
You receive: A JSON object { segment, acute_pain, frequency, current_workaround, why_now } checked for a specific (non-generic) segment and substantive fields.
Part of Validate Demand
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [],
"checkNames": [
"parses_json",
"segment_specific",
"pain_is_acute",
"frequency_present",
"workaround_present",
"why_now_present",
"no_em_dash"
],
"constants": {
"_YC_BANNED_GENERIC": [
"all businesses",
"all companies",
"anyone",
"businesses",
"companies",
"consumers",
"customers",
"developers",
"enterprises",
"everybody",
"everyone",
"people",
"small businesses",
"smbs",
"startups",
"the world",
"users"
],
"_YC_EM_DASHES": [
"—",
"–"
]
},
"deliverableLabel": "yc_target_user_statement",
"documentKeys": [],
"enumLiterals": [],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Example
A sample of what this objective produces. Your result is generated for your inputs.
Segment
Engineering and ops leads at mid-size SaaS companies who are deploying autonomous AI agents into production workflows (support triage, code changes, data pipeline tasks).
Acute pain
They cannot trust or prove that an agent actually did the work correctly, so every agent output has to be manually spot checked before it can be shipped or paid for, which erases the time savings the agents were supposed to deliver.
Frequency
It bites on every agent run that touches a customer-facing or revenue-impacting system, multiple times per day per workflow.
Current workaround
They wrap agents in homegrown logging plus human review queues, screenshot or copy outputs into spreadsheets, and rely on after-the-fact incident postmortems when an agent silently fails.
Why now
Agent adoption is outpacing any way to verify agent work, and buyers are starting to refuse to pay for or rely on agent output they cannot independently audit, so a marketplace that makes agent work verifiable removes the trust blocker holding back deployment and payment.
Get early access to STUD the day it goes live.