I turn "someone should build this" into a working AI agent by next week.
I got into AI agents the practical way not chasing hype, but because I kept running into the same problem: teams had tons of repetitive, multi-step work that no chatbot could actually finish for them. It could summarize, suggest, and explain but someone still had to do the actual task. That gap is what I build for.
I'm a software developer with around 10 years of experience, and over the last 5 years I've focused specifically on agentic AI systems that don't just respond, but plan, use tools, call APIs, and carry a task through to done. I've built agents that handle customer support tickets end-to-end / pull and reconcile data across systems / automate research and reporting swap in your real projects, and I care a lot about the difference between a flashy demo and something that survives real usage: error handling, logging, fallback behavior, and clear documentation so a client isn't dependent on me forever.
Before AI-specific work, I spent time in full-stack development which is honestly why my agents tend to be more "production system" than "cool prototype" I think about scale and failure cases from day one, not as an afterthought.
Outside of client work, I'm usually experimenting with new agent frameworks. I like this field because it moves fast enough that there's always something worth rebuilding better.
What you can expect from me: clear scoping before I write a line of code, honest timelines (I'd rather under-promise), and a system you actually understand when I hand it off not a black box.
Work Terms
Hours: I'm generally available Mon–Fri, 6:30pm–12am SGT during week days and 8:30 am - 7pm during weekends, with reasonable flexibility for urgent fixes or calls across time zones. I'll always confirm expected response times before we start.
Communication: I prefer keeping everything in writing on the platform (for a clean paper trail) quick questions get same-day replies, and I'll flag proactively if something's blocking progress rather than going quiet. Video calls are welcome for kickoff and scoping; day-to-day updates work well async.
Payment: For fixed-price projects, I typically work in milestones a deposit to start, remainder on delivery (for longer projects, split into 2–3 milestones tied to concrete deliverables). For hourly work, I bill through the platform's time tracker so everything's transparent on both sides.
Scope & revisions: I scope clearly upfront so there are no surprises. Reasonable revisions within the agreed scope are included; anything beyond that we'll just discuss as a small add-on rather than me quietly eating the cost or you getting a surprise bill.