Dev.to
Dev.to threads where people ask for the tool you are building
IntentRat reads Dev.to every 15 minutes and scores each thread for buying intent.
What a lead looks like there
What do you use for a status page on a small budget?
Customers keep asking for uptime history, and right now we only have a spreadsheet.
Draft reply
At this size a static status page that the monitor updates is usually enough. Which monitor are you pointing it at?
Edit it, then post it yourself.
What IntentRat reads on Dev.to
Article comments
Public comments on the articles of the tools and stacks your buyers read.
Questions about the setup
Comments asking which tool the author uses for a job the article describes.
Threads about a missing piece
Comment threads where two people build the same small thing by hand.
The labels you see on Dev.to
Pain point and recommendation request are the labels you will see most on Dev.to.
The person says they are looking for a way to solve this now. A budget or a deadline is often close by.
The person is unhappy with the tool they use and is shopping around for something else.
The problem is described clearly, but nobody said they are buying yet. Worth a reply; the close comes later.
The person names the tool they use and says what it fails at. That gap is yours.
An existing product almost does the job. Someone is telling you what to build.
The thread asks the community for a recommendation. Reply early and you set the category.
Somebody praises a tool in public. Useful to know, rarely a lead.
Score = fit to your brief (0 to 100). Example data.
Add your product.
Paste your website and see the leads of the last seven days, free, before you pay.
Free lead preview · 7-day money-back guarantee
- Hacker News
- GitHub
- Bluesky
- Dev.to