Yusta HQinternal systemBuenos Aires

17agents, eleven of them on a fixed schedule, plus a watchdog over the client apps

The system I run my own company with.

How it was before

Yusta Labs is just me. Writing code is half the work; the other half is finding businesses, writing to them and checking that no client app is down. It started as a marketing agency: I wanted agents that understood my taste and made the content for the company Instagram, the part I am worst at. Others brought me business owners with their email and phone, every day.

With one pair of hands, whatever is not scheduled does not happen. The code held up; the follow-up kept slipping.

What I built

HQ runs on my work machine: seventeen agents built on Anthropic and Gemini models. Eleven run at fixed times through Windows Task Scheduler, and a watchdog checks the client apps in production several times a day while the machine is on. It decides on its own what content to make, from what I post and what I skip. Sales emails go out within limits; posts and WhatsApp messages wait in one tray for my approval. It has produced 642 pieces for the company Instagram in 62 days. By my own count, doing that by hand would take a full working day. No client has signed through it yet, and this case is about how it is built.

Node 24, standard library only, zero npm dependencies · JSON, JSONL and Markdown instead of a database · Anthropic and Gemini APIs · 2,086 automated tests

The interface is in Spanish today. Which language it ships in is set per build.

The tray after the company’s morning: six items in three piles. Nothing has gone out yet.
The tray after the company’s morning: six items in three piles. Nothing has gone out yet.

The decisions, and why

  1. Each shift runs at a fixed time.

    A loop that runs every so often cannot be audited: when nothing shows up, you cannot tell whether there was no work or it never ran.

  2. WhatsApp never sends on its own. Email does, within limits.

    I sent too many messages in one day, WhatsApp read it as spam and suspended me for twenty-four hours. That is where the cap of forty a day came from, and every other cap behind it. Email goes out between 9:30 and 6, with a cap per batch and a cap per day.

  3. The screenshots on this page do not come from the HQ I use.

    The real tray lists names and phone numbers of businesses that never asked to be on a website. HQ has a showcase mode: the same system reading sample records written by hand, with everything but reading blocked.

One of those messages, open: the business, the hook an agent found, who reviewed it, and two buttons.
One of those messages, open: the business, the hook an agent found, who reviewed it, and two buttons.

Before and after

BeforeAfter
Whatever I rememberedEleven shifts at fixed times
Checking the apps when I rememberedA watchdog round several times a day
Send first, look laterLimits on email, my approval for the rest
Conversations lost in the inboxEach business with its next step
The Office: seventeen desks and the time each agent last ran.
The Office: seventeen desks and the time each agent last ran.

No client quote here: the client is me.

The Studio archive: three days of content for the company Instagram, each piece with its score. These pieces are real.
The Studio archive: three days of content for the company Instagram, each piece with its score. These pieces are real.

The system, running

No sound, with subtitles and made-up data.

The reels the Video agent makes

The Video agent turns an archive carousel into a reel from code. I cut the slides with the old prices. It is in Spanish.
Why a business doesn’t show up on Google.
What a well-built website includes.

Email me about a system like this, or about a role

I quote a custom system within 24 hours. If you are hiring, my resume is one page.

WhatsApp: +54 9 11 2469-3394

Next case: SLE MensajeríaBack to all five