Operations automation studio · n8n, Airtable, Supabase, Next.js

Five systems, four sectors, one method.

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.

The five systems

SystemWhat it doesStateOpen
AutoRecruit The whole hiring pipeline in one recruiter portal, backed by eight n8n workflows. LIVE · 8 OF 8 →
AutoClose Capture through close in one platform. PRODUCTIZED BUILD →
Cold email engine Seven interlocking workflows that bound sending reputation by design. LIVE · 7 OF 7 →
Recruitment retrieval layer A retrieval-grounded email system rather than a chatbot bolted onto an inbox. DELIVERED →
Sponsor sourcing pipeline 249 prioritized local businesses for a creator to pitch, delivered with contact and social details, at roughly a cent of API spend per business. DELIVERED →

Note

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.

Specification sheets

AutoRecruit

Live

The whole hiring pipeline in one recruiter portal, backed by eight n8n workflows. Built so a confidently wrong automated rejection cannot happen quietly.

Sector
HR and recruitment
Stack
n8n · Sheets · LLM
Workflows
8 of 8 active
Source
Own build, redacted set
Read the AutoRecruit case
AUTORECRUIT / PORTAL / APPLICANTSDEMO DATA
AutoRecruit applicants dashboard with candidates tracked across hiring stages
FIG. 01 Applicants tracked across stages, with filtering by stage and position. Candidate details are redacted; the records shown are test data.
Seeded demo data. Nothing on this screen is a client result.

AutoClose

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.

Sector
Sales operations
Stack
n8n · SMS · Email · Voice
Data shown
Seeded demo data. Nothing on this screen is a client result.
Source
Own build, redacted set
Read the AutoClose case
AUTOCLOSE / CONSOLE / REPORTSDEMO DATA
AutoClose reports view with response rates broken down by channel
FIG. 02 Response rates by channel, computed by the system instead of assembled by hand. Figures are seeded demo content.
Seeded demo data. Nothing on this screen is a client result.

Cold email engine

Live

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.

Sector
B2B lead generation
Stack
n8n · SMTP · Sheets
Workflows
7 of 7 active
Source
Own build, redacted set
Read the cold email case
COLD EMAIL / N8N / WORKFLOW LIBRARYLIVE
n8n workflow library listing the seven cold email workflows, all active
FIG. 03 The library: all seven workflows active, from sourcing to reply handling.

Recruitment retrieval layer

Delivered

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.

Sector
HR and recruitment
Stack
n8n · Supabase · Cohere
Design
Answers trace to a source
Source
Own build, system drawing
Read the retrieval layer case
RETRIEVAL LAYER / SYSTEM MAPDIAGRAM
CLASSIFY EMAIL FRONT DOOR PARSE QUESTIONS ONE OR MANY HYBRID SEARCH SEMANTIC + KEYWORD RERANK BEST SOURCE WINS ANSWER RATIO GATE ALL OR ESCALATE COMPLETE PARTIAL SEND REPLY SOURCE ATTACHED ESCALATE A PERSON ANSWERS
FIG. 04 The complete-or-flagged design: a partial answer never goes out dressed as a full one.

Sponsor sourcing pipeline

Delivered

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.

Sector
Creator sponsorship
Stack
Python · Apify
Spend
$2.87 against a $5 ceiling
Source
Client delivery, system drawing
Read the sourcing pipeline case
SOURCING PIPELINE / SYSTEM MAPDIAGRAM
SEARCH SPACE CITIES x TERMS PULL DATA UNDER A $ CAP ENRICH OWN SITE, FREE CLASSIFY NAME, NOT TERM PRIORITIZE DEDUPED LIST THE CAP IS AN ARGUMENT TO THE RUN, NOT A HOPE.
FIG. 05 Five stages, re-runnable. New cities or categories are a config change, not a rebuild.