See the real price of every meeting
I built MeetCost to turn raw salary numbers into a clear meeting expense. The core idea is simple: every person invited to a meeting earns money for the time they spend in that meeting. By converting each attendee’s annual compensation into an hourly rate and then multiplying by the meeting length, you get a payroll‑based cost that reflects actual money spent.
The process follows four distinct steps. First, you collect the annual salary (or contract rate) for each person who will attend. Second, you turn that yearly figure into an hourly wage by dividing by the standard work hours in a year. Third, you multiply the hourly wage by the meeting duration in hours to obtain the cost for that individual. Fourth, you add together the individual costs to arrive at the total meeting price.
To make the steps concrete, here is a table that shows the flow without using any real numbers.
| Step | Description | Output variable |
|---|---|---|
| 1 | Gather attendee compensation | Annual salary per person |
| 2 | Convert to hourly rate | Hourly wage = salary ÷ work hours per year |
| 3 | Apply meeting length | Individual cost = hourly wage × meeting hours |
| 4 | Sum individual costs | Total meeting cost = Σ individual costs |
Each step uses only basic arithmetic, so the tool runs instantly in the browser. No external calls, no hidden fees, and no need for a server‑side calculation. The transparency of the formula means you can verify the result with a calculator or a spreadsheet if you wish.
You start by entering the annual compensation for each participant. If a person works part‑time, you can input their pro‑rata salary. For contractors, you can use the agreed daily or monthly rate and convert it to an annual equivalent before entering. The field accepts any numeric value, and you can add as many rows as you need.
The tool assumes a standard full‑time year of 2,080 hours (40 hours per week × 52 weeks). It divides the entered salary by 2,080 to produce an hourly wage. If your organization uses a different baseline (for example, 1,800 hours to account for holidays), you can adjust the hidden constant in the settings panel.
Next you specify the meeting duration in hours and fractions of an hour. Entering 1.5 captures a ninety‑minute session. The tool multiplies the hourly wage from step two by this duration to compute the cost for that attendee.
Finally, the tool adds together all individual costs. The result appears as a single number labeled “Meeting cost”. Because the calculation is linear, you can see how each additional participant or each extra minute changes the total in real time.
MeetCost asks for three categories of information: attendee compensation, meeting length, and optional adjustments. Providing accurate data ensures the output reflects true payroll expense rather than a rough guess.
For each person, enter their gross annual salary before taxes and benefits. If you only know a monthly figure, multiply by twelve. If you know an hourly rate, multiply by the standard yearly hours to get an annual equivalent, then enter that number. The tool does not store or share these values; they remain in your browser session only.
Specify the total time the meeting will run, expressed in hours. You can use decimal fractions for minutes (for example, 0.25 for fifteen minutes). The tool treats the length as a continuous variable, so a meeting that lasts 2.75 hours is processed exactly as entered.
You can toggle a setting to include estimated benefits cost. If enabled, the tool adds a flat percentage (default 20 %) to each attendee’s hourly wage to approximate the employer’s share of health insurance, retirement contributions, and payroll taxes. Another toggle lets you exclude certain attendees from the calculation, useful when a participant is optional or when you want to see the cost of core decision‑makers only.
I want to be clear about the limits of MeetCost. The tool does not guarantee that the number it shows equals the exact financial impact of a meeting on your organization’s bottom line. It does not promise 100 % accuracy for every possible scenario, nor does it claim to never miss a cost factor. The calculation is based on the data you supply and the assumptions built into the tool; if those inputs are incomplete or the assumptions do not match your context, the result will be off.
Specifically, MeetCost does not:
Think of the output as a baseline payroll figure. It is useful for comparing meeting options, highlighting expensive gatherings, and starting conversations about meeting hygiene, but it should not be the sole basis for high‑stakes budgeting decisions.
When you express a meeting’s expense in payroll terms, you make the invisible visible. Many teams treat meetings as free because they do not see a line item in the budget. By attaching a salary‑derived price, you create a concrete signal that can influence behavior.
This approach aligns with guidance from reputable sources. For example, the NIST AI Risk Management Framework https://www.nist.gov/itl/ai-risk-management-framework stresses the importance of measuring resource use when evaluating any process, including collaborative activities. Knowing the payroll cost helps you assess whether a meeting’s outcomes justify the investment of employee time.
Additionally, viewing meetings through a payroll lens supports better prioritization. If a recurring status update costs several thousand dollars each month, you might explore alternatives such as asynchronous updates or a shorter stand‑up. The metric also aids in setting meeting policies: you can define a threshold above which a meeting requires explicit approval, encouraging teams to question the necessity of long gatherings.
Once you have the meeting cost, you can apply it in several practical ways.
Run the tool twice: once for a proposed in‑person session and once for a remote version. If the remote version eliminates travel time, you may see a lower hourly cost because attendees can join from their desks without commuting. The difference highlights the financial impact of logistics.
Add or remove participants and watch the total change. If removing a single high‑salary attendee cuts the cost by a noticeable amount, you can assess whether that person’s presence is essential or whether their input could be gathered via a brief email or a recorded update.
Some organizations allocate a quarterly budget for meeting time. By summing the costs of all planned meetings, you can see whether you stay within that limit. If the projected total exceeds the budget, you have a quantitative basis for trimming the schedule or shortening durations.
When presenting a meeting proposal to leadership, include the payroll cost alongside the agenda. This adds a layer of transparency that helps stakeholders understand the resource commitment involved. It also shifts the conversation from “Is this meeting useful?” to “Is the value we expect worth the payroll expense we will incur?”
MeetCost relies on a few simplifying assumptions to keep the tool fast and easy to use. Understanding these helps you interpret the output correctly.
The calculator assumes a uniform work year of 2,080 hours for all attendees. It does not account for part‑time schedules, shift work, or seasonal variations in hours. If your workforce includes many contractors with irregular hours, you may need to adjust the salary figure manually before entering it.
The tool treats each hour of a meeting as equally costly. In reality, the first ten minutes might involve setup, while the final five minutes could be a wrap‑up with lower cognitive load. MeetCost does not differentiate between these phases; it applies the same hourly rate across the entire duration.
If you enable the benefits toggle, the tool adds a flat percentage to each attendee’s hourly rate. This percentage is a rough estimate and may not reflect your actual benefits burden, which can vary by role, location, or employment contract. For a precise benefits cost, you would need to pull data from your payroll system.
Finally, MeetCost does not incorporate any external guidance beyond the basic payroll formula. While sources such as the OWASP LLM Top 10 https://owasp.org/www-project-top-10-for-large-language-model-applications discuss risks associated with AI‑generated content, they do not prescribe a specific method for pricing meetings. The tool stays focused on the transparent arithmetic described earlier.
Enter attendee salaries and duration and it computes the true cost with a per-attendee and hourly breakdown, so the number reflects real payroll, not a vague guess.