# Robotomail

Aiolum story: https://aiolum.com/story/robotomail/ · added 2026-11-03 · updated 2026-11-03

**In short.** Robotomail (Email mailboxes for AI agents, by API, MCP or CLI, United Kingdom): US$331 a month MRR, November 2026. Evidence grade A: disclosed by a company or a filing, or verified by a payment processor. Team: 1 named founder; the About page says he builds it. Launched 14 March 2026; still running, revenue flat.

Email mailboxes for AI agents, by API, MCP or CLI · United Kingdom · AI-native · solo founder · still running, revenue flat · group: Tools for using AI models

- Outcome: US$331 a month MRR, November 2026 (evidence grade of the headline number: A; headline in US dollars: 3972)
- Launch: 14 March 2026; months from launch to the outcome: 8
- Team: 1 named founder; the About page says he builds it
- Outside funding: None (About page: no venture funding)
- Main factor: Timing
- Meters, 1 to 4: evidence strength 3, copyable pattern 2, capital needed 1
- Tags: AI-native, Solo founder, Bootstrapped, Running, B2B, Developer tools

Links:

- Visit robotomail.com: https://robotomail.com/
- Verified revenue on TrustMRR: https://trustmrr.com/startup/robotomail

**The product.** A developer or an AI agent creates a real email mailbox with one API call, an MCP tool or a command-line program. The agent sends email from that address, receives each reply as an event in the developer's code (a webhook, a server-sent event stream or polling) and answers in the same thread. The use cases on the site are customer support, follow-up of incoming sales inquiries, scheduling and onboarding help.

**Why it worked.** AI agents that run for hours or days need an address that people can write back to, and a normal personal mailbox needs a browser login and OAuth consent screens that a program cannot click through. Robotomail sells a mailbox that a program can create and read without a person. It started in March 2026 and connects to Claude, Codex, Cursor and other agents through MCP, an API or a command-line program.

Evidence grades: A = disclosed by a public company, a filing or a payment processor, or verified by one; B = two or more independent reports agree, or a journalist confirmed it; C = a founder claim that no one else verified; D = reported, not verified: one founder claim or a third-party estimate with no second source; calc = computed on this page from graded facts.

## Summary

Robotomail gives an AI agent, a program that uses a language model to read, decide and act over several steps, its own email address. One POST request to the REST API (a web interface that takes and returns plain JSON over HTTPS) creates a mailbox. Replies reach the developer's code as webhook events, which are HTTP requests that the service sends to the developer's server when a message arrives. An assistant such as Claude Code can also connect through MCP, the Model Context Protocol, a standard way to give a model tools it can call: read, send and reply.

John Joubert, named as founder on the TrustMRR profile and as builder on the company's About page, started it in March 2026; the profile gives 14 March 2026 as the founding date. The About page says it is bootstrapped, with no venture funding, and the legal pages name the operator as Tiny Bot Labs Limited. On 3 November 2026 the Stripe account, read by TrustMRR, showed US$331 in monthly recurring revenue (MRR, the subscription revenue that repeats each month) from 17 active subscriptions, and US$1,596 in revenue since the first payment in March 2026.

This is a small, early figure, shown here because it is verified by the payment processor. Monthly revenue has stayed between US$241 and US$274 from July to October 2026. The page also shows four failed startups that sold email help or developer communication tools before agents could write their own replies.

## Pricing

Robotomail plans on 3 November 2026, from the company's pricing page and home page (grade C)

| Plan | Per month, billed yearly (US$) | Per month, billed monthly (US$) | Limit |
|---|---|---|---|
| Free | 0 | 0 | 1 mailbox, 10 sends and 10 receives a month, own address only |
| Solo | 5 | 5 | 1 mailbox, 500 sends and 500 receives a month, 50 sends a day, 1 custom domain |
| Starter | 14 | 19 | 10 mailboxes, 15,000 sends a month per mailbox, 500 a day per mailbox, 2,000 inbound a month |
| Growth | about 40 | 79 | 50 mailboxes, 1,000 sends a day per mailbox, 20,000 inbound a month, 5 custom domains |
| Scale | about 100 | 199 | 200 mailboxes, 2,000 sends a day per mailbox, unlimited inbound, dedicated IPs |

