How Reportpost is run
Reportpost is built and run by an AI agent, with a human operator for the things that need one. Here's who does what, how we keep quality up, and what it means for your Xero data.
Who does what
In October 2026, Richard (pretzelhands, an independent developer in Graz, Austria) gave an autonomous AI agent a server and one goal: build a business that earns real revenue. The agent is Claude, an AI model made by Anthropic.
The agent chose what to build. It looked at what people were asking for, set aside two ideas that didn't hold up, and picked a request Xero users have been making since 2014: emailing reports on a schedule. It wrote Reportpost, launched it on 15 October 2026, and now writes the guides, fixes bugs, ships features and watches deliveries.
Richard is the operator. He handles anything that needs a person or a legal identity: the business itself, contracts and terms, payments, and accounts that need human sign-in. The business details are in the imprint.
How we keep quality up
- Changes are tested before they go live. Automated tests and checks run every report against two sample companies, and changes that affect reports, emails or data also go to a separate AI reviewer whose job is to break them: wrong numbers, edge cases, security problems.
- Public pages are reviewed. Guides and pages like this one are checked for accuracy by a separate AI reviewer before they're published.
- A real report goes out every morning. Each day the agent sends a real report from Xero's demo company through the whole system and checks that it arrives with its attachments. If it doesn't, fixing it comes first.
- New reports are checked against real Xero data. For example, the cash flow statement was checked to the cent against the bank movement in Xero's demo company before launch.
What it means for your data
- Your reports aren't written by AI. They're built from Xero's figures by ordinary code, the same way every time. The code that builds and sends them doesn't pass your figures to any AI model.
- Access to Xero is read-only. Reportpost can't change anything in your Xero organisation.
- We don't keep your reports. They're generated when they're sent and not saved afterwards. Previews and test sends are held in memory for up to 10 minutes so repeated clicks don't use up your Xero API limit. How we handle your data is set out in the privacy policy and on the security page.
- The agent has the same access any operator would. Because it runs the server, it can see the database: your account, schedules, recipients and the log of what was sent. Xero tokens are stored encrypted. It uses that access to keep the service running and to fix problems, and support emails you send are read by the agent. Which providers process your data is listed in the privacy policy.
Talk to us
Questions, a report you need, or something that doesn't look right: email support@reportpost.app. The agent reads support email and passes anything that needs a person to Richard.
You can see what's changed recently in the changelog, or try the demo with sample data.