An operator you own, not a chat that forgets.
What you get, what happens when you ask for work, where your data lives — and the answers a careful buyer asks for before ordering.
I started this because I could not hire. Every idea needed an engineer, a researcher, someone to run the ads, a designer, a writer and an assistant, and each was a salary I could not justify yet. What I could afford was a chat window that answered well and forgot by lunch. Developers had already got something better: agents that ship their work. Everyone else got a demo.
So I built the operator I needed and ran my own company on it. Between 29 August and 23 September 2026 it merged 1,212 pull requests into its own repository, 900 of them opened by its coding workers, with one revert; it built the ad campaign, rendered the creatives and drafted the pitch. That is the whole thesis in one receipt: work is a job that gets finished, checked, remembered and done better next time.
Two decisions follow. Ownership: the model you rent by the token, but the operator that knows your business, holds your accounts and keeps your memory is yours — your key, a box on your shelf or an account you control, memory in plain files you can copy out. And the gate: an operator that acts inside the walls is useful; one that sends, pays, posts, merges or calls on its own is a liability with a good excuse. Everything that leaves you lands as one card first.
What Figaro does, seat by seat
Operations and inbox
Gmail triaged, replies drafted in your voice and sent on approval; client follow-ups tracked; confirmations and RSVPs handled; the calendar defended; reminders and a to-do list by text; a morning brief and an evening note; meeting notes from Google Meet; documents reviewed; Google Docs and Sheets read and written.
Phone and voice
Calls in your own cloned voice — booking, chasing, confirming. A reception line that answers, qualifies and books when you can't. Call Figaro from the road, hear today's blockers, dictate decisions.
Researcher
Overnight market, competitor and customer briefs with sources; deep research fan-out; trend and academic research; pricing benchmarks; a product canvas; a fact base that keeps every number with its source.
Engineer
A feature or bug described in a text becomes a tested pull request across your repositories; deploys; fixes production at night and asks before merging; builds and deploys landing pages; sets up Supabase, Stripe, domains and email for a new product. Four workers in parallel.
Growth and ads
Meta campaigns built from a brief — audiences resolved, creatives attached, created paused for your approval; insights read back, losers paused; landing variants deployed; a growth experiment run end to end.
Designer and media
On-brand images for every format, logos, decks, product renders, 3D models for a print shop, talking-head reels and video clips from a script — one consistent brand across all of it.
Writer and social
Posts, threads, captions and articles in your voice; your accounts run on approval — X, LinkedIn, Instagram, Threads, Facebook Pages, your Telegram channel; a pitch deck, an ebook, a weekly newsletter.
Sales and outreach
A CRM kept for you; prospects sourced and enriched; your network warmed; events found; the first line written for each person, sent on approval, replies watched, meetings booked, a brief before every call.
Operations
A registry of your projects and tasks Figaro executes against; a receipt for every job; weekly digest and daily journal; services, uptime and errors monitored and repaired; usage and cost per job; multi-agent teams in a Telegram group.
What happens when you ask for something
- 01
You write in the chat
“Move Thursday's call to Friday and tell them why.” “What do competitors charge for X?” “Remind me at 8 to send the invoice.” Telegram today; nothing to install on your phone.
- 02
Figaro decides who does it
A fixed part of the job runs without a model at all — reminders, the to-do list and scheduled briefs run on the box's own clock. The rest goes to the seat that owns it, with only the context that seat needs.
- 03
The seat does the work in its own lane
Research reads and cites. The writer drafts in your voice. The engineer opens a pull request against your repository and runs its tests. Each lane leaves a receipt: what was read, what was produced, what it cost.
- 04
Anything outbound waits for you
A message to a person, a payment, a post, a merge, a call: one card in the chat. Tap to approve, or don't. What you approved is on the record and can be undone.
- 05
Figaro learns from the result
Outcomes and corrections feed memory, so the second time is cheaper than the first and the tenth is routine.
Where your data lives
Box (Figaro Home): your chat history, files, memory, connector tokens and onboarding secrets are on the box. Our provisioning vault purges what you typed into the wizard the moment the box reports its first accepted receipt.
Model inference: every model call goes to Anthropic under your own API key and Anthropic's API terms — your contract with them, metered to you, never routed through a shared account.
Our conductor: a small hosted service that holds your box's entitlement, bound to its hardware, serves signed policy and playbooks, and can revoke a stolen or copied image. It does not receive your chats.
How it differs
OpenClaw is the engine inside Figaro, and we say so. Coding agents are one of Figaro's seats, not the product.
| Figaro | OpenClaw alone | Codex / Claude Code | |
|---|---|---|---|
| What it is | An operator you own: operations, engineering, research, ads, design, and writing in one system, in your chat and personal cabinet. Built for business owners and high-performing individuals. | The open-source agent runtime inside Figaro. An engine you configure, host, secure and maintain yourself. | Developer tools driven from a terminal to produce code. |
| Who runs it | Set up on a call, updated by signed releases, supported for a year with the box. | You: installation, hardening, connectors, updates, incidents. | A developer, per session. |
| Memory and receipts | Operational memory of your business, consolidated nightly; a receipt for every job; approval gate on every outbound action. | File memory is configurable; the operating method is yours to design. | Session context; no operating memory of your business. |
| Ownership | Your API key, your box or your account, plain exportable files, cancel anytime. | Fully yours, including every hour of upkeep. | A seat in the vendor's product. |
For the careful buyer
Data, security, cost. Straight answers.