I build the software, the agents, and the copy that sells it.

An agent that answers every Instagram and Facebook DM in under five minutes, around the clock, and takes the conversation all the way to a booking or a sale. Built to close, not to chat. It replaces a $4k to $8k per month human setter for $27.

• $50,000 in ticket sales for one event, out of DMs
• $2,000 single sale closed end to end in the thread
• $27/mo against $4k to $8k for a human setter
• 26 migrations, RLS on every tenant table

Next.js 16React 19Tailwind v4Supabase RLSMeta Graph APIWhatsApp Cloud APIn8nWhopSentry

The hard part was never the model. It was billing state that tells the truth: webhooks, plus a nightly reconciliation cron that re-pulls every membership from the provider, plus an admin repair tool. Webhooks lie. A reconciler doesn't.

Not an editor. The operational backbone for a video agency: ingest a raw recording, strip silence, filler words, breaths and retakes, cut it into vertical clips, score every clip for virality, caption it against a brand kit, schedule it, publish to five platforms, then attribute what it earned.

• 16 creator workspaces operated on it
• 5 publishing platforms, one scheduler
• 6 always-on daemons behind it
• 1200/1200 requests served during a live deploy

FastAPIPython 3.11Next.js 14SupabaseOracle CloudnginxsystemdRemotion

The part I'm actually proud of: it deploys without dropping a request. Rolling SIGHUP across four uvicorn workers, a blue/green Next.js pair sharing a build dir, a 17-URL smoke gate, and a cron that repairs a build mismatch every two minutes.

Agents that make and take real phone calls. You describe the job, it places the calls, holds the conversation, books into a calendar and writes the outcome back to a CRM. Text agents are forgiving; a voice agent has to hold a turn in under a second or the person hangs up.

• 130 calls placed, 100 completed end to end
• 26% reached a successful outcome
• ~5¢ per call, all in
• Live Stripe billing, real subscriptions

Next.jsVapiTwilioA2P 10DLCStripeSupabaseVercel cronSentry

Built with two others, so to be clear about my half: the billing and subscription enforcement, the campaign engine, the telephony reliability work, and the instrumentation that made failures visible instead of mysterious. The product is a joint venture; the engineering above is what I own.

Film made with no crew, no location and no shoot day, and the motion system that finishes it. Cast a character, clone the read, generate the shots; the graphics that go over the top are authored as a spec file and rendered headlessly, frame by frame, so the same input gives the same output every time.

• 17 generated shots in one film, one character across all of them
• 212 render-verified components across 16 categories
• Same in, same out — the look is a parameter set, not a mood

Higgsfieldimage-to-videovoice cloningThree.jsGSAPRemotionffmpegheadless Chrome

The hard part is continuity, not generation: a model forgets the room between shots, so holding one actor across seventeen of them took a locked character token and a world description repeated verbatim in every prompt. The render side is the opposite problem, solved by measurement rather than taste — and this page runs that same look.

A brain is just memory an agent can search. I feed it everything I know — my notes, how each client talks, what worked and what did not — and it turns that into something retrievable. When the agent needs to act it looks up the relevant pieces first, so what comes out sounds like me and knows the specifics, instead of reading like generic AI.

• 409 conversations run and logged, without me in the loop
• 66 days continuous, starting itself on boot
• 179 communities mapped and scored for fit
• 3 calls booked off threads it opened

PlaywrightMCPpgvectorvoyage-3.5-liteSupabaseTypeScript

Two rules keep it safe: the ledger is the only source of truth, so it refuses to act on a thread where it spoke last; and anywhere the cost of being wrong is a burned account, it drafts for me instead of sending. The brain half is read-only by design — it can answer, never write.