Block 0
Auto-Responder
Event-driven email automation with Gmail Trigger and Claude API
M1 – M2
Pipeline Design & Classification
Workflow mapping and AI-powered email classification with structured JSON output
M3 – M4
CRM Integration & Calendar CTA
HubSpot Contact + Deal creation, Google Calendar booking link automation
M5
Multi-Source Ingestion
Outlook/Hotmail as second email source with character sanitization and loop processing
M6 – M7
Enrichment & Lead Scoring
Apollo.io API integration and dynamic lead scoring with HubSpot property updates
M8
Automated Follow-Up
Schedule-triggered pipeline review with AI-generated personalized follow-up drafts
M9
Modular Architecture
Refactored system into specialized workflows: Ingestor, CRM, and Nurture
M10
Contextual Memory (RAG)
Full lead history passed to Claude for coherent, personalized responses across weeks
M11
Autonomous AI Agent
Claude decides actions without IF logic — tools: Ingestor, CRM, Nurture called autonomously
M12
Applied Production Build
Multi-branch pipeline generation system built and validated in live production for a real B2B sales role — Apollo enrichment, AI scoring, HubSpot CRM, and automated outreach drafts
M13
Predictive Lead Scoring & Signal Automation
Weighted 4-factor scoring engine (Fit, Intent, Reachability, Value) built in Clay with real-time funding/news signal monitoring, connected via webhook to n8n for automated high-priority lead alerts
M14
Multi-Source Compliance Signal Enrichment
Three independent, fault-tolerant sub-workflows (openFDA 510(k)/PMA, EUDAMED via its real public search endpoint reverse-engineered through live network capture, and the ClinicalTrials.gov API v2), each invoked by the Orchestrator as its own Execute Workflow call
M15
Production Incident Diagnosis & Repair
Live debugging of a 44-node production workflow — broken canvas wiring, a per-item execution-mode bug silently dropping 80% of each batch's items, missing error handling on expected "no results" API responses, and a cross-service credential mix-up causing 401 errors
M16
Cross-System Autonomous Orchestration
A second autonomous agent, independent of n8n, that keeps a downstream reporting layer (Notion) synchronized with the pipeline's own deterministic business logic (weekly Cycle numbering) — including defining its own scoped write-permission boundary