One person can't triage inbox, track finances, monitor SEO, prep meetings, and chase follow-ups daily. I needed a team — without hiring one — that operates without me watching.
Architecture
Entry
Telegram botone tap
Orchestrator
Chief-of-Stafforchestrator / router
Specialists
Inbox
Daily Brief
FinanceStripe
SEOAhrefs
CRM
Calendar
Content
Weekly Review
Safety / control
QA / Self-Healingmonitors + re-triggers
Data layer
Notionshared data layer
Tools
Cloud routinesthe clock
MCP toolsGmail · Cal · Stripe · Ahrefs · Canva
A Telegram bot is the single entry point. It routes to a Chief-of-Staff orchestrator, which delegates to eight specialist agents — Inbox, Daily Brief, Finance/Stripe, SEO/Ahrefs, CRM, Calendar, Content, and Weekly Review. A QA / self-healing agent monitors every run, re-triggers failures, and only alerts me when it can't fix itself. Notion is the shared data layer all agents read and write; scheduled cloud routines act as the clock; and MCP tools — Gmail, Calendar, Stripe, Ahrefs, Canva, Zapier — are the hands that reach external systems.
Key decisions
01
Notion as the single source of truth
Every agent reads and writes one substrate, so state is shared and I get an audit trail of everything the workforce did.
02
A chief-of-staff router
One entry point instead of many bots. Agents compose into multi-step workflows behind a single conversational surface.
03
Conservative by default
Agents draft and label, never send or delete. Trust is earned before autonomy is widened — the safe default is reversible.
04
A QA agent that treats agents as flaky services
It detects missing or errored outputs, re-triggers the run, and escalates to me only when it genuinely can't self-heal.