Meetmeter User Guide: How to Calculate the Real Cost of Any Meeting

Most teams treat meetings as free. They aren’t. Meetmeter makes the cost visible — in real time, in dollars, while the meeting is still happening. This guide covers everything: how the calculator works, how to read the metrics, how to use the history and budget tools, and how to get your team to actually care about the number on the screen.

What Meetmeter is — and what it isn’t

Meetmeter is a real-time meeting cost calculator. You add the people in the room, set their hourly rates, press start, and watch the cost accumulate in real time — the same way a taxi meter runs. By the time the meeting ends, you have an exact number: what this conversation cost in salary, before anyone has shipped a line of code or closed a deal.

What it isn’t: a meeting scheduler, a note-taker, or a productivity suite. Meetmeter does one thing deliberately — it makes the invisible cost of a meeting visible at the moment it’s happening. That single intervention, consistently applied, changes how teams think about whether a meeting should exist at all.

The core insight behind Meetmeter A 60-minute meeting with 8 people at an average rate of $85/h costs $680 in salary alone — before overhead, before the 23-minute focus recovery each developer needs afterward. Most teams have never seen that number. Meetmeter puts it on the screen, in real time, where it can’t be ignored.

The real-time calculator — how it works

The calculator is the core of Meetmeter. Everything else — history, analytics, budget — feeds from the sessions you run here. Understanding how to configure it correctly takes about two minutes and makes every subsequent session more accurate.

01

Set your participant rates

Meetmeter uses three role tiers by default — Junior ($25/h), Mid ($45/h), and Senior ($110/h). These are fully editable: tap or click any rate field and type your own number. The rates represent fully-loaded hourly cost — salary plus employer taxes and benefits. If you’re not sure of the exact figure, use 1.3× the base salary divided by 2,080 annual working hours as a starting estimate.

02

Add participants by role

Use the + and − buttons to add the number of people in each role attending the meeting. You can also tap the number directly and type it. There’s no limit — Meetmeter handles up to 999 participants per role, which covers every all-hands meeting you’ll ever run and several that you probably shouldn’t.

03

Toggle real cost (optional)

The «real cost» toggle applies a 1.33× multiplier to account for overhead costs beyond salary — office space, software licences, employer contributions, and the indirect cost of context-switching. Enable it when presenting to management or when you want the most accurate total economic cost of a meeting. Disable it for simple salary-only calculations.

04

Press Start — and let the meter run

The cost counter starts immediately and updates in real time. You can pause at any point — the timer holds the accumulated time and cost — and resume when the meeting continues. The bar indicator on the right tracks elapsed time against a 60-minute reference: green up to 15 minutes, yellow from 15 to 45, red beyond 45. If you’re in the red zone, the meeting is almost certainly past the point of diminishing returns.

05

Save the session when it ends

When the meeting is over, press Save. A modal asks you to name the session and tag it by category — Daily, Planning, Retrospective, Review, or Meeting. The name and tag appear in your history and feed the analytics panel. If you skip naming, the session saves as Uncategorized. You can delete any session from the history panel at any time.

Reading the live metrics panel

While the meter runs, three secondary metrics update alongside the main cost counter. Each one gives a different view of the same number — useful for different audiences in the room.

Metric What it shows When it’s useful
Cost per person Total cost divided by number of attendees Makes the individual stake visible — «this meeting has already cost each of you $42»
Cost per minute Current hourly rate divided by 60 Useful for deciding whether a tangent is worth pursuing — «this side conversation costs $8 per minute»
Projected monthly cost Current session cost × 3 meetings/week × 4.33 weeks The number that lands hardest in management conversations — turns a single meeting into an annual budget line

The three status zones — what the colours mean

The bar indicator and the timer colour change as the meeting progresses through three zones. They’re calibrated against research on meeting effectiveness and cognitive load — not arbitrary thresholds.

Green — under 15 minutes
Yellow — 15 to 45 minutes
Red — over 45 minutes

The green zone is where meetings produce the most value per minute — decisions get made, blockers get surfaced, alignment happens. The yellow zone is where most meetings live, and where discipline around agenda and time-keeping matters most. The red zone is where meetings consistently cost more than they return — the conversation has usually fragmented into side threads, and the original agenda item has long since been resolved or abandoned.

A note on the red zone Going red doesn’t mean the meeting was bad. Some decisions genuinely need 60+ minutes of collective thinking. What it does mean is that the meeting should have had an explicit plan for using that time — and that running red regularly, on the same recurring meeting, is a signal worth investigating.

Presentation mode — using Meetmeter in the room

Presentation mode is one of Meetmeter’s most practical features and the least obvious one. It hides the individual hourly rates from view while keeping the cost counter running — so you can project or share the screen during a meeting without revealing anyone’s salary to the room.

