Outreach that runs itself. Sends only what you approve.
mapleroot is a self-hostable AI operator that finds leads, drafts outreach, and watches your inbox while you build — in plain English, without ever sending a word you didn’t approve.
Self-hostable · bring your own keys · nothing sends until you approve
Example workspaces — illustrative
- Fernwick
- Ostrove Labs
- Quailbridge
- Tidemill
- Lanternworks
500+
apps via Stigmerge
24/7
inbox autonomy
0
unapproved sends
100%
actions audited
capabilities
Everything an operator does.
Not a chatbot with plugins — one agent with real tools, a memory, and a gate on everything outbound.
Lead sourcing on tap
Describe your ICP in plain English. Apify-powered search with rich filters lands deduped leads in your pipeline and your Google Sheet.
Approval-gated outreach
Every email and message is a draft until you say go. Approve, edit, or reject from chat, the approvals page, or Telegram.
Cron in plain English
“Every weekday at 9, find 20 leads and draft intros.” Schedules become morning briefings in chat and Telegram.
Night autonomy, grounded
It watches your inbox overnight and auto-replies only from your knowledge base — sources cited. Everything else escalates to you.
Guardrails in code
Do-not-contact lists, reply caps, and quiet hours are enforced before the model runs — not suggested to it.
500+ apps, one operator
Gmail, Sheets, Slack, and phone calls — connected through Stigmerge and ElevenLabs, with two-way Telegram control.
how it works
Three moves. Then it runs.
Setup is a conversation, not a configuration. Everything after step three happens on your schedule.
- 01
Connect your stack
Link Gmail, Telegram, and Sheets through Stigmerge. Drop your docs into the knowledge base.
- 02
Say what you want
Your ICP, tone, and cadence — in plain English. Schedules and watch rules work the same way.
- 03
Approve. It operates.
Review drafts from chat or your phone. Approve, edit, or reject — it learns your voice from every edit.
see it run
A morning run, start to sent.
One instruction on Monday becomes a briefing every weekday — drafts staged, approval waiting on your phone.
Example conversation: the user schedules a weekday morning job. The operator sources twenty leads, skips three already in the pipeline, stages seventeen drafts through Stigmerge, syncs the sheet, and asks for approval before anything sends.
use cases
For the person who is also the sales team.
Small B2B teams with no SDR, no RevOps, and no appetite for spam going out under their name.
You are the sales team — in the gaps between shipping.
- A pipeline that fills itself before you open the laptop
- Drafts in your voice, approved from your phone in Telegram
- Domain reputation protected by reply caps and quiet hours
wall of love
What operators say.
Illustrative quotes — swap in real customer words before launch.
“I approve outreach from my phone over coffee. The pipeline was full before I opened my laptop.”
“The approval gate is the whole product for me. It drafts all night; nothing leaves without my thumb.”
“We cancelled three subscriptions. The audit trail is what I show clients at the end of the month.”
“Night autonomy answers the routine stuff from our docs — with citations. Mornings start calmer.”
questions
The ones worth asking.
Model, data, control — the answers are in the code, not the marketing.
Claude Opus 4.8 is the main agent; Haiku 4.5 handles bulk mechanical work. You bring your own Anthropic key, so you control the spend.
Put an operator on it.
Self-host in minutes. Bring your keys. Approve every send.
Get started freenothing sends until you approve