Chapter
Chapter: Open Source GTM for Developer Tools.
Install / Use
/learn @chapter-gtm/ChapterREADME
<br /> Chapter finds highly relevant leads based on your exact "niche" search criteria (e.g. OpenAPI, REST API, SDKs, release frequency, engineering team size, public facing developer docs, etc), and delivers contacts and evidence on why they are relevant. <br /> <br /> <img width="100%" alt="flow-chart" src="https://github.com/chapter-gtm/chapter/blob/main/assets/images/chapter-agent-flowchart.png">[!IMPORTANT] Development on this project is paused indefinitely until further notice.
Chapter is the 1st open source GTM tool designed for developer tool companies. We believe that developer tools should have a new kind of sales tool that enables them to sell to mid-market and enterprise–one that requires no additional research, and provides a broad set of niche data points (specific to developer tools, e.g. tool stack, libraries, github activity, etc). Finally you can scale relevant outbound with trustworthy and relevant data. Your recipients will thank you.
About the Project
<img width="100%" alt="product-screenshot" src="https://github.com/chapter-gtm/chapter/blob/main/assets/images/github-chapter-screenshots.png">Chapter - Lead research, purpose-built for developer tools
It takes 1 minute to create an AI agent that researches for relevant leads matching your exact search criteria around the clock. Get daily leads in real-time based on a wide variety of triggers, and evidence on why they matter.
Built With
Quick Start
To quickly get a development environment running, run the following:
make install
. .venv/bin/activate
Local Development
cp .env.local.example .env
pdm run start-infra # this starts a database and redis instance only
# this will start the SAQ worker, Vite development process, and Litestar
pdm run app run
# to stop the database and redis, run
pdm run stop-infra
Docker
docker compose up
Note: This project integrates with third-party APIs. You will need to obtain the necessary API keys for these services and update them in your .env file. For example, see the provided .env.docker.example file for the required format.
Contributing
We <3 contributions big and small:
- Submit a feature request or bug report
