DROPCustomer development on Twitter / X
Do customer development on X by collecting jobs from public posts, then interviewing the authors who already wrote the problem.
Short answer. Customer development is talking to people with the job. On X they already wrote it down. DROP queues those posts so you are not guessing who to @.
The post is the screener
A post can suggest a question worth asking. Verify the author’s task and constraints; a keyword or public question does not establish qualification, budget or permission to contact them.
Ask what they tried
A good next question is “what did you try last week?” That turns a public complaint into a development note.
Thirty days beats a launch day
A longer observation period helps put a viral thread in context. It still describes a sample, not the whole market. Paid DROP monitoring can search up to 30 days within the allowance; the initial preview does not guarantee that full window.
Turn one observation into a learning conversation
Ask permission to discuss the task, then ask what the person tried, what happened and what constraint remains. Avoid asking whether they would buy an imagined feature. Record their answer separately from your interpretation and finish with an agreed next step, if any. Use customer discovery to choose what to test; development follows up with the person.
Test a hypothesis, not a sales label
Illustrative exercise — not a real customer result.
Worth checking: If you think agencies struggle with approvals, ask an author describing that problem what they currently do and what fails.
Do not count: Do not call the author qualified solely because the post contains “approval.”
Next step: Write down evidence for and against the hypothesis. Ask permission before requesting a longer conversation.