Start with 10 meetings. Go further with Pro.
Try 10 meeting analyses free. Pro adds ongoing analytics and AI features, with pricing and scope agreed before billing.
Plans
Analyze your first 10 meetings for free. Choose Pro for ongoing analytics and additional AI features.
Free trial
$0to get started
See what your meetings are costing your team.
- 10 meetings analyzed
- Meeting time and cost
- Attendance insights, where available
Pro
With AISubscriptionfor ongoing insights
Keep improving your meetings with additional AI features.
- Ongoing meeting analytics
- AI attendance recommendations
- Ask AI about your team’s meeting patterns
AI features depend on connected data and workspace settings.
Talk to us about Pro
Pro pricing and scope are agreed in writing before anything is billed. Creating a workspace does not start a paid subscription.
Enterprise (1,000+ users): scoped annual agreements. Storage region, SSO, support and rollout requirements are confirmed during technical validation. Ask for the works council briefing pack, the document you hand your employee representatives before rollout.
Estimate what coordination costs.
Put numbers behind the time your team spends communicating. Adjust the assumptions to explore meeting and thread costs side by side. They are never added together: one is time booked on a calendar, the other is modeled from message volume.
Your company
Meetings
Priced from time on the calendar: people × meetings × length × the loaded rate. In a workspace, measured from calendars and attendance reports.
Your scenario assumption; not a measured customer result.
Shortening, splitting or sunsetting standing meetings.
$382,500 a week goes into meetings for 500 people. On these assumptions $61,200 is the modeled weekly cost reduction — $3,182,400 over 52 identical weeks.
Threads
Modeled from message volume: 3 minutes to write each message and 30 seconds for each other person to read it. Never from what anyone wrote.
Slack threads and pull-request or issue conversations.
$46,750 a week of reading and writing time across 300 threads, modeled from message volume.
- One thread: 20 messages, 6 people
- $156
- A 30-minute call with the same 6 people
- $262
At this size the call becomes the cheaper option after 34 messages. Past that point, Quorum can propose one for a thread that is still open.
The two figures sit side by side and are never added together: meeting cost is time booked on a calendar, thread cost is a model of reading and writing time.
The meeting scenario assumes a 40% overlap discount on the recurring reduction and caps the result at total spend. Those assumptions are not validated outcomes. Neither figure predicts cash savings or financial return; actual results depend on implemented changes and data coverage.
What the first month asks of you.
Quorum reads calendar data without editing events, and Slack and GitHub activity without storing what anyone wrote. Plan time for administrator consent, an explanation to employees, data verification, and someone to own the changes you choose.
Start · administrator setup
IT connects it
A tenant admin runs one provisioning script per calendar platform and pastes the credentials it prints; Slack is one app install, GitHub one connection per repository. Read-only calendar scopes. No agent, no bot in any call. The optional calendar extension shows each person only their own meetings, and writes nothing.
Next · confirm assumptions
Finance sets the cost bands
Four or five bands with a loaded hourly rate. This is the only input that turns hours into money, and it stays entirely under your control — nothing is inferred and no payroll system is touched.
Day 2–3
You read the baseline
Thirty days of calendar history are priced and deduplicated: committed spend, attended spend and the gap between them, by department and by recurring series. Thread and response-time figures start the day Slack and GitHub are connected and build as conversations happen.
Week 2–4
Teams choose what to change
Review recurring meetings, long threads and response patterns with the people responsible. Meeting organizers receive recommendations in Slack and make any calendar changes themselves. Quorum keeps the decision record so you can review what happened afterwards.
Employees never have to log in, install anything, or change how they work; anyone who wants to can open their own week. If your works council or employee representatives need to review it first, ask us for the briefing pack. Organization, team and series analytics are complemented by scoped person views for workload planning, with no employee performance scores.
Talk to us about Pro.
Tell us your team size and which AI features you need. We’ll agree subscription scope and pricing in writing.