Anthony C.

Is there a manual process eating hours of your team's week? That is what I automate: AI agents that answer and act, LLM pipelines that read, sort and draft, scrapers that pull the data you need on a schedule, API integrations between the tools you already use, and jobs that check their own output and alert you when something breaks. What I have running today: - Qwalify, a live SaaS I built (see Portfolio) on Cloudflare Workers, D1 and KV, with Twilio SMS, Telegram bots, calendar (ICS) sync and LLM-written replies. 297 automated tests run on every deploy. - 240+ scheduled automations running 24/7 on my own machine: scrapers, bots, reporting and monitoring, each one re-checked on a schedule so a silent failure gets caught. - Claude Code is my daily engineering partner, so I write and test in Node.js fast and keep the code readable for whoever maintains it next. Before the engineering I spent 10 years in growth marketing, including managing the @Dunk Instagram (2.7M followers) at Dunk Media. That is why I ask what an automation is worth to you before I write a line: which hours it saves, which leads it stops losing, which report you stop building by hand. Good fits: lead capture and follow-up, inbox or ticket triage with an LLM, scraping and enrichment into a sheet or CRM, Telegram and Discord bots, connecting the APIs and tools you already use, and fixing a workflow that keeps breaking. The easiest way to start is a small paid first task. Send me the one manual process that eats the most of your week, and I will scope a fixed-price first build so you can judge the work before committing to more.