Work

Systems that are already running.

We don’t show mockups. We show what was broken, what we built and what changed after. Every case says plainly whether it was a client, a pilot or one of our own — because blurring that is the easiest way to look bigger than you are.

01 — The case the method came from
Pilot Delivered · Apr 2026

Accounting practice
in Chile

An accounting practice with around fifteen active clients, run by the owner and one assistant. Good tools, loyal clients, and absolutely no capacity left.

Before
Not one written process — the owner confirmed it outright. What actually ran the business was a spreadsheet only she knew how to use. One whole process was broken: access to the proper tool had been lost, so each case got handled by editing an old document.
The system problem
It wasn’t a software gap: three accounting programs were running fine. It was that no part of the system existed outside one person’s head. No naming convention, duplicate files, and no way to tell which one was current. If she stopped for two weeks, the technical work stopped with her.
What we built
We mapped the whole business: the three real operating cycles, the calendar of hard deadlines, who does what, and what breaks first as it grows. On that map we built a new document structure, wrote up the critical cycles as procedures, and stood up a single source of truth to replace the spreadsheet, with the old history carried across.
What changed
The system stopped living in one head and got written down. The assistant now has a written procedure to consult instead of having to ask. The practice is now in a state where someone new could join without being talked through everything from scratch.
Evidence and scope A full operational diagnosis, a document structure and four written procedures, delivered April 2026. We then stayed through a complete operating cycle to test it against real data.

We publish this case without naming the firm: we don’t have written permission to name them, and we’re not assuming it. For the same reason there are no screenshots — the system holds their clients’ information.
DiagnosisDocumentationSource of truthProcesses
02 — Custom booking system
Client Live

Perrito Zen
Grooming & SPA

perritozen.cl

A dog grooming business in Chile. Guillermo does the grooming, and while he’s grooming he can’t answer the phone.

Before
Every booking came in by message and got written down by hand, one at a time. The owner was the diary — juggling times from memory with a dog on the table.
The system problem
What was missing wasn’t a booking app. It was that availability, payment and the consent form needed to be one defined process instead of three loose conversations.
What we built
The whole booking flow: the client sees real availability, picks a day and time, pays the deposit online and signs the consent form, with nobody stepping in. Each booking syncs both ways with the business calendar and emails the owner and the client.
What changed
There is now an online booking, payment and confirmation flow that did not exist before: a client can complete it without speaking to anyone. We have not measured how many bookings arrive that way, or how much time it gave the owner back — when we do, we will say so.
Evidence The system is live and anyone can check it: go to perritozen.cl and walk the booking flow through to the payment step.
BookingsOnline paymentsAutomationWeb
03 — Operating platform
Our own product Live

Automaty OS

os.automaty.io

Our own product. We built it because the same gap turned up in every business we organised.

Before
Once a business was documented, the information was still scattered: a spreadsheet here, a calendar there, the history in the owner’s head. The order existed on paper with nowhere to live.
The system problem
Documenting a process isn’t enough if there’s nowhere for it to actually run. What was missing was the operating layer between the document and the working day.
What we built
A platform where each business gets its own space and sees its real operation — clients, orders, records, history — in one place, in real time. It installs like an app on a phone.
What changed
There is a place where one business’s operation can be seen whole instead of scattered. Mostly it’s our own proof: if we don’t build the system for ourselves, we’ve no business selling it.
Evidence and scope The platform is live and currently has one business with real data inside it. Access is private per business, so the public URL only shows the sign-in screen — their data isn’t ours to put on display.
PlatformMulti-businessOperations panelApp
04 — Brand + operational diagnosis
Client Antofagasta, Chile

Hielos Maass

A family ice business in northern Chile. Good product, repeat customers, and an owner who is the entire business.

Before
Orders arrived by message and on scraps of paper. No customer list, no order tracking, no view of stock. All the commercial knowledge lived in the owner’s memory.
The system problem
It looked like a communication problem — “we need to tidy up the messages” — but it wasn’t. There was no system for the messages to be the front end of: nothing to tidy, because nothing was recorded.
What we built
A full brand identity and commercial system, so it stopped reading as improvised to customers who buy on trust. Alongside that we ran the operational diagnosis: real volume, production capacity, the order cycle, and where information falls through.
What changed
The brand now holds up the commercial promise, and for the first time there’s a written map of how the business runs — the mandatory starting point before building any tool.
Evidence and scope Brand and commercial system delivered. The operating system is diagnosed and designed, not built: the next step is the customer record. We say it that way because the order matters — you don’t automate what isn’t organised yet.
IdentityCommercial systemOperational diagnosis
Straight with you

Automaty is a young company. These are the real systems we’ve built — not one of them is a mockup — and each is labelled for what it actually is: client, pilot or one of our own.

We have also built brand and site work for the founder’s own projects. We don’t list them as cases, because they aren’t clients — and mixing them in would be the easiest way to look bigger than we are.

Let’s start by seeing where you stand.