Production patterns,
rebuilt in the open.
Each of these systems already runs in production — their full breakdowns are in Work. The lab versions are sanitized rebuilds I'm publishing so the code itself can be read.
- Proven in production
- The pattern itself runs in a live system. Each card links to it.
- Public rebuild in progress
- A sanitized version is being written. The public code isn't ready yet.
- Public rebuild queued
- Not started. "In progress" or "queued" never means the pattern is unproven.
Enrichment Waterfall
Fills in missing contact data by trying one provider, then falling back to the next — so incomplete records get completed and you only pay for lookups that work.
Runs in production as the enrichment stage of the outbound pipeline.
> reading raw_contacts.csv...
Procurement Signal Harvester
Watches public procurement and tender sources, and turns announcements into structured, CRM-ready records — instead of someone finding them by accident.
Runs in production as automated tender discovery inside the CRM.
Inbound Signal Router
Takes an incoming lead, applies routing rules to decide who owns it, updates the CRM and alerts the team — in seconds, not next-morning.
The same event-driven pattern powers the production approval-to-send flow.
LLM Account Qualification
Scores a company against a written ideal-customer profile and returns structured JSON with its reasoning. A human still makes the final call — by design.
Runs in production as the AI qualification stage of the lead pipeline.
"reason": "fleet and procurement signal present" }
The same patterns, under bigger systems.
Enrichment and qualification sit inside the lead-generation console. The signal harvester's collect, de-duplicate and review loop also runs under tender discovery, a procurement research pilot and a job-discovery tool.
The small panels inside each card are interactive illustrations of the pattern, not live connections to production data.