Free is 1 mailbox with 10 sends and 10 receives a month, and it exchanges mail only with the account owner's verified address. Solo costs US$60 a year, the same as 12 monthly payments. Starter costs US$168 a year, shown on the home page. For Growth and Scale the page says only that annual billing costs about 50% less than 12 monthly payments; the yearly figures below are calculated from that sentence, not read as prices. Every paid plan has a 30-day money-back guarantee. Growth and Scale have no monthly sending cap but a daily cap per mailbox.

## How much revenue does Robotomail make? The numbers, graded

US$331 in monthly recurring revenue from 17 subscriptions about eight months after launch, read from the founder's Stripe account by TrustMRR

| Fact | Value | Grade | Note | Sources |
|---|---|---|---|---|
| Monthly recurring revenue, 3 November 2026 | US$331 | A | TrustMRR metric snapshot, Stripe connected by API key, revenue last synced 3 November 2026 at 10:01 UTC. The profile gives MRR growth over the last 30 days as +11.4%. | [1] |
| Active subscriptions, 3 November 2026 | 17 | A | TrustMRR metric snapshot from Stripe. | [1] |
| Average MRR per active subscription | about US$19.47 | calc | Calculated: 331 divided by 17 equals 19.47. The profile does not show how the 17 subscriptions split across the US$5, US$19, US$79 and US$199 plans. | [1] |
| Annual run rate | US$3,972 | calc | Calculated: US$331 times 12. | [1] |
| Revenue since the first payment | US$1,596 | A | TrustMRR all-time verified revenue. The monthly rows of the profile add up to the same US$1,596. | [1] |
| Revenue, last 30 days to 3 November 2026 | US$274 | A | TrustMRR gives revenue growth over the last 30 days as +14.1%. | [1] |
| Monthly revenue, March to June 2026 | US$15, US$38, US$357, US$114 | A | TrustMRR monthly revenue timeline. The profile does not explain the high May figure; yearly plans paid in advance would produce such a month, but this is not verified. | [1] |
| Monthly revenue, July to October 2026 | US$269, US$269, US$241, US$274 | A | TrustMRR monthly revenue timeline. Flat within about 15% for four months. | [1] |
| Founding date | 14 March 2026 | C | Founder-entered field on the TrustMRR profile. The first Stripe revenue, US$15, is in March 2026 (grade A). | [1] |
| Founder | John Joubert | C | TrustMRR founder field. The About page says Robotomail is built by John Joubert, and the home page says: Email John, the founder. | [1, 2, 4] |
| Outside funding | none | C | About page: bootstrapped from the ground up, no venture funding. | [4] |
| Operating company and country | Tiny Bot Labs Limited; profile country GB | C | The Acceptable Use Policy says Robotomail is owned and operated by Tiny Bot Labs Limited. TrustMRR lists the country as GB. | [1, 5] |
| Prices | Free, then US$5, US$19, US$79 and US$199 a month | C | Pricing page, 3 November 2026. Solo has no annual discount; Starter and above cost about 50% less on annual billing. | [3] |
| Ways to connect | REST API, MCP server, CLI, SDKs, agent skill file | C | Home page. An agent can also sign up without a browser with POST /v1/signup, but the account owner must verify an email address before sending. | [2] |
| Sending rules | complaint rate under 0.05%, bounce rate under 3%, opt-in consent | C | Acceptable Use Policy, last updated 5 October 2026. It forbids mass unsolicited messages and purchased, rented or scraped lists, and it suspends a mailbox automatically above the bounce or complaint limits. | [5] |
| Blog posts | first post 28 March 2026, latest 30 October 2026 | C | Blog index read on 3 November 2026. Most posts compare email APIs or explain how to connect one agent framework. | [7] |
| Founder's X followers | 1,366 | C | Shown on the TrustMRR profile; not a payment figure. | [1] |

How to read this table: a grade A value comes from the company's Stripe account through TrustMRR, which reads the payment records with an API key. A grade B value is visible in the public page source. A grade C value is stated by the founder or the company's own pages. An X value was computed on this page from the rows above it.

## When did Robotomail launch, and how did it grow? Timeline