Activate it via the toggle in the top right of the calculator. The rate fields blur immediately. The cost counter, the timer, the metrics panel, and the bar indicator all remain fully visible. The meeting sees the number accumulating in real time. They don’t see how it’s calculated.

This is particularly effective in three scenarios: running the meter during a recurring meeting to make its cost visible to the whole team for the first time; presenting meeting cost data to senior leadership without exposing individual compensation; and using Meetmeter as a facilitation tool in workshops on meeting culture.

The history panel — your meeting cost record

Every saved session appears in the history panel below the calculator, sorted chronologically with the most recent first. The history stores up to 50 sessions locally in your browser — no account required, no data sent to any server.

View by week or month

Weekly and monthly charts

The bar chart at the top of the history panel shows your total meeting cost per day for the current week. Switch to monthly view to see the full month. Click any bar to filter the session list to that specific day — useful for reviewing what drove a spike in cost on a particular date.

Session statistics

Aggregate metrics

Above the session list, four summary stats update automatically: total sessions, total cost, total time, and average duration. These update based on the active filter — so if you’ve clicked a specific day in the chart, the stats reflect only that day’s meetings.

Zone rating

Session efficiency badge

Each session in the history list shows a zone badge — OK, Risk, or Critical — based on the duration at the time of saving. This gives you a quick visual read of which meetings in your history were well within healthy time boundaries and which ran long enough to warrant a review.

Export your data

CSV export

Export your meeting history as a CSV file — filtered by today, this week, this month, or all sessions. The export includes date, time, session name, category, duration, cost, team composition, and zone rating. Paste it into a spreadsheet and you have a full audit trail of your team’s meeting spend.

The analytics panel — where the patterns are

The analytics panel appears once you have at least two sessions saved in the current week. It doesn’t require any configuration — it reads your session history and surfaces the patterns automatically. There are three things it tells you that the raw history list doesn’t.

01

Your most expensive day of the week

The analytics panel identifies the day with the highest average meeting cost per session and flags it explicitly. This is usually the day with the most recurring meetings stacked together — Monday all-hands, Tuesday planning, Wednesday retrospective. Seeing it named changes the conversation about whether that day’s calendar makes structural sense.

02

Your highest-cost category

If you’ve been tagging sessions by category, the analytics panel surfaces the category that accounts for the highest proportion of your weekly meeting spend. For most engineering teams, it’s Planning or Daily. For most management teams, it’s Review. Whatever it is for your team, seeing the percentage — «Planning accounts for 61% of this week’s meeting cost» — gives you a specific target rather than a vague sense that meetings are expensive.

03

Your efficiency score

The efficiency score is a 0–100 index calculated from three factors: how concentrated your meeting cost is on a single day, how long your average session runs, and how many days per week you hold meetings. A score above 70 means well-distributed, reasonably short meetings. Below 40 means a structural problem worth addressing — usually either one extremely expensive day or chronically long sessions in a single category.

The monthly budget — setting a meeting spend limit

The budget panel lets you set a maximum monthly meeting cost for yourself or your team. Once set, a progress bar tracks your spend against the limit in real time — updating automatically as you save new sessions throughout the month.

To set a budget: open the budget panel, click the edit button, type your monthly limit, and press Enter or click Save. The limit persists across sessions — it stays set until you change it. There’s no right number for a monthly budget. A useful starting point is to calculate your current monthly spend from the history panel and set the limit at 20% below that. That’s a realistic reduction target that most teams can hit without structural changes in the first month.

Using the budget tool with a team The budget is stored locally per browser, so each team member tracks their own. For a team-level budget view, the most effective approach is to designate one person to run Meetmeter during shared meetings and track the aggregate. Export the CSV monthly, sum the costs in a spreadsheet, and compare against the team’s target. It takes about 5 minutes per month and produces data that most engineering managers have never had access to before.

Sharing and exporting — getting the data out

Meetmeter has three ways to get data out of the tool, each suited to a different use case.

Method What it produces Best for
Share as image PNG screenshot of the history panel with Meetmeter branding Slack, email, team retrospectives — fast visual proof of meeting cost
Export CSV Spreadsheet with all session data — date, cost, duration, category, zone Management reporting, monthly reviews, building a long-term cost dataset
Session summary image PNG of the post-meeting summary — cost, duration, team composition, zone Sharing a single meeting’s cost immediately after it ends — most impactful for in-the-moment culture change

The session summary image deserves a note. It appears automatically after you save a session. Sharing it in the team Slack channel immediately after a meeting — «this just cost us $340, here’s what we decided» — is consistently the single most effective way to change how teams think about meeting culture. Not a policy. Not a deck. Just a number, attached to a real meeting, shared in the channel where people can see it.

Using Meetmeter as a manager — the playbook

Individual contributors use Meetmeter to understand what meetings cost them personally. Managers use it differently — as a tool for making the case for change, tracking improvement over time, and creating a culture where meeting cost is a normal part of the conversation rather than an awkward topic nobody raises.

01

Run the meter in your next recurring meeting

Don’t announce it in advance. Open Meetmeter at the start of the meeting, configure the participants and rates, enable presentation mode, and share your screen. Let the number run in the background for the first 10 minutes. The effect is immediate — conversations tighten, tangents get cut, people start looking at the clock differently. Do this once per week for a month and track whether meeting durations change.

02

Use the monthly CSV to build a cost baseline

Export your team’s sessions at the end of each month. Sum the total cost. That number — your team’s monthly meeting spend — is the baseline against which every process change is measured. When you cancel a recurring meeting, you can point to the exact saving. When a new meeting format cuts session duration by 30%, the data shows it. Most engineering managers have never had this data. Meetmeter makes it routine.

03

Use the projected monthly cost in budget conversations

The projected monthly cost metric — visible in the live metrics panel during any session — is the number that lands hardest in management conversations. «Our weekly planning meeting projects to $2,400 per month in salary cost» is a concrete budget line, not an abstract complaint about too many meetings. It belongs in quarterly reviews, in engineering all-hands, and in any conversation where you’re making the case for fewer or shorter meetings.

04

Share the session summary after high-cost meetings

Make it a habit: after any meeting that crosses a threshold you set — say, $500 — post the session summary image in the team channel. Not as a criticism. As information. «This is what today’s planning session cost. Here’s what we decided. Here’s the team composition.» Over time, the team internalises the number. Meetings start getting shorter not because of a policy, but because people can feel the cost.

Why making the cost visible actually changes behaviour

Meetmeter is built on a simple behavioural premise: people make different decisions when costs are visible than when they’re invisible. This isn’t a theory — it’s the same principle behind Shopify’s internal meeting cost calculator, which their CFO credited with fundamentally changing how employees think about scheduling meetings after their 2023 calendar purge.

The psychological mechanism is straightforward. When a meeting has no visible price tag, the implicit assumption is that it’s free. Free things get scheduled without much scrutiny. When a meeting has a number attached to it — a number that updates in real time, that everyone in the room can see — the calculation changes. The question stops being «should we have this meeting» and starts being «is this decision worth $680.»

Most teams that use Meetmeter consistently for 30 days report two changes without any explicit policy intervention: average meeting duration drops, and the number of recurring meetings decreases as people become unwilling to schedule something they’ve watched cost $400 for no clear output.

The compounding effect A 10-person engineering team that reduces average meeting duration by 20% and eliminates two recurring meetings per month saves approximately $28,000 per year in direct salary cost — without changing headcount, tools, or process. Meetmeter doesn’t produce that saving. The visibility does. Meetmeter just provides the visibility.

FAQ — Meetmeter

Is my meeting data stored anywhere?

No. All data — session history, rates, budget settings — is stored locally in your browser using localStorage. Nothing is sent to any server. Meetmeter has no account system and no backend database. Clearing your browser data will delete your history, so if you want to keep a permanent record, export the CSV regularly.

How do I calculate the right hourly rate for my team?

For a fully-loaded rate, take the annual base salary and multiply by 1.3 to account for employer costs (taxes, benefits, equipment). Then divide by 2,080 — the standard number of working hours in a year. For example: a $90,000 salary × 1.3 ÷ 2,080 = approximately $56/h fully loaded. The default rates in Meetmeter (Junior $25, Mid $45, Senior $110) are conservative estimates for US market rates — adjust them to match your team’s actual compensation.

What does the «real cost» toggle add?

The real cost toggle applies a 1.33× multiplier to the base salary cost. This accounts for indirect costs that don’t appear in the hourly rate: office space, software licences, employer-side tax contributions, and the opportunity cost of context-switching. Enable it when you want the most complete picture of what a meeting actually costs the business. Disable it when you want a conservative, salary-only figure.

Can I use Meetmeter for a team without revealing individual salaries?

Yes — that’s exactly what presentation mode is for. Enable it before sharing your screen and the rate fields blur immediately. The cost counter, metrics, and bar indicator remain fully visible. The room sees the total cost accumulating; they don’t see the individual rates that produce it.

Why does Meetmeter only store 50 sessions?

localStorage has a size limit per domain. 50 sessions covers approximately one to two months of typical meeting frequency for most teams — enough history to produce meaningful analytics without approaching browser storage limits. Export your CSV monthly if you want a longer-term record.

How does the efficiency score work?

The efficiency score (0–100) is calculated from three weighted factors: cost concentration (how much of your weekly meeting spend falls on a single day, weighted at 50%), average session duration against a 30-minute benchmark (30%), and spread across days of the week (20%). A score above 70 indicates healthy distribution and reasonable session lengths. Below 40 indicates a structural issue — usually either one extremely expensive day or chronically long sessions in a specific category.