What I get hired for

Automation That Runs Itself

Your repetitive work happens on schedule, and you can see which step failed.

Proof
3 pieces of work
Tools
n8n, Klaviyo, Playwright
Availability
Remote · UTC+7
Reply
Within a day
01Proof

Where this has already shipped.

02Brief

Build your brief.

Tick the parts that sound like your project. They collect in a bar at the bottom of the page, and one button turns them into an email to me. Nothing is sent until you press it.

  • A scheduled pipeline

    Sources in, the work in the middle, results published out the other end, self-hosted and unattended.

  • See which step failed

    Runs you can inspect step by step, so a failure shows up as a failure and not as a missing result.

  • Transactional email flows

    Default store emails replaced by Klaviyo flows mapped to real order and customer data.

  • Long jobs handed off cleanly

    Async render jobs waited on, the finished result passed to the next step, and every stage logged back to a database.

  • Repetitive browser work

    Steps that live in a web interface, driven by Playwright and scheduled with launchd.

  • A cost check before a big run

    Paid model calls measured on a small sample so the invoice is not the first time you learn the number.

03Field notes

What I already knew about your domain.

The traps specific to this kind of product, each one from work that shipped rather than from a reading list.

04Start

Think this is your problem?

Tell me what is happening in your own words. No brief needed, no spec. I will tell you within a day whether it is mine to solve, and roughly what it takes.

Describe the problemrafiimanggala3@gmail.com · reply within a day