Stop introducing yourself to your own assistant.

Every session, you explain yourself again. What the business does, who the client is, how you like things written, what you decided last week. The assistant is capable — and it meets you as a stranger every single time. This turns it into one that remembers, that you can reach from your phone, and that works while you sleep.

The install is a conversation

You hand it the folder and say one sentence. It asks nine questions — all with defaults you can accept by pressing enter — and configures everything from your answers.

$ claude

> Read INSTALL.md and set this up for me.

  Reading INSTALL.md… done.
  Following install/INTERVIEW.md — nine questions.

  1 / 9   What do you want to call me?
  ❯ Atlas

  2 / 9   Your name, and what should I call you?
  ❯ Marie Dupont — Marie is fine

  3 / 9   In a sentence or two: what do you do?
  ❯ I run a two-person design studio. Proposals,
    invoicing, and chasing the follow-ups I forget.

  4 / 9   Language and register?
  ❯ English, direct

  …

  9 / 9   Anything I must never do without asking?
  ❯ Never email a client without my go-ahead

  ─────────────────────────────────────────────
  Applying.

  ✓ workspace          ~/Documents/Atlas
  ✓ working contract   CLAUDE.md
  ✓ memory             index seeded
  ✓ phone bridge       running (survives reboot)
  ✓ voice notes        large-v3-turbo, local
  ✓ morning brief      weekdays 07:00
  ✓ continuity kit     built · nightly 21:20

  Sending a test message to your phone…
  ✓ Delivered.

  Atlas is running. Talk to me here, or from Telegram.

What changes, day to day

The voice notes are the part people keep

You are walking, driving, between two things. You hold the button and talk. Thirty seconds later the work is done on your machine and the answer is on your phone.

Transcription runs entirely on your machine — no audio is uploaded anywhere. And it is tuned for how voice notes are really recorded: outdoors, one-handed, with traffic. The audio is cleaned before transcription, the language is pinned rather than guessed, and your own names and jargon are fed in as hints. That last part is what stops it turning a client’s name into nonsense.

What it costs

The install largely runs itself — that is not what the session is for. Three decisions determine whether this becomes part of your day or another thing you configured once and stopped opening: what it should remember and what is noise, what it must never do without asking, and which recurring task is worth automating before the others. That hour is the product.

Built around your work instead

It ships opinionated, because a default has to choose something. When your work does not fit those defaults, it gets built around your work — quoted per project after a scoping call.

• Your tools — CRM, accounting, calendar, project tracker, internal APIs, your databases
• Your workflows — your real process, your approval gates, your formats and vocabulary
• Your trade — a memory structure and prompts shaped for what you actually do, not generic business assistance
• Your team — multiple users, shared memory, role separation
• Other channels — WhatsApp, Slack, SMS or email, alongside Telegram or instead of it

Honest limits

• You need your own Claude Code subscription. This configures it; it does not replace it.
• One person, one bot. Two people means two installs, or a custom build.
• The Mac has to be awake for scheduled work. A laptop is not a server — fine for a morning brief, wrong for anything critical.
• Telegram sees your messages. The voice transcription is local; the messages themselves are not. If that matters for your work, say so and we will use a different channel.
• macOS today. Everything works on Linux except the scheduled agents, which need systemd timers instead.

Common questions