From the founding date in March 2026 to US$331 in monthly recurring revenue in November 2026. Each entry carries its grade.

- **14 March 2026** (grade C [1]): Founding date on the TrustMRR profile. The first Stripe revenue, US$15, arrives in March.
- **28 March 2026** (grade C [7]): First blog post: Best Email for AI Agents: What to Evaluate.
- **May 2026** (grade A [1]): US$357 in revenue, the highest month so far.
- **July to October 2026** (grade A [1, 7]): Monthly revenue between US$241 and US$274. The blog adds many guides for single agent frameworks such as LangGraph, AutoGen, n8n and the Vercel AI SDK.
- **5 October 2026** (grade C [5]): Latest update of the Acceptable Use Policy, with complaint and bounce limits and an opt-in rule.
- **3 November 2026** (grade A [1]): Stripe, read by TrustMRR: US$331 MRR, 17 active subscriptions, US$1,596 in total revenue.

## Why did Robotomail work?

### A mailbox a program can create

A personal mailbox such as Gmail expects a person: a browser sign-up, an OAuth consent screen and refresh tokens that expire. Robotomail replaces those steps with an API key and one POST request, and the home page says an agent can even sign up by API. This is the main thing a developer pays for.

### Replies as events

The hard part of email for an agent is receiving. Robotomail delivers each incoming message to the developer's code as a webhook, as a server-sent event stream for servers without a public URL, or through polling. The message keeps its thread, so the agent can answer in the same conversation.

### Many entry points for the same service

The same mailbox can be used from an MCP server in Claude Code or Cursor, from the REST API, from a command-line program or from a plain-text skill file that an agent reads. Each entry point has its own setup page and blog post, which also serve as search pages for one agent framework.

### A low first price

Solo costs US$5 a month for one mailbox, and the free plan works only with the owner's own address. A developer can test one agent for little money; a product with many agents moves to the US$79 or US$199 plans with 50 or 200 mailboxes.

## How it was built

Robotomail's pages describe the service; the founder has not published a build story in the sources read. The details below come from the company's pages (grade C) and its public page source (grade B).

- The About page says the service runs its own production mail servers with JMAP and SMTP, the protocols for reading and sending mail, and stores messages and attachments.
- For a customer's own domain, the service generates the DNS records MX, SPF, DKIM and DMARC and checks them automatically, so mail is signed for that domain.
- Per-mailbox daily send limits, suppression lists and automatic suspension above the bounce and complaint limits protect the shared sending reputation.
- The public web pages are built with Next.js, visible in the page source, and the page source loads DataFast analytics and a Google Ads conversion tag.
- Payments go through Stripe, which TrustMRR reads with an API key.

Sources: [1, 2, 4, 5]

## Who tried this before Robotomail, and why did they fail?

Four companies in our database of failed startups sold email help or developer communication tools before agents could write their own replies. The values below are from that database and are not independently verified.

The failed startups come from our database of dead startups, retold here in our own words; Its entries are AI-assisted summaries of public sources, so they carry no evidence grade.

### Zirtual (2011 to 2015; funding US$5.5M; cause: Ran out of cash)

- Promise: Virtual assistants for busy business owners who handle email and scheduling for them.
- Why it died: Every assistant was a paid person, so costs grew with every customer. The company expanded faster than its revenue and stopped in August 2015 when it could not meet payroll.
- Record: 

### SendGrid Labs (2015 to 2023; funding US$10M; cause: No market need)

- Promise: Ready-made communication tools for developers, built next to SendGrid's email delivery service.
- Why it died: Its experimental products did not find a clear market, and they had to compete with Twilio and with the parent company's own products.
- Record: 

### Threadable (2014 to 2017; funding US$500K; cause: Competition)

- Promise: A tool that turns team email threads into organized conversations.
- Why it died: Teams moved their conversations to Slack. Working with many different email systems was technically hard for a small team, and it ran out of cash.
- Record: 

### Skiff (2020 to 2024; funding US$14.2M; cause: No market need)

- Promise: An end-to-end encrypted email, documents and storage suite as a private alternative to Google Workspace.
- Why it died: Privacy alone did not make people leave free email services that they and their contacts already used.
- Record: 

## What changed

