I built ReachLog because I

I built ReachLog because I wanted something simpler for my own outreach.

Most CRMs came with functionality I didn’t need, while still missing things that mattered to my workflow. I wanted to keep track of who I’d contacted, what we’d discussed, whether they’d replied, and when I should follow up. I also wanted it to work with my existing email setup.

So I built a small application around those needs.

ReachLog brings contacts, companies, email conversations and follow-ups into one place. It supports CSV imports with duplicate checks, searchable contact lists, drafts and templates, and an overview of outreach activity.

Email integration was a big part of it. You can send through your own SMTP account and sync messages and replies through IMAP. Opening a contact gives you the conversation alongside their details, so the context stays together.

I also included practical things that are easy to overlook: do-not-contact controls, data exports and backups. Those matter when you’re using a tool regularly.

It’s built with Next.js, React, TypeScript and SQLite, runs locally in your browser, and is published on npm.

This started with a specific frustration in my freelance work. Building ReachLog let me turn that into a working tool, with room to improve it as my outreach needs change.

Package and setup instructions: https://www.npmjs.com/package/reachlog

Screenshots show the application with sample data.