What you are about to read took us less than 3 hours to put together. Built using Claude Code, and uses Claude Code as a backend (lol, I know).
I have been experimenting with multiple GTM and CRM setups to book more demos with potential customers. They were all super painful to use; most felt very restrictive and basically pushed you to leave your creativity at the door.
So I vibe-coded the sales GTM tool I wanted, it's basically a clean interface for Claude Code running very specific tasks:
1. Enriching leads with very high-quality information - Use Chrome to browse LinkedIn, construct an org chart, see what people are interacting with, etc.
2. Score each enriched lead based on our internal criteria, a lot of which is based on the Founding Sales book.
3. Find the decision maker at each org and reach out to them.
Once we remove 90% of the noise and have a list we should spend our time on, we decided to send out cold emails.
A week later - 10 booked demos! This is insane. Feel free to try it yourself, it's local first, MIT license - https://github.com/chaitanyya/sales - Open an issue, the entire app is heavily vibe-coded and may be a little rough.
It's an interesting one. Every time I speak with engineering teams about reliability and correctness, they all want more of it, yet when it comes to investing in it, it's never really a priority.
More often than not, people test the wrong things; they struggle to even identify the right properties to test.
I question my worldview on this because I don't think it's a particularly difficult problem. There are companies like Antithesis that have done incredible work in this space.
I am building in automated property-based testing, and it's not an easy sell.
