How Aecaro works

They notice before you ask

Every coworker keeps watch over your connected calendar, inbox and records. Through the day the platform keeps a ledger of what was promised, booked and asked, and looks for the shapes that cause trouble: two things booked in the same slot, a reply you owe, a promise coming due with nobody on it, an email that contradicts a booking, something that moved.

When one is worth your attention, the coworker whose job it is prepares the fix as a draft — the email, the new time, the record change — and you get one card: Do it, Not now, or Never this kind. Nothing is sent until you choose, and your choices teach it what's worth raising. A new email or calendar event wakes it within minutes; "Look around now" on the Command Center runs it on demand, and tells you if it couldn't read a source (for example, an app that needs reconnecting).

Standing orders

Each coworker has a standing order: what it keeps an eye on without being asked, and when it stops and asks you. It starts from the coworker's role and connected apps; you can read and edit it on the coworker's Settings tab, next to how many things it has raised and how many you acted on. Problems it notices are routed to the coworker whose order covers them.

Briefs and the findings log

Every job ends with three lines — Found, Changed, Next — and that's what you see in its chat; the full write-up is behind "Read the full write-up". Each brief is added to the coworker's findings log (/team/<coworker>/findings.md), and the next job starts from it: report only what changed, and when nothing did, follow the next open question instead of rewriting last week's answer.

If a job finds that something on file is now wrong, it corrects it — its own facts directly, a shared file through your approval — or you get a card to have it fixed. The log never forgets: older entries shrink to one line and are kept in full in monthly archives beside it. The Command Center's "What changed" shows the team's discoveries from the last two days.

The knowledge base, as files

Knowledge Base → Files is a folder tree your coworkers read, search and write: /company for what everyone shares, /owner for your notes, /team/<coworker> for each coworker's own work. A coworker writes freely in its own folder; anywhere else its change waits for your approval. Every change keeps the version before it — History → "Bring this back" undoes it.

Import a .zip of SOPs, price lists and notes (PDF, Word, Markdown, text, CSV) into any folder; download any folder as a .zip with an index of what's inside. Long files open for coworkers as an outline so they read only the section they need, and a new file that repeats one beside it is merged into that one instead of piling up.

Aeco, your assistant on every page

Aeco comes with every plan and needs no setup — open it from the button at the top of any page. It sees the whole team and everything waiting on you, puts recurring work on anyone's schedule, builds and runs workflows, launches multi-step research, connects apps and hires a new coworker when you need one. It keeps watch over your own calendar and inbox, and takes anything no other coworker owns.

The Command Center

One screen: your team live on one side — each coworker's Now, Found and Next — and on the other, what needs you (questions, problems it noticed with the fix drafted, anyone stuck), what changed, and recent work. Click a coworker to open its chat beside the page.