About Automaty

I build operating systems
for businesses that grew
faster than their structure.

The through-line

Always the same pattern.
The shortcut inside the system.

01 · Growing up online

Modifying what was already built

Deep in forums figuring out how to modify what others had built. I wasn't learning to code from scratch — I was learning to read a system and find its shortcut.

02 · Heavy operations

The same instinct in a mine

Blasting supervisor on site. When the manual reports became the bottleneck, I automated them. The instinct was the same — only now applied to a real production process.

03 · Technical training

No break, just continuity

Python course by IBM. AI program with Ed Donner underway. It wasn't reinventing myself — it was putting a formal name to what I'd been doing for years.

04 · Automaty

The synthesis

Looking at a business as a system with bugs and finding where to intervene. The same thing from the forums, the same thing from the mine, now applied to service businesses.

The same instinct, at different scales.

The click

Why Automaty exists.

I watched someone close to me work too hard, knowing that with a system she'd work less. Tasks that repeated every month. Information that lived only in her head. The feeling that the business depended on her always being available. That's not a system — that's her working twice as hard.

Automaty is also the life I want. Geographic independence, my own project, something I love doing. I sell what I practice — if I don't build the system for myself, I have no right to sell it.

How I work

Two things that aren't negotiable.

01 · Cross-trained lens

I see the business as a program with bugs.

I come from heavy operations and from reading systems. That's different from the traditional process consultant, who sees people and rituals. I see inputs, outputs and where information gets lost.

That view changes the diagnosis. What looked like a team problem is almost always a structure problem.

02 · Async as a signature

I work from where you aren't.

Today I write from Australia. Later, other time zones. That forces everything to be documented and nothing to depend on "being online" to respond.

I end up delivering what I practice — a system that works in your absence, because I'm not physically present either.

First proof

The pilot that
validated the method.

CYS Soluciones Tributarias — a Chilean accounting firm. V1 delivered in April 2026: a diagnosis of the operating system, a new document structure and the first processes formalized.

Since June, a symbolic retainer runs to accompany a full cycle and validate the methodology with real data, not assumptions.

No commercial clients yet. The first real paying client is next.

Let's start by seeing where you stand.