Internal build
A prospecting copilot we built for ourselves
Internal · WishBuilt business development
Before
Every prospecting session started from zero—no signals, no context, no queue of next actions.
After
Sessions start with a ranked list of reasons to contact specific companies, grounded in real signals.
What was stuck
Prospecting happened in bursts, then stopped whenever delivery got busy.
No systematic way to notice buying signals. Every outreach message started from a blank page.
The pipeline lived in memory.
- 01Understand
- 02Design
- 03Build
- 04Measure
01Understand
The bottleneck wasn't effort—it was that every session started from zero: no accumulated signals, no reusable context, no queue of next actions.
Success definition: a working session should start with a ranked list of reasons to contact specific companies—not with a search box.
02Design
A small internal application: signal collection from public sources, a "why now" layer, AI-assisted drafting grounded in the signal (human decides, never auto-send), and a lightweight pipeline view.
03Build
Built as a small web app in days—the same fast, focused build approach we use for clients. API keys and integrations run server-side.
Measure
Metrics agreed upfront
- Sessions start warm instead of cold
- Outreach references something real about the company
Prospecting sessions start warm instead of cold. Outreach references something real about the company instead of a template.
Definition of done: Concrete tracking will be added once the tool has been in daily use long enough to measure honestly.
In one line
The same sequence—understand the bottleneck, design the smallest system that removes it, build it fast, measure it honestly—applied to our own business development.