MRR, churn, LTV and every MRR movement, with each month remembered as it closes.
Connect ChartMogul with an API key and Memtro reads MRR, ARR, customer count, churn, LTV and ARPA over any period, the MRR movements behind it, and customers by email or billing id with their subscriptions. Once a calendar month has ended, the hourly sync writes its metrics and movements into memory. When you ask, and once an administrator has granted each action by name, it can create and update customers and leads, add tags, notes and call logs, set follow-up tasks and add opportunities. Merging customers is undone only by unmerging, and deleting a customer permanently removes its billing data.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ChartMogul tool, reads what it needs, and answers with the source cited.
These tools change something in ChartMogul. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ChartMogul, choosing the same kinds; the tab shows ChartMogul's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. ChartMogul signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce ChartMogul is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What was MRR at the end of October, and how did it change from September?
Which customers churned in the last 30 days, and how much MRR went with them?
What is jane@acme.com subscribed to, and what is her MRR?
How much expansion MRR came from the Growth plan in Q3?
Add a note to Acme Ltd that they asked for a discount at renewal
The board pack is due Friday. The founder asks for October's MRR, ARR, customer count and both churn rates against September. Memtro answers from the month already in memory, and reaches ChartMogul only for the movements behind the churn.
Ruth Okoye sees Acme Ltd's contraction last month and asks Memtro to log what the customer told her and set a follow-up. Memtro adds a note to Acme's timeline in ChartMogul, which everyone in the account can see, and creates a task assigned to Ruth by email, due next Tuesday.
The teams that lean on ChartMogul most, a question each of them asks, and what they connect beside it.
A record in ChartMogul is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn ChartMogul open Profile → View Profile → API Keys. A read-only key covers every read and keeps Memtro to reading, and the actions need a key with read and write access
In Memtro open Connections → ChartMogul, paste the API key and connect. Memtro checks the key and lists the billing systems feeding the account
The first sync records the last complete month, and a connection that has fallen behind catches up three months an hour
Ask what MRR did last month and where the churn came from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ChartMogul tools are the same everywhere.
Only when you ask, and only what it has been granted: create a customer or lead, or change its company, location, owner, lead status, website or primary contact; add tags to a customer; add a note or call log to a customer; create a follow-up task for a team member, or change or complete one; add a sales opportunity to a customer; merge one customer into another; delete a customer and all its billing data (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed ChartMogul records into memory as entities.
API key. In ChartMogul open Profile → View Profile → API Keys. A read-only key covers every read and keeps Memtro to reading, and the actions need a key with read and write access.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ChartMogul, choosing the same kinds; the tab shows ChartMogul's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