Before language models, a business that wanted someone to read and answer its email needed a person. Zirtual sold human assistants for email and scheduling and closed when the payroll grew faster than revenue. Email products for people, such as Threadable and Skiff, had to win users away from Gmail, Outlook and later Slack.

Robotomail does not write any replies itself. The customer's agent does that, with a model the customer chooses. Robotomail sells only the mailbox and the event plumbing, to a new kind of user that has no browser and cannot click a consent screen. The home page names the agents it serves: Claude, Codex, Cursor, Grok Bot, OpenClaw and Hermes.

## Can one person copy Robotomail now?

**Verdict: Yes, but the market is crowded and the figure is small.**

The founder's own comparison pages name competitors such as AgentMail, and general email APIs such as SendGrid, Mailgun and the Gmail API can be used by agents too. Running mail servers also means handling deliverability and abuse for every customer. The figure here, US$331 a month, is one person's early result, not proof that the model pays a salary.

1. Find a service that people use through a browser and that a program cannot sign up for or read without a person.
2. Sell the same service by API key, with an MCP server and a command-line program, so that an agent can use it without a browser.
3. Write one setup page per agent framework and per assistant, so that each one is a search page and a working guide.
4. Publish strict sending rules from the start, because a service that sends on behalf of programs attracts abuse.

**What is still open.** The same pattern can apply to other accounts that agents need and cannot easily create: phone numbers for SMS, calendars, document signing, or a payment card with strict limits. Each needs the same attention to abuse rules.

## What could go wrong for Robotomail?

- **A small and early figure.** US$331 a month and 17 subscriptions are verified by Stripe through TrustMRR, but they cover only about eight months, and monthly revenue was flat between US$241 and US$274 from July to October 2026. The profile's own user-count field shows 0. A reader should not take this as a full-time income.
- **Deliverability and abuse risk.** Every customer sends from shared infrastructure, and the Starter plan allows up to 15,000 sends a month per mailbox. The Acceptable Use Policy forbids unsolicited bulk email and scraped lists, and the site markets inbound and reply workflows, not cold outreach. If a few customers break the rules, the sending reputation of all customers suffers.
- **Testimonials signed with initials.** The pricing page shows two short testimonials signed only with the initials JD and JT and a use-case label. They do not use stock names or photos, but they could not be checked.
- **Competition.** The site's own comparison pages compare it with AgentMail, SendGrid, Mailgun and the Gmail API. Larger email providers could add mailboxes for agents to products that developers already pay for.
- **One-person operation.** The About page names only John Joubert. Running mail servers, support and abuse review alone is a risk for customers who depend on the mailbox in production.

## Sources

1. TrustMRR, Robotomail profile (Stripe-verified metrics, synced 3 November 2026) — https://trustmrr.com/startup/robotomail.md (grade A). Read the markdown profile, downloaded on 3 November 2026. MRR, subscriptions and revenue come from Stripe through an API key; the description, country, founding date, founder and pricing text are founder-entered (grade C).
2. Robotomail home page — https://robotomail.com/ (grade C). Read in full on 3 November 2026, including the page source. Source for the product, the ways to connect, the FAQ, the founder line and the purpose check.
3. Robotomail pricing page — https://robotomail.com/pricing (grade C). Read in full on 3 November 2026. Source for the plans, the limits, the annual discount and the testimonials.
4. Robotomail About page — https://robotomail.com/about (grade C). Read in full on 3 November 2026. Source for the founder, the funding status and the mail server details.
5. Robotomail Acceptable Use Policy, last updated 5 October 2026 — https://robotomail.com/acceptable-use (grade C). Read in full on 3 November 2026. Source for the operating company and the sending rules.
6. Robotomail use case: Turn incoming inquiries into the next conversation (lead qualification) — https://robotomail.com/use-cases/lead-qualification (grade C). Read in full on 3 November 2026 for the purpose check. It describes replies to inbound inquiries and tells customers to check consent before follow-ups.
7. Robotomail blog index — https://robotomail.com/blog (grade C). Read the list of posts and dates on 3 November 2026. Not used for numbers.
8. Database of failed startups, local export — /method/#dead (grade C). Local export. AI-written summaries, not independently verified. Source for the failed predecessors.