Home / Businesses / MRR Bridge and Net Revenue Retention
MRR Bridge and Net Revenue Retention
Explain how recurring revenue moved between two snapshots: new, expansion, contraction, churn and reactivation MRR, net and gross revenue retention, logo churn, with a signed record.
Live
- What it does
- Explain how recurring revenue moved between two snapshots: new, expansion, contraction, churn and reactivation MRR, net and gross revenue retention, logo churn, with a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
mrr_bridgeat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Live: open today. Free
New to this? Start here.
What it does
MRR Bridge and Net Revenue Retention is for agents that report subscription revenue for a business (board decks, investor updates, monthly close) and need the same bridge and retention figures from the same data every time. Explain how monthly recurring revenue (MRR) moved between two subscription snapshots. Send each customer's MRR at the start and at the end (customer code and amount), and mark customers at the end who had paid before the start snapshot but were at 0 in it (returning). Get back the MRR bridge: starting MRR, new, reactivation, expansion, contraction, churn and ending MRR, with the customer count for each movement, net and gross revenue retention, logo churn, the quick ratio, and the movement for every customer. It is one of the Sales (CRM) department tools LLPRO builds for the work agents do across business software (Stripe, Chargebee, Recurly, Salesforce, HubSpot). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that report subscription revenue for a business (board decks, investor updates, monthly close) and need the same bridge and retention figures from the same data every time.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, start up to 200 entries, end up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not read your billing system: the MRR figures are taken as given. Does not turn annual, quarterly or usage billing into MRR (send monthly amounts: an annual contract divided by 12), convert currencies, or annualize: the retention figures cover the span between your two snapshots (send snapshots 12 months apart for yearly NRR). Does not apply a company's own published NRR definition (many public companies use trailing twelve months, ARR or revenue instead of MRR), discounts or one-time fees. Not accounting advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "mrr_bridge", "arguments": {"start": [{"customer": "A", "mrr": 100}, {"customer": "B", "mrr": 200}, {"customer": "C", "mrr": 300}, {"customer": "D", "mrr": 50}], "end": [{"customer": "A", "mrr": 150}, {"customer": "B", "mrr": 200}, {"customer": "C", "mrr": 250}, {"customer": "E", "mrr": 400}, {"customer": "F", "mrr": 80, "returning": true}]}}}For agents
Tool mrr_bridge on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:invfthgyrvzy63vowlvlhrsh3q): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): Ai5R+yc4GcMz2x4avjUZ0YOZ1yrmH2BNmNulqo9C/I0=
For agents that search MCP registries for MRR bridge, net revenue retention, churn tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: An MRR bridge is one step of subscription reporting. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card