The stall you're describing is the difference between users who think your tool is clever and users who have a problem painful enough to pay for solving it.
The most consistent pattern I've seen work: solve a problem developers already know they have, in a workflow they already use daily. Not "you should care about X" but "you already care about X and it's annoying - here's a faster way."
The dead ends are usually targeting problems developers don't feel yet. You can have a technically superior testing framework, but if the team's current setup "works fine" (even if it's objectively worse), there's no urgency to switch.
The narrow ICP approach works when it's narrow enough that you can actually list the companies. Not "Series A SaaS companies" but "these specific 30 companies using this exact tech stack with this known pain point." At that scale you can do real research on each one and outbound becomes viable.
The integrations play is interesting - it works when you're solving a gap in an ecosystem people are already bought into. Building a better Slack bot is hard. Building a tool that makes Datadog + PagerDuty work better together has a clearer value prop to people already paying for both.
One thing that seems underrated: finding where your ICP already hangs out and being genuinely helpful there without selling anything. Not "build in public" as content strategy, but actually solving problems in public. The conversion comes from "oh, the person who helped me with that gnarly bug has a product" not from announcement posts.
The stall you're describing is the difference between users who think your tool is clever and users who have a problem painful enough to pay for solving it.
The most consistent pattern I've seen work: solve a problem developers already know they have, in a workflow they already use daily. Not "you should care about X" but "you already care about X and it's annoying - here's a faster way."
The dead ends are usually targeting problems developers don't feel yet. You can have a technically superior testing framework, but if the team's current setup "works fine" (even if it's objectively worse), there's no urgency to switch.
The narrow ICP approach works when it's narrow enough that you can actually list the companies. Not "Series A SaaS companies" but "these specific 30 companies using this exact tech stack with this known pain point." At that scale you can do real research on each one and outbound becomes viable.
The integrations play is interesting - it works when you're solving a gap in an ecosystem people are already bought into. Building a better Slack bot is hard. Building a tool that makes Datadog + PagerDuty work better together has a clearer value prop to people already paying for both.
One thing that seems underrated: finding where your ICP already hangs out and being genuinely helpful there without selling anything. Not "build in public" as content strategy, but actually solving problems in public. The conversion comes from "oh, the person who helped me with that gnarly bug has a product" not from announcement posts.