What a Meeting Costs the Company, and What the Number Is For

What the ticker actually computes

Three inputs, one formula, five outputs. The cost per second is attendees times the hourly rate divided by 3,600; the big number on screen is that multiplied by the seconds since you pressed Start. Under it sit the cost per person, the cost per minute, the projection to one hour, and a line converting the running total into coffees and pizzas. Nothing else happens, and nothing is stored.

Two of those deserve a warning. The coffees-and-pizzas line divides the running total by 5 and by 15, and those two divisors are hard-coded — they do not change when you switch the currency picker, which offers twenty-one currencies from the euro to the Angolan kwanza. And the elapsed counter does not read the clock: it adds a quarter of a second every time a 250-millisecond timer fires. Browsers throttle timers in background tabs to roughly one per second, so a ticker left running in a tab you are not looking at counts about four times too slowly. Keep the tab in front, or take the projection instead.

Fully loaded: what it covers, and what nobody measures

A salary is what lands in someone's account. What an hour of their attention costs the company is larger, and the gap has a name: employer contributions, insurance, retirement, paid leave. The Bureau of Labor Statistics measures it directly. In March 2026 private-industry employers paid $32.60 in wages and salaries and $14.01 in benefits for every hour worked, a total of $46.61 — so total compensation is about 1.43 times wages. Across all civilian workers it was $33.72 and $15.60 for a total of $49.32, a ratio of 1.46. In state and local government, where benefits are richer, wages were only 61.5 per cent of the bill and the ratio is 1.63.

A common rule of thumb puts the loaded cost at 1.25 to 1.4 times gross. Against the BLS series that is low at the top end: benefits alone already take private industry to 1.43 and government employers past 1.6. It also invites a comparison that does not hold, because the two sides of the Atlantic count differently. BLS counts paid leave — vacation, holidays, sick days — as a benefit. Eurostat counts payment for days not worked inside wages and salaries, and its non-wage costs are employers' social contributions plus employment taxes minus subsidies. So a European share that looks smaller is not measuring a cheaper employee; it is measuring a different thing. Use the ratio for your own market and do not convert one into the other.

Then there is the part neither statistic contains. Equipment, software licences, the square metres somebody sits on, the share of the IT team that keeps their laptop working — real costs, all of them, and no public series measures them per employee per hour. Some organisations know their own figure from their own accounts. If you do not, leave it out and say so, which is what this article does. A stale invented overhead is worse than an honest gap, because it survives into every calculation somebody builds on top of it.

There is no multiplier field, so the rate box is the multiplier

This is the single most important thing to know about the tool. Nothing in it grosses your figure up. The box is labelled "Avg. hourly rate", and whatever you put there is multiplied straight by the head count and the seconds. Type a payroll rate and the ticker will happily under-report the cost by a third and look precise while doing it.

So do the multiplication before you open the tool. Take the gross hourly figure — annual salary divided by the hours actually worked in a year — multiply by the ratio for your market, and type the result. Round to something you can defend rather than to a false decimal: the input is an average across a room of people on different salaries, and a number carried to the cent implies a precision the input never had.

The number is for a decision, not for shaming anyone

A ticker projected onto a wall is a party trick. It produces a gasp, a joke, and no change, because a single meeting's number answers a question nobody asked: was this hour worth it? Almost every hour is worth it or is not for reasons that have nothing to do with payroll. Judgement, disagreement, a decision that needed six people in one place — those are not priced by a stopwatch.

The question the number does answer is about the recurring one. A standing meeting is not a decision that was made once; it is a decision that is being remade, unexamined, every week. Multiply the session by the number of times it happens in a year and you have something you can hold next to its alternative. Eight people, half an hour, forty-six weeks: $17,480 in the United States example above, which is a hire, a piece of software, or a piece of research. That is a comparison a room can actually have.

A written update costs writing time plus reading time

The comparison is only honest if the alternative is priced properly, and "write it up instead" is not free. It has two halves. Someone spends time writing, once. Then every reader spends time reading, in parallel — which is the whole reason the alternative is cheaper, because reading is faster than listening and eight people do it at the same time rather than in sequence.

Run it at the same rate, so the two sides are comparable. Twenty-five minutes to write at $95 an hour is $39.58. Seven readers at four minutes each is $44.33. Total $83.92, against $380 for the meeting — about a fifth. Over forty-six weeks that is $3,860 against $17,480. The arithmetic here is done in the text, not by the tool: the ticker has no second scenario and no memo mode, so the honest way to use it for this is to run it twice, once with eight attendees for thirty minutes and once with the writing and reading minutes folded into a single elapsed figure.

Where the meeting wins is worth naming too, because the arithmetic always favours the memo and the arithmetic is not the whole answer. A memo is one-way. When the point is to reach a decision that several people have to argue their way to, or to hear the thing nobody would write down, the meeting is the cheaper instrument even at twenty times the price, because the alternative is four days of asynchronous misunderstanding. What the number kills is the recurring status update, which is a memo being read aloud.

Frequently asked questions

Does the calculator apply a fully loaded cost multiplier?

No. There is no overhead field and no hidden factor. The whole computation is attendees × hourly rate × seconds elapsed ÷ 3,600, and the rate is exactly what you typed. If you enter a payroll rate you get a payroll answer, which understates the real cost by roughly a third in US private industry. Gross the rate up yourself before entering it.

Why does the tool show zero when I open it?

Because it is a ticker, not a planner: the cost is the rate multiplied by the seconds since you pressed Start, and before that there are no seconds. If you want a number without running a clock, read the one-hour projection, which is attendees × rate and updates as soon as you change either. For a thirty-minute meeting, halve it.

What hourly rate should I actually type in?

The average gross hourly pay of the people in the room, multiplied by a loaded-cost ratio for your market. From the BLS's March 2026 figures, US private-industry total compensation was about 1.43 times wages and salaries; all civilian workers, 1.46; state and local government, 1.63. Those ratios cover benefits only. Equipment and premises are on top and no public series measures them per employee, so either use a figure from your own accounts or leave the gap open and say so.

Is a meeting always more expensive than a written update?

In money, nearly always, because readers read in parallel while listeners listen in sequence. But the arithmetic only prices the time, not the outcome. A memo cannot hold an argument, cannot surface the objection nobody would write down, and cannot get six people to commit to the same decision in one sitting. Use the number against the recurring status update, which really is a memo read aloud, and not against the meeting where something is genuinely being decided.

Does the timer stay accurate if I switch to another tab?

No, and it under-counts rather than over-counts. The elapsed figure is not read from the system clock: the tool adds a quarter of a second each time a 250-millisecond timer fires. Browsers throttle timers in hidden tabs to about one per second, so an hour spent in a background tab can register as roughly a quarter of an hour, and the cost with it. Keep the tab visible while it runs, or reconstruct the cost afterwards from the one-hour projection and the real duration.