About

I am Ricardo Gomez. I build automation systems for small businesses from Melbourne, and I work with clients wherever they are.

Most of what I know came from running automation against my own businesses before selling it to anyone else. Publishing pipelines that write and post without a person, content queues that refill themselves, mailing that reaches an entire list rather than the first fifth of it, and reporting that arrives before anyone asks. All of it in production, all of it having broken at least once in a way that taught me something worth charging for.

Alongside that I have written a lot of automation inside a working business, in Python and Visual Basic, aimed at the unglamorous end: reconciliation, reporting, and the manual copying between systems that nobody owns and everybody does.

Why the supervisor exists

In one day I traced four separate outages across systems I had built. Three of them had exited successfully. The scripts ran, returned zero, and did nothing. Nothing in the logs said otherwise, and nothing would have said otherwise for months.

That is the failure mode nobody sells against, because it is invisible in a demo. It is the reason every system I build now ships with something watching it, and the reason supervision is a line on the pricing page rather than a thing I quietly hope you never need.

How I work

Fixed prices, quoted before the work starts. Built on your accounts so you can walk away with everything. A two week supervised run against real work before anything is called finished. And a straight answer when a thing is not worth automating, which happens more often than you would expect from someone selling automation.