Years on the customer side
Phone, email and chat queues. Payment remediation, integration triage, OAuth and webhook debugging, web admin and auth flows. I know where work gets stuck.
I build AI tooling for the operational layer: agentic workflows with a human in the loop, onboarding systems, the glue between systems. Years working directly with customers taught me where work gets stuck. I build what unsticks it.
Phone, email and chat queues. Payment remediation, integration triage, OAuth and webhook debugging, web admin and auth flows. I know where work gets stuck.
n8n hands each ticket to an LLM for triage and a draft reply. A reviewer approves, edits or rejects it in a control room I wrote. Only then does the reply go out.
Measure messy customer exports. An LLM proposes each field mapping with a confidence and a reason. A human approves every one. Dry-run the migration, report readiness.
Implementation tool for bringing an enterprise customer onto a SaaS platform. Measures the exports, has an LLM propose field mappings with a confidence and a reason, puts a human on every approval, dry-runs the migration through the target API, reconciles, and issues a readiness report.
n8n takes the Zendesk ticket, an LLM triages it and drafts the reply, a reviewer approves, edits or rejects it in the Control Room, and the approved reply posts back to Zendesk. Not autonomous, not manual. A human at the one step that matters.
Pulls bank transactions through the Plaid API into Google Sheets twice a week, sorts each one into a budget category, and emails a Sunday report. Passed Plaid's Production review and ran on live data from March to August 2026. The hard part was the data: sign conventions, transfers that look like spending, timezones, a call cap.
I sit with the customer's problem, ship the tooling, and bring the customer's-eye view your roadmap is missing.