An agency's growth on Upwork Insights is measured, not estimated: the index reads the total earned figure on the agency's public Upwork page, reads it again at least 14 days later, and the difference is money the agency actually earned in that window. Annualised, that difference is the run-rate, and it is the only growth figure on the site. Until two reads exist, the agency page says "pending" rather than printing a number.
What the public page gives us
Every Upwork agency page publishes a lifetime counter: total earned, alongside total jobs and total hours. Upwork maintains it; the index only reads it. The counter has two properties that make it useful for measuring growth. It only goes up, because it is a lifetime sum, and it is stated to the dollar on most pages, rounded on some. What it does not say is when the money was earned. An agency showing a large figure might have earned it last year or ten years ago.
Reading the counter twice solves that. The observation is the unit of the index: a timestamped read of the page, with every public field stored. Two observations of the same agency bracket a window, and the change in total earned over that window is earnings that happened inside it. Nothing is inferred about which contracts paid or when; the sum simply moved.
The 14-day floor and the 90-day window
Two reads a day apart would produce a number, but a noisy one: a single invoice clearing would show as an enormous annual pace. The index therefore requires the two observations to be at least 14 days apart before it computes anything. Where more than two reads exist, it uses the newest window of up to roughly 90 days, so that the run-rate reflects the recent quarter rather than the whole history and does not swing on one payment.
The arithmetic is plain. Take the change in total earned over the window, divide by the length of the window in days, multiply by 365. The result is stated per year on the agency page, labelled "Run-rate, measured", and the agencies ranking can be sorted by it. Archived captures of the page from the Internet Archive count as earlier observations where they exist, which is why some agencies show a run-rate from their first live read. The full procedure is in methodology, section 2.
Why run-rate beats an estimated MRR
Other leaderboards print a monthly revenue figure for every agency. The usual recipe takes the most recently ended contract, or the visible contract values from the last few months, and divides. There are three problems with that, and the run-rate avoids all of them.
First, the public page shows contract values only for hourly work, so fixed-price earnings vanish from the estimate. Second, a contract that ended last week says nothing about next month; an estimate built on it is a guess dressed as a figure. Third, nothing on the page states when money was earned, so any monthly figure from a single read is a modelling assumption. The run-rate uses one source, the lifetime counter, read twice, and the figure it produces is a fact about the window rather than a forecast. Its cost is patience: a new agency in the index waits at least 14 days for its first run-rate.
Lifetime pace, the labelled estimate
Beside the measured run-rate the agency page shows one estimate, clearly labelled: lifetime pace, which is total earned divided by the number of years since the agency joined Upwork. It is a floor on historical throughput, not a current figure, because it spreads everything evenly across the years and most agencies did not earn evenly.
It is useful in two ways. For an agency with one observation, it is the only pace figure available, and it is honest about being an average. For an agency with a run-rate, the comparison between the two is the momentum component of the Index Score: an agency earning faster now than its lifetime average is growing, one earning slower has cooled. The second estimate on the page, realised hourly, is total earned over billed hours; fixed-price work inflates it, so it sits beside the rate card as context and is never used for ranking.
How to get a run-rate sooner
The index re-reads every page on a rolling schedule, so most agencies acquire a second observation within a few weeks of their first. Claimed pages are read weekly, which brings the first run-rate forward and keeps it current afterwards; claiming needs no Upwork login. Until then the agency page shows its observations as a table, each with the earned figure, the jobs count and the JSS as read, so the raw material is visible even before the index computes anything from it.
Frequently asked questions
- Why does my agency page say "pending" for run-rate?
- Because the index has read your page only once, or the reads it has are fewer than 14 days apart. A run-rate needs two observations with at least 14 days between them. Claiming the page moves it to weekly reads.
- Is the run-rate the agency's revenue?
- It is annualised Upwork earnings over the most recent measured window, which is revenue earned through Upwork before Upwork's fees are considered. Work billed outside Upwork is invisible to it, and the agency's costs are not part of it.
- Can a run-rate be zero?
- Yes. If total earned did not change between two observations at least 14 days apart, the run-rate for that window is zero, and the agency page shows it. That is a measurement, not a judgement: it means no payment cleared in the window.