Technical deep-dive

Automations for various ventures.

Workflow automations built for clinical, logistics, sales, journalism, and marketing teams.

A lot of the work I do never ships as a product — it ships as a quiet pipeline that runs every hour and saves somebody a day of manual work each week. This page collects automations I've built across five very different verticals. The shape of the work is the same everywhere: find the boring, error-prone seam between two systems (or between a human and a system), and replace it with something deterministic that fails loudly when it does fail. The verticals below describe the kinds of automations I've shipped, anonymized but real.

Node.jsPythonFlowWiseOpenAI Agent SDKOpenAI APILangChainPostgreSQLAWSSalesforceZendeskSAPIntuit QuickBooks
  1. 01

    Neuropsych Clinical Reports

    Clinical

    A per-section pipeline that turns raw neuropsychological assessments and clinician transcripts into structured, deidentified reports — with evals at every step and a human in the loop wherever the model isn't sure.

    Backed by Y Combinator
    • Ingest & Deidentify: Raw assessments and transcripts come in via OCR and the Extend API, get deidentified with Presidio, and land as a normalized JSON document per case
    • Section Pipeline: A dedicated sub-pipeline per report section — each runs extraction, standardization, and formatting against that section's schema
    • Step-Level Evals: LLM-as-judge against a mix of distilled and raw context for grounding, plus deterministic checks on formatting and required-field presence — every step is scored before it can advance
    • HITL Dashboard: Surfaces each step's output and flags low-confidence spans for clinician review before anything leaves the system
  2. 02

    Logistics & Procurement Ops

    Logistics

    Operations and revenue-side automations for a logistics business — pulling four separate systems into one dashboard, tracking procurement state through email instead of rigid status updates, and feeding cold leads in from the open web.

    Client logoBelcastro Group logo
    • Unified Ops Dashboard: Internal dashboards that pull ServiceCore (field service), SAP (ERP), QuickBooks (accounting), and Extensiv (3PL / warehouse) into a single operational view — one place to see order, fulfillment, and financial state side-by-side instead of swiveling between four systems
    • Procurement Tracker: Mailgun ingests every email CC'd to the pipeline mailbox, OpenAI classifies each thread into a procurement stage (inquiry → quote → PO in SAP → invoice in SAP → shipping confirmation → delivered in Extensiv → payment reconciled in QuickBooks), and the oversight dashboard reconciles AI-inferred state against the systems of record so any drift surfaces immediately
    • Cold-Lead Enrichment: Scrapes target sources through Bright Data, dedupes against the existing book, and pushes structured contacts into HubSpot and Salesforce with first-touch metadata pre-filled
  3. 03

    Sales & Revenue Ops

    Sales

    Built in close partnership with the CFO and CEO of a company managing the web presence of 10,000 medical practices. Three workflows aimed at the parts of the revenue org that were eating the most human time — exec reporting, ticket triage, and SDR prospecting.

    Client logo
    • Exec Sales Reports: Pulls live numbers from Salesforce, joins context from Google Sheets and Docs, and ships a formatted brief into the executive's email or Slack (DM or channel) on a schedule. Replaced hours of weekly hand-rolled reporting for the CEO
    • Ticket Classifier: LLM-driven Zendesk ticket router that categorizes inbound tickets by language required, estimated skill level, and current agent backlog, then assigns or recommends. Low-confidence cases defer to a human dispatcher instead of being auto-assigned
    • SDR Lookup Extension: Browser extension for SDRs working cold lists — when the rep lands on a prospect's site, the extension looks the company up in Salesforce in the background. If it exists, last-contact context appears inline; if not, a quick-input form pre-fills a new record. Cuts the lookup-or-create cycle from minutes to seconds
  4. 04

    Marketing content

    Vertical

    Automations for content teams shipping across many channels — turning a single brief into coordinated assets with brand-voice constraints baked in.

    • Brief-to-Draft: Takes a structured brief and produces blog, social, and email drafts that share a single voice and CTA
    • Asset Orchestrator: Ties image and video generation to the copy, gated on a brand-review step before anything is published
    • Performance Loop: Pulls post-launch metrics and feeds them back as constraints on the next brief — what worked, what to avoid
Automation

What makes an automation hold up

A demo automation and a production automation are very different artifacts. The demo runs once on clean data; the production one runs every hour for two years against whatever the world throws at it. These are the things I optimize for so the second one keeps working.

Primary metrics

Hours returned per week

The honest unit of value. Measured against the manual workflow it replaced, averaged over a few weeks to wash out novelty effects.

Error rate vs. the manual baseline

Automation has to beat the human floor, not perfection. I compare error rates against what the manual process actually produced — including the errors nobody was counting.

Secondary signals

Handoff fidelity

Most automations don't replace a human — they hand off to one. The data that lands on the human's desk has to be clean, structured, and easy to act on, or the automation just moves the work around.

Graceful failure

When an upstream API changes shape or a webhook drops, the automation should fail loudly and stop — not silently write bad data for a week. I default to fail-closed, with alerts pointed at someone who can act.

Auditability

Every run leaves a trail a non-technical operator can read. What it saw, what it decided, what it sent. This is what turns an automation from a black box into something a team will actually trust.

More

Want the rest of the story?

The non-technical write-up lives on the work page. If you're building something in this space or want to dig deeper into any of the stages above, get in touch.