DROPHow to do competitor research on Twitter / X
Do competitor research on X by reading their users, not their launch tweets. DROP starts from the rival’s site.
Short answer. Competitor research on X is a user-research pass. Paste the rival. Read complaints, comparisons, and workarounds. Write down the job, not the feature list.
Skip the announcement thread
Launch posts are marketing. The replies and the unrelated complaints are research.
Capture the sentence they would pay to end
If you cannot quote the pain in their words, you do not have a finding yet.
Compare only after both sides have posts
DROP’s compare is one reading on the same radar after you add your product. It is not a feature matrix generator.
Produce a traceable theme table
Use one row per theme with source URLs, publication dates, distinct author count, observed constraint and counterexample. Separate a pricing complaint from a missing integration or resolved support incident. Note the sample window and source failures in the brief. This table describes collected evidence; it cannot establish market prevalence or a competitor’s private customer list.
Research the workflow, not only the complaint
Illustrative exercise — not a real customer result.
Worth checking: Read descriptions of how users approve work, share results and migrate data around a rival. Preserve the task and source.
Do not count: An isolated complaint without context cannot justify a roadmap change.
Next step: Group distinct observations by workflow and record counterexamples from users whose needs your product does not meet.