What are people asking for
Say "what are people asking for" and get the Problems your signups named, ranked by revenue at stake, with quotes and who said each.
Read what your signups said, grouped by the Problem they named. The ranking puts the problem people would pay to fix first.
Needs Find out if anyone wants this
What you get
- 1list of Problems, revenue at stake firstProblem
- 1quote per Problem, in the person’s own wordsEvidence
- 1count of who said it, each linked to their LeadLead
- 1tool they use today, per ProblemProblem
- 1query behind the ranking, shown beside itCollection
Your agent does
You, to your agent
What are people asking for?
What did signups say?
Which problems come up most in the interviews?
# Problem.rank
curl -X POST https: //api.sb/ leaseline.app/ problems/ rank \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
-H "Content-Type: application/ json" \
-d '{"icp": "icp_1"}'
import { $ } from 'startup-builder'
await $.Problem.rank({ icp: 'icp_1' })
npx startup-builder do Problem.rank --json '{"icp": "icp_1"}'
{
"name": "do",
"arguments": {
"code": "return await $.Problem.rank({ icp: 'icp_1' })"
}
}
The same sentence does more as the business grows:
| State | Calls | Asks first |
|---|---|---|
| Idea | Problem.rank | |
| Live | Problem.rank, Issue.schedule | Put the top one in next week’s work? |
| Repeatable | Collection.query, Problem.rank | Paying customers only, or everyone? |
Change it
- Show only people who said they would pay.
- Compare this week with last week.
- Email the top ten people to book a call.
Under the hood
- Systems
- Discovery, Surveys, Waitlists
- Nouns
- Problem, Evidence, Lead, ICP, Interview
- Events
Problem.ranked
Problem.rank orders Problems by revenue at stake, the strength of their Evidence and the effort to fix them. A quote from someone who would pay outranks ten from people who would not.