The range is the point: hiring, sales, outreach, sourcing. The same discipline transfers because the failure modes are the same everywhere: silent duplicates, unbounded spend, confident guesses, and nobody able to say what actually ran.
| Idx | System | State | |
|---|---|---|---|
| 01 | AutoRecruit | LIVE 6/8 | → |
| 02 | AutoClose | PRODUCT | → |
| 03 | Cold email engine | LIVE 7/7 | → |
| 04 | Recruitment retrieval layer | BUILT | → |
| 05 | Sponsor sourcing pipeline | DELIVERED | → |
Two of these are recruitment systems that solve different problems: AutoRecruit moves candidates through a pipeline; the retrieval layer answers questions from a grounded knowledge base. Three of these are my own builds, one is a productized build, and one was a client delivery; each page says which.
LIVE · 6 OF 8 WORKFLOWS ACTIVE
The whole hiring pipeline in one recruiter portal, backed by eight n8n workflows. Built so a confidently wrong automated rejection cannot happen quietly.
Read the AutoRecruit case
PRODUCTIZED BUILD
Capture through close in one platform: AI lead scoring, automated multi-channel follow-up, integrated scheduling, and a complete interaction history per lead.
Read the AutoClose case
LIVE · 7 OF 7 WORKFLOWS ACTIVE
Seven interlocking workflows that bound sending reputation by design: hard daily quotas per inbox, one sender per prospect, follow-ups timed in business days, and sequences that stop on reply.
Read the cold email case
BUILT · ANSWERS TRACE TO A SOURCE
A retrieval-grounded email system rather than a chatbot bolted onto an inbox. Hybrid search plus reranking over a curated knowledge base, and a question with no source gets flagged to a person instead of an invented answer.
Read the retrieval layer caseDELIVERED · $2.87 SPEND AGAINST A $5 CEILING
249 prioritized local businesses for a creator to pitch, delivered with contact and social details, at roughly a cent of API spend per business. The cost ceiling was passed in at runtime, so an expanded run cannot surprise anyone with a bill.
Read the sourcing pipeline case