Let's talk

Six ways: freelance for a scoped build at a fixed price, contract for ongoing engineering capacity across three to six months with milestone billing, full-time for systems roles, remote as the default, plus speaking and mentoring. If a project does not fit any of them, I say so early instead of forcing it into one.

Full-stack web and product development, system integration between tools that refuse to talk to each other, IoT and hardware builds on ESP32 and MQTT, automation workflows in n8n and Python, and AI integration with retrieval that cites your own data. If something sits outside that, you hear it before any money moves.

Yes. Scope, price, and timeline are written down before anything gets built, and the price is fixed against that scope. Revisions inside the agreed scope are already part of it rather than a change request. Anything genuinely new gets quoted honestly instead of absorbed quietly.

Work lands milestone by milestone, and every milestone is something you can actually run on your own data, not a screenshot. You get a demo, a changelog, and a list of what is still open, whether or not you ask for it.

Source, deploy setup, documentation, and a short support window. It is deployed and handed over so your team can run it without me: no lock-in and no undocumented magic.

Depok, Indonesia, working in GMT+7 and comfortable across Jakarta and Jabodetabek in person. Remote is the default and async is fine: written handoffs mean overlapping office hours are not a requirement.

Usually within a day. Write in English or Bahasa Indonesia, whichever is more natural for you, and I reply in the same language.

Send a message for an intro, a short question, or when you are not sure yet. Book a call when the topic needs back-and-forth, planning, or live context. Either way the first step is the same: what breaks, what is slow, what keeps landing back on your desk.