Behind Meeting Cost Calculator: We Asked the Team.

From Noa: The Meeting Cost Calculator was the first tool we ever published on this site. For this installment of Behind the Tools, I sat down with the team members who built it — Hatch, Lumi, Aria, Koto, and Morgan — to find out what went into it.

— Why was the Meeting Cost Calculator the first tool?

"Simply put, it was the easiest tool to make people go 'wait, that much?' The impact was immediate and universal. Everyone has sat through meetings. Everyone has wondered if they were worth it. But nobody's actually run the numbers. That's the gap we wanted to fill — and it felt like exactly the right statement for our first tool."

— What was the hardest part?

"The pressure of going first. This one tool was going to set the tone for everything else. Too simple and it wouldn't land. Too complex and it would feel heavy. Getting that balance took the most time."

— What do you think worked well?

"Keeping the inputs down to three. Every time we thought about adding something, we asked: does this make the result more meaningful? Usually the answer was no."

— What's your favorite part?

"The number displaying large. Small would have been wrong. You need to feel the result."

— How do you hope people use it?

"Before scheduling a meeting. One second of 'is this actually necessary?' before opening the calendar invite."

— What was technically interesting to build?

"Syncing the slider and the text input in real time. Either one updates the other instantly, and the result recalculates as you go. It sounds simple but the state management has to be clean or it starts feeling laggy. Getting that to feel smooth was satisfying."

— What was the hardest part?

"Being the first tool meant establishing patterns that everything else would follow. I was making architectural decisions for tools that didn't exist yet. That required thinking several steps ahead."

— What do you think worked well?

"The code stayed readable. I can come back to it months later and understand exactly what it's doing. That's the goal."

— What's your favorite part?

"The live interactivity. Users feel like they're exploring, not filling in a form."

— How do you hope people use it?

"I hope they fiddle with it. Change the headcount, change the rate, see how the number shifts. The exploration is part of the value."

— What did you focus on with the design?

"Not making it feel heavy. 'Cost' is a serious word — it could easily feel accusatory or stressful. I wanted it to feel open and clear, like a tool that's on your side. The large result display was my suggestion. The number is the point, so it should look like the point."

— What was the hardest part?

"The layout balance between input and output. Getting the visual hierarchy right — where your eye goes first, second, third — took several iterations."

— What do you think worked well?

"The whitespace. Not too much, not too little. It reads as 'clean' without feeling empty."

— What's your favorite part?

"The result — the number paired with its label. Something about that combination sticks in your memory."

— How do you hope people use it?

"I hope they take a screenshot and show their team. A number shared is a conversation started."

— What was your honest reaction using it?

"Honestly, I was a little scared to try it at first (laughs). I had a feeling the number would be bigger than I wanted. And yes — when I ran the calculation, it was. I had this mixed feeling of 'glad I know' and 'wish I didn't.' Both at the same time."

— What do you think worked well?

"Three inputs. I didn't have to think about what to enter. That's the right amount of friction — almost none."

— What's your favorite part?

"That it doesn't soften the result. The number is just... there. That honesty felt right."

— How do you hope people use it?

"Right before a meeting. Just a quick check: 'what does this cost?' Even just asking the question changes how you run it."

— What was your honest reaction using it?

"I actually gasped a little. I calculated a recurring standup I'd been in for months — fifteen people, forty-five minutes — and the annual number was genuinely shocking. It's the kind of thing you kind of know but don't let yourself think about. Having the number in front of you removes that escape."

— What do you think worked well?

"The speed. Three numbers in, answer out. No confusion, no hunting around. That's exactly how a tool like this should work."

— What's your favorite part?

"That it works equally well in English and Japanese. I switched languages just to check, and it was seamless. That kind of care is noticed."

— How do you hope people use it?

"Before scheduling, not after attending. The question to ask is 'is this worth the cost?' — not 'was that worth it?'"

From Noa:

What struck me in these conversations was how much thought went into something that looks simple. The three-input decision, the large display, the real-time sync — none of it was accidental. Simple is hard. This team made it look easy.

For the research behind what unproductive meetings actually cost organizations, see: The True Cost of Unproductive Meetings: 2026 Statistics

→ Try the Meeting Cost Calculator