You L.

10 years in software engineering. Anthropic Claude Certified Architect - Foundations (CCA-F). I build the systems service businesses run on. And I build them so one failed step doesn't stop the rest. Recent work: ✅ Launched a self-serve booking website. Customers book, invite others and verify their ID on their own. ✅ Took payments live on QuickBooks, by card or wire. Every flow signed off. ✅ Pulled a scattered approval process into one set of rules, in one place. ✅ Built a voice agent that runs the intake call. It never guesses a field. Usually I get the call when a business has grown faster than its tools. Requests come in by phone, text and web form, and they land in different places. The approval rules live in automations that don't agree. Someone matches payments to the books by hand. And when something breaks, a customer finds out before the team does. What I build: 🗓️ BOOKINGS CUSTOMERS RUN THEMSELVES ▪ Group bookings, invites, text code sign-in, ID check, extra services ▪ React, Cloudflare, Airtable, Stripe Identity 💳 PAYMENTS THAT MATCH THE BOOKS ▪ Card or wire, card fees, refunds and voids, branded PDF invoices ▪ QuickBooks Online, QuickBooks Payments 📞 CALLS AND TEXTS IN ONE PLACE ▪ Voice intake, one thread per customer, automatic follow-up ▪ Retell, ElevenLabs, JustCall, Airtable ✋ A PERSON APPROVES THE MONEY ▪ Review screens that put the caller's own words next to every value ▪ Nothing gets invoiced until someone signs off 🛡️ BUILT TO KEEP RUNNING ▪ One alert path, a morning summary, a fallback when the AI fails ▪ A record of every AI decision, links locked until a one-time code 🤖 AI AGENTS (CLAUDE CERTIFIED) ▪ Lead and intake agents, knowledge agents with a source on every answer ▪ Claude API, MCP, Python, n8n, Make, Qdrant I start with the data, not the screens. Before I write any code, you get a data model and a build order in blocks you can start or stop. That's where most rework comes from, so I settle it first. Then I write the failure paths before the happy path. And wherever money moves, a person signs off. Not everything needs AI I'll tell you which steps should just stay plain rules. And if a tool won't hold up with real data, I'll say so before you pay for it. After launch I stick around for fixes and the next phase. When something ships, you get a short Loom. Every week, a recap. And every build comes with documentation and a walkthrough video. Send me the process you want automated. I'll tell you what I'd build first and where it'll probably break. That part's free. You Li