DROPFind unhappy users of a competitor on X
Find unhappy users of a competitor on X from public complaints and switch posts — then decide if they fit you.
Short answer. Unhappy users write what broke. DROP surfaces those public posts around a rival’s site. You still decide if their job matches your product.
Anger is not always a fit
Someone furious about pricing may still need an enterprise feature you do not have. Read the job, not just the sentiment face.
Check whether the complaint is still unresolved
A complaint can be a resolved support issue, a joke or a request for a capability you do not offer. Read the thread and author’s constraints before deciding whether you can help. Sentiment alone does not establish willingness to switch.
Filters are for the chart and the list
On DROP, sentiment filters change both the timeline and the cards. Use them to work one mood at a time.
Use a switch-readiness checklist
Check whether the author uses the named product, the problem remains unresolved, a change is being considered, and the required capability exists in your product. Mark each field supported, contradicted or unknown with a source. A single unknown may justify a respectful question; it does not justify labelling the author ready to buy.
Frustration without switching fit
Illustrative exercise — not a real customer result.
Worth checking: “Our tool is expensive and we need SSO” states both dissatisfaction and a requirement.
Do not count: If your cheaper product lacks SSO, the negative tone does not make the author a suitable lead.
Next step: Keep the complaint as research; approach only if your current capabilities satisfy the requirement.