North America · 2025 to now

AI command center for a two-business owner

The automation backbone for an owner running two businesses, one of them handling health data.

  1. 112workflows in production, June 2026
  2. 27permissioned actions, every one logged
  3. 1,857records migrated, zero lost

The problem

More than twenty tools that did not talk to each other, work done by hand across two businesses, and health data that has to stay protected.

What I built

  • One command router over 20+ services, with 27 actions that are permissioned, risk-tiered and logged.
  • Four surfaces in daily use: a web dashboard, Slack, a custom GPT, and a phone line with an AI voice and warm transfer.
  • Health fields masked in view, a kill switch, and two-person approval for risky actions.
  • Daily encrypted backups with restore drills, and hosting moved for data residency.

What changed

  • 112 workflows running in production as of June 2026.
  • 1,857 records moved between systems with zero loss.
  • The intake desk opens the dashboard every working day. Staff trained, SOPs and runbooks written.
An operations dashboard with an audit feed, an approvals queue, a masked contact card and a kill switch, sample data.
The dashboard: audit feed, approvals, masked contact card, kill switch.
A two line business phone console with an active call, voicemail transcripts and a message thread, sample data.
The phone line: two numbers, AI answering, warm transfer.
A migration reconcile panel showing source and destination counts matching, sample data.
The migration check: every record counted on both sides.

Recreated from the live system, client details removed.

Tools

  • n8n
  • Airtable
  • Twilio
  • VAPI
  • Slack
  • Lovable
  • QuickBooks Online
  • Google Workspace
  • Cloudflare