Web apps, AI workflows, and the integrations between them. Built one project at a time, by one specialist, for small teams that need software they can rely on.
Generic automations are everywhere. What you need is a hyper-personalized workflow built around your daily friction, not another template that almost fits.
Still doing these manually?
I map the tools you already use, then build one workflow that handles it, with alerts when something breaks.
Running a store but still doing this manually?
I connect your shop, inbox, and spreadsheets into one reliable flow, so ops run while you focus on growth.
Next.js apps, dashboards, admin panels, marketing sites with a real backend. The kind your team uses every day, not the kind that looks good in a screenshot.
Agents that read documents, draft replies, summarise meetings, or triage tickets. Built with an evaluation set, validation, and a human-review fallback so 'mostly works' never reaches your customers.
Not another Zapier template. Workflows built around how you actually work. Make.com, n8n, and custom backend glue when no-code hits its limit.
Most of my work is building AI agents, model demos, and API integrations — then wiring them into Python and Node services, databases, and production workflows. Front-end is part of the delivery when a product needs a UI; the depth is in AI engineering and backend.
Every skill below is part of my active stack.Core= strongest professional focus.
Agents, demos, model tooling, and integrations that survive real data — with prompts, validation, and fallbacks baked in.
Services, webhooks, and REST layers that agents and apps depend on.
You tell me what your team is trying to do and where the friction is. I ask questions to understand the work. Plain English, no pitch.
I send back a written plan: what gets built, what's deliberately out of scope, the price, and a timeline scoped to your actual project. If it doesn't fit, we stop here. No obligation.
I build the work in vertical slices and share progress at regular check-ins. You can change direction at any point without it costing more.
You get the runbook, a recorded walkthrough, and a follow-up period for free bug fixes after launch. After that, you can run it yourself or send the occasional task.
You reach me directly. I do the work. I do the hand-over. No PMs, no junior devs, no game of telephone between you and the person actually building it.
I build things that ship. If something is risky or unlikely to work on your data, you'll hear about it before you've paid for the full build, not after.
Every AI workflow I build comes with an evaluation set and a fallback path. If accuracy isn't good enough on your real data, you'll know before launch.
Every project ends with a runbook plain enough that a non-developer can change a webhook URL, swap an API key, or read the logs when something looks off.
I'm a software developer, which means I argue with machines that are always right until 4:47 p.m. on a Friday. I joined for meetup pizza, unlimited tabs, and saying "it works on my machine" while production quietly panics. I debug with a rubber duck, deploy with courage, and estimate tasks as guess times pi times guilt. Computer science has two hard problems: cache invalidation, naming things, and off-by-one errors. Three items. Accurate. I write undocumented features until QA disagrees in writing. Technical debt is a gym membership I narrate well and visit rarely. Hire me before I refactor this into three services and a webinar.
Experience, approach, and where I come from.
Describe your friction: scattered apps, store ops, inbox chaos, whatever eats your time. I'll reply with whether it's worth automating and what a personalized workflow would look like. No commitment, no pitch.