Recruitment CRM
Built by a Solo Recruiter for Solo Recruiters
Built in the Trenches. Designed for the Solo Recruiter.
I didn’t start coding because I loved software. I started because I was drowning in it.
For years, my recruitment process was a patchwork of Excel sheets, Outlook inboxes, LinkedIn tabs, and Word templates.
I spent more time copying data, chasing follow-ups, and formatting documents than actually talking to candidates or closing clients.
I paid for SaaS platforms that promised automation but delivered complexity.
I worried about my candidate database living on someone else’s servers.
And worst of all, I knew I was leaving placements on the table simply because the admin work was slowing me down.
The Turning Point
So I did what recruiters do best: I took control of the process.
I stopped looking for a tool that almost fit my workflow and built one that exactly matches it.
What I Built
The result is a desktop-first, local-AI Recruitment CRM.
No monthly cloud subscriptions. No data leaving your machine. No bloated features you’ll never use. Just a clean, powerful system that handles the repetition so you can focus on relationships, judgment, and placements.
1-Click Sourcing → Import profiles directly from LinkedIn
Local-First AI Matching → Ollama + BGE-M3 run on your hardware. Zero cloud dependency.
Quality-Gated Pipeline → Move candidates only after adding real evaluation notes
Auto-Generated Candidate Profiles → Stage 4 triggers a polished, client-ready email with AI summaries & attachments
Smart Email Campaigns → Drip sequences with AI response interpretation (Manual / Semi / Full Auto)
Offline Invoicing & Revenue Tracking → From placement to payment, all logged locally
Proof It Works
I didn’t launch this in a vacuum.
I tested it on my own desk, with my own clients.
Last month, I imported a candidate’s profile with one click. The local AI matched him at 89% against an active job.
I moved him through quality-gated stages, added interview notes, and at Stage 4, the system auto-generated a professional candidate presentation email.
The client called the next day. The candidate was hired on the spot.
Time saved on admin: ~80%.
The Philosophy
This isn’t about replacing recruiters with AI. It’s about amplifying them.
You bring the intuition, the network, and the deal-closing skill.
The software handles the parsing, the matching, the follow-ups, and the paperwork.
Your data stays yours.
Your workflow stays yours.
Your margins stay yours.
1 Comment
You have already found the wedge most founders in your space never will, and your post proves it: local-first AI. "Ollama and BGE-M3 running on your own hardware, zero cloud, candidate data never leaves your machine" is a genuinely uncopyable position, because Bullhorn and every venture-funded cloud CRM structurally cannot match it, their whole model is your data on their servers and a monthly bill. In a world of GDPR and candidate PII fear, "the AI runs on your machine and your database never leaves it" is the sharpest thing you can say. Lead with it, not "Recruitment CRM."
Your closing triple is the manifesto, so use it as the hero: your data stays yours, your workflow stays yours, your margins stay yours. That is a stance, not a feature list, and it is the exact stance the incumbents cannot take without cannibalizing themselves. Pair it with the built-by-a-recruiter proof, because a tool made by someone who actually sourced candidates is a trust signal a product team cannot buy.
One honest tension to decide on purpose, because the wedge and the ceiling are the same feature: local-only is perfect for the solo recruiter and it breaks the moment you want two recruiters sharing a pipeline. So own the solo, do not drift toward cloud and team features that would quietly dissolve the "your data never leaves" promise that is your whole identity. And get ahead of the one fear local invites, "what if my laptop dies," by making backup and export trivially easy and saying so loudly, the same way you say the data never leaves. One question: is your buyer the solo recruiter who wants ownership, or the small agency that wants collaboration? Because you can only build the hero for one.