Exit rate calculator
If last month brought in 50,000 of recurring revenue, the exit run rate is 600,000: that month multiplied by twelve, as quoted in board packs and term sheets. A pre-revenue month simply gives zero. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Monthly revenue
- 50,000
- Months per year
- 12
- Exit rate
- 600,000
Exit run rate, also called exit ARR when the top line is subscription revenue, is the annualized snapshot of a company's last month of recurring revenue. Founders, operators, and investors use that single figure to describe the business as if the most recent month continued for a full year, without mixing in earlier months that may have been smaller or larger. This exit rate calculator accepts one finite number — last month's recurring revenue — multiplies it by twelve, and returns the annualized exit run rate together with the monthly figure it started from. Values that are missing, empty, or not a number fail the same way and are not billed. Zero is a legitimate outcome: a pre-revenue month still has an exit run rate of zero.
How last month's recurring revenue becomes an exit run rate
Exit run rate asks a narrow question: if the most recent month of recurring revenue continued for twelve months, what annual figure would that book print. Multiplying by twelve is the convention investors quote on a term sheet and operators quote in a board pack: it is a going-in annualization of the exit month, not an average of the trailing year and not a forecast that bakes in growth.
A fifty-thousand last month prints an exit run rate of six hundred thousand because twelve times fifty thousand is six hundred thousand. Zero monthly revenue is a legitimate outcome and is not an error: a pre-revenue month still has an exit run rate of zero once the figure is finite and non-negative. You supply one finite non-negative number that already lives in one currency and one month; the calculator multiplies by twelve and rounds the annualized figure half-up to two decimal places so goldens compare byte-for-byte across runtimes.
This is last-month times twelve, not a cohort walk, not a recognized-revenue schedule, and not a live quote.
What you can do with it
Month-end close before the ARR model
Turn last month's recurring revenue into one exit run rate line before you open a full ARR model or a board pack.
Fundraising memos and term sheets
Pin exit ARR next to a trailing-twelve-month reconstruction so a data room shares one going-in annualization rather than unscaled MRR.
RevOps packs versus retention walks
Drop billing-export MRR into one last-month × 12 figure beside net revenue retention and a booked-versus-billed view.
FAQ
How is exit run rate calculated?
The annualized figure rounds half-up to two decimal places.
What happens if monthly revenue is negative?
Exit run rate is undefined for a negative recurring book, so the calculator does not return a signed annualization. A value that is not a finite number is also rejected. Those failures are not billed.
Is this trailing-twelve-month ARR or last-month annualization?
Last-month annualization. The identity uses the final month's recurring revenue only. It does not average twelve months, apply net revenue retention, or bake in a growth rate.
Can monthly revenue be zero?
Yes. A pre-revenue month still has an exit run rate of zero.
Does exit run rate include growth or retention?
No. It takes last month exactly as it was and multiplies it by twelve. It applies no growth rate, no net revenue retention and no currency conversion, so it is a snapshot, not a forecast.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fin/exit-rate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"monthly_revenue":50000}'const res = await fetch("https://api.kit.forhosting.com/fin/exit-rate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"monthly_revenue": 50000
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fin/exit-rate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"monthly_revenue": 50000
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fin/exit-rate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"monthly_revenue":50000}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"monthly_revenue":50000}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fin/exit-rate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"monthly_revenue": 50000
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fin.exit_rate",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Negative monthly revenue is rejected with invalid_input because a run rate is not defined for a negative recurring book.
How last month's recurring revenue becomes an exit run rate
The identity this calculator uses is exit_rate equals monthly_revenue times twelve. monthly_revenue is last month's recurring revenue in one currency — typically monthly recurring revenue, or MRR, for a subscription business, but the same identity applies to any recurring book you already measure on a monthly cadence, such as retainers, maintenance contracts, or billed usage that has been converted to a monthly run. Negative monthly revenue is not a legitimate run rate: a negative recurring book would annualize into a nonsense annual figure, so the task fails with invalid_input rather than returning a signed annualization that a model might treat as a real exit ARR. This calculator does not reconstruct trailing-twelve-month ARR from twelve separate months, does not apply net revenue retention or a growth rate, does not convert currencies, and does not look up a live billing export.
Input contract, response shape, and error behaviour
Zero is allowed: a pre-revenue month still produces a finite exit run rate of zero rather than an error. A fractional month such as one thousand two hundred thirty-four point fifty-six annualizes to fourteen thousand eight hundred fourteen point seventy-two after the same half-up money rounding. POST a JSON body with one required finite number: monthly_revenue, the final month's recurring revenue in one currency. Aliases mrr, monthly_recurring_revenue, last_month_revenue, and recurring_revenue map to the same field so a worksheet can keep its column names. The field may arrive as a JSON number or a numeric string. Missing fields, empty strings, and non-finite values — NaN, Infinity, or text that does not parse as a number — fail with invalid_input naming monthly_revenue. Those failures are not billed. A negative monthly_revenue fails because exit run rate is undefined for negative monthly revenue; the message names the field so a form can mark that control instead of a generic alert. On success the body echoes monthly_revenue, reports months_per_year as twelve so a client does not have to hard-code the convention, returns exit_rate as monthly_revenue times twelve rounded half-up to two decimal places, and includes a formula string restating the identity. Example: fifty thousand of last-month recurring revenue yields months_per_year of twelve and an exit_rate of six hundred thousand. Pair the JSON with your own rule for which month is the exit month and which lines count as recurring — billed usage, one-off professional services, and deferred revenue are not the same book — because this endpoint multiplies the one number you send; it does not rebuild a billing ledger, choose a recognition convention, or look up a payment processor.
Where an exit rate calculator earns its keep
Operators closing a month use an exit rate calculator to turn last month's recurring revenue into one comparable annual line before they open a full ARR model or a fundraising memo. Revenue-operations and investor-relations teams drop MRR from the billing export into this identity and compare that exit run rate with net revenue retention and a booked-versus-billed walk rather than treating any one of those as a substitute. This is a different search and a different job from trailing-twelve-month ARR, from net revenue retention, from a rule-of-forty score, and from a simple annualization of total revenue that is not recurring: those tools start from different lines and answer different questions. Failed validation does not consume balance. Founders and finance partners re-run the same field when a board pack, a data room, or a term sheet asks for exit ARR, then pin exit_rate next to a trailing-twelve-month reconstruction so every memo starts from one going-in annualization rather than from a monthly figure that has not been scaled. Keep monthly_revenue finite and non-negative, pin the rounded exit_rate in tests, and you get a reproducible last-month annualization for teasers, LMS plugins, and edge workers without standing up a general ledger of your own.
Technical questions
What does the exit rate calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.