RunningTab puts a live cost meter in every Teams meeting — one number, ticking where the whole room can see it. Invites stop being free the moment the price is on the wall.
This is the same card RunningTab posts in your Teams meeting. The only difference: the clock is sped up, so a full hour plays out in about a minute. Set your own headcount and rate, and watch the number move.
Installs in about a minute. Free for 20 meetings a month. No card needed.
No invented statistics here — just multiplication. Plug in your own numbers and it gets worse.
One card in the meeting chat — or the side panel — ticking as people join, stay, and leave. Green to amber to red as the budget burns. Everyone sees the same number.
The bill, itemized. A receipt lands in the chat: total cost, who spent how long, and 2–4 dollar-quantified ways to spend less next time. Not lectures — line items.
The org dashboard your finance team will actually read: total spend, weekly trend, the five most expensive meetings. No names — just the money.
At a restaurant, nobody does math mid-meal — that's what the tab is for. Meetings never got one. The second yours ends, RunningTab prints the tab into the chat: who spent how long, what it cost, and exactly how to spend less next week. People screenshot these. That's the point.
Not technical? You don't need to be. One button copies a ready-to-send request for whoever approves Teams apps — exact permissions, data handling, and a 15-minute pilot plan included.
Per-seat pricing would punish you for the meter being seen — which is the whole idea. One price for your whole Microsoft 365 tenant.
The math: kill one recurring 30-minute, 6-person meeting and Team pays for itself ~8× over. The product computes its own ROI in every meeting it attends.
No — and the architecture proves it. RunningTab never stores names, salaries, titles, recordings, or message content. It multiplies a blended rate by minutes. Per-person timing dies with the meeting; the dashboard keeps totals only.
Add the bot to a meeting. It asks four questions on one card (rate, currency, budget, and what the money could buy instead). Defaults are fine — hitting Save works too.
That's who we designed for. Three resource-specific permissions scoped to meetings the bot joins, a one-page data-handling summary for admins, and a purchase path through the Microsoft marketplace if procurement prefers it.
The meter pauses politely with your usage on a card. Nothing you already saw is taken away, ever. Upgrade takes one checkout and the meter resumes instantly.
Copy this and send it to whoever approves Teams apps at your company. Fill in the brackets — that's it. Prefer a link? Send them /admin.