Auttendo

An AI crew for a company. One agent per project, and a personal one for everyone.

Role
Product design and engineering
With
Tim, at Dazzled
When
May to November 2026

Auttendo started with a simple idea. A business owner sends a WhatsApp message like “add our summer hours to the contact page”, and it gets done. Agents made the change in a real codebase and reported back in plain language.

We kept pulling on that thread. If an agent can look after a bakery’s website, it can also watch prices, write the ads and keep an eye on the shop’s orders. By September the product had become a workspace. Every cluster of work in a company gets a Project, every Project gets exactly one agent, and every person gets a personal one. Mine was called Pietje.

Auttendo is about to change completely. Before it does, this is how it looked on 6 November 2026, captured from our own workspace.

Auttendo home: a greeting, then seven agent characters in a row with a speech bubble above one of them, and a box to ask Pietje anything
Home /vespucci

The crew

Home shows the crew. Each agent is a small character in its Project’s colour, and the bubble above it says what it worked on last. Lennie runs Monitoring and posts a price update every day.

A conversation with Pietje: a list of past chats on the left and a request to turn a block of website-editing rules into a reusable skill
Conversation with Pietje /vespucci/personal

Talking is the interface

Everything starts in a conversation. You ask in plain words, the agent does the work, and each step shows up in the thread. Here I asked Pietje to turn a set of website-editing rules into a skill that every Project could reuse.

The Inbox with one conversation open, in which the shop’s agent removes an automation and confirms it is gone
Inbox /vespucci/inbox

The Inbox

When an agent needs a person, its conversation lands in the Inbox. This one is the agent for a WooCommerce shop, removing the new-order notification it had been asked to stop.

The Library: recent skills and documents as cards, then a list of databases, apps and documents with the Project each belongs to
Library /vespucci/library

Everything it makes

Whatever the agents make ends up in the Library: documents, databases, small apps and skills. The price monitoring dashboard in this list is an app built inside the Monitoring Project.

Integrations: a search across 3,238 apps and a grid of tools such as Context7, Medusa, Notion, Slack, Gmail and Google Calendar
Integrations /vespucci/integrations

Connected to the tools you already use

Agents worked in the apps a company already had. Gmail, Google Sheets, Slack, Notion, Medusa and WooCommerce were a click away, out of more than 3,000 apps, and any MCP server could be added on top.

Around the edges

Routines ran on a schedule. Pietje wrote me a morning brief every day at 07:30. Each agent also had a voice, its own settings and a private library.

  • Pietje’s routines: a five-minute reminder and a morning brief every day at 07:30
    Routines /personal/routines
  • Pietje’s private library with a morning briefs database and a planning document
    Personal library /personal/library
  • Settings for Pietje: name, voice, which credits it uses and the floating character
    Agent settings /personal/settings

The build

Built with Tim out of Dazzled, our product studio. The last version was a full rebuild: 556 commits between 7 September and 26 October 2026, for the web and a Mac app.

I’m proud of what we shipped. This page is here so I remember what it looked like.

© 2026 Chris Jayden Crafted with Svelte