Build · Create · Analysis & Finance

Customer profile

A ranked customer profile for one segment: the jobs your customer is trying to get done, the pains in their way, and the gains they want, every entry carrying a high, medium, or low rank so the profile states priorities instead of listing everything equally.

You receive: A JSON object: customerSegment (a phrase naming the segment), customerJobs (array of {job, importance}), customerPains (array of {pain, severity}), customerGains (array of {gain, relevance}). Ranks are high, medium, or low; each section names at least one high.

Part of Validate Demand

What's verified: STUD verifies the deliverable parses as a JSON object with a customerSegment phrase of at least two words and the three sections present as arrays (customerJobs, customerPains, customerGains), that every entry is an object whose text field (job, pain, or gain) is a phrase of at least two words and whose rank field (importance, severity, or relevance) is exactly high, medium, or low, that each section meets its minimum count of qualifying entries (your intake settings, default 3 each), that each section names at least one high-ranked entry, that no section repeats an entry (ignoring case and surrounding spaces), and that no em or en dash appears anywhere. Checks run in order and a structural failure stops the run there. STUD does NOT verify that the jobs, pains, gains, or their ranks are true for your customers: your intake answers brief the operator and are never machine-checked against the content.