We’re the cofounders of Chapter: an open source lead sourcing alternative, purpose-built for developer tools. Instead of throwing your credits to enrich static databases, you get daily leads sent to your inbox in real-time as they mention certain keywords publicly, filtered to match your exact ICP, and fully enriched.
We’re starting with job posts and GitHub as the main two sources for information on tool stack, libraries, engineering size, and more. Since the workflow is triggered through public posts - the data sent is proof that your topic is top of mind for the lead.
Our website is at https://chapter.show and our Github is here: https://github.com/chapter-gtm/chapter
We’re focused on helping dev tool companies with sales for three main reasons:
1) It’s extremely important for dev tool companies to be relevant and genuine in their outreach. Anything else will back fire in short term and long term. Their customers are engineers and quickly see through any fluff. 2) most dev tools we spoke with struggle to sell to mid-market or enterprise (i.e. teams) after relying solely on self serve (i.e. individuals), and 3) existing tools on the market lack “niche” data like tech stack or engineering team size, so teams are stuck piecing together data from different sources - which eats up their time.
Today, sales is often seen as the "dark side," but it doesn't have to be. We believe the systems we need for a brighter future in sales will look nothing like what's out there now. Instead of prioritizing volume, they'll focus on quality and genuine connections. Instead of rigid segmentation and automated sequences, they'll deliver personalized, white-glove experiences based on immediacy and relevance.
We believe this future starts with community, which is why we're making it open source.
We just completed Techstars, and what you see now is about three months' worth of feature development. We realize we still have a lot to learn!
We can see multiple use-cases in the future, like extensibility (both for data objects and workflows), messaging (increasing productivity around individual contacts), and analytics (understanding ICPs based on market, and conversions).
One neat use case that a user is exploring right now is auto-connecting with these ICPs on LinkedIn with the goal of having them enter their orbit and engage with their content. In other words, building an audience of perfect ICPs–low touch, high relevancy.
Chapter is built with Next.js, shad/cn, Tailwind CSS, Litestar and PostgreSQL, and is licensed under AGPL 3. We plan to make money by offering a hosted version.
We’re very eager to get your feedback as we haven’t launched anywhere before this post.
What's your story with dev tools? What should we prioritize next?