The Pricing Paradox: "User Seats" vs. "Connected Calendars"
You budgeted for 50 employees. The invoice says 80 billable units. Here is the technicality that inflates enterprise scheduling contracts.
In most SaaS categories (like CRM or Slack), a "Seat" is a human being with a login. In the scheduling software industry, the definition is far more fluid—and dangerous for your budget.
The core friction point is the difference between a Login User (someone who logs in to configure settings) and a Schedulable Resource (a calendar that can accept bookings). Vendors often charge for the latter, even if no human ever logs into that account.
This analysis supplements the TCO section of our Enterprise Procurement Guide.
The Three Types of "Billable Units"
Before signing a contract, you must clarify which of these your vendor considers "billable." The answer varies wildly between Calendly, Chili Piper, and Acuity.
1. The Standard User
A human with a login email and a personal calendar.
Verdict: Always Billable.
2. The "Add-on" Calendar
A user connects their personal calendar AND a "Sales Demo" team calendar. Some vendors charge per connected calendar, not per user.
Verdict: Often a Hidden Cost.
3. The Resource (Room/Equipment)
Meeting rooms or equipment that need to be booked. They have no login, but they consume a "scheduling license" because the software manages their availability.
Verdict: The "Ghost" Cost.

The "Admin" Trap
Another common pitfall is the IT Admin License. In many platforms, if an IT manager needs to log in solely to configure SSO or audit logs—but never books a meeting—they still consume a full "Pro" license.
Negotiation Tip:
Ask for "Free Admin Seats." Many enterprise sales reps can waive the cost for IT/Ops users who have 0 connected calendars. If you don't ask, you will pay $15-$25/month for someone who just logs in once a quarter.
The Golden Rule of Forecasting
Never calculate your budget based on "Headcount." Calculate it based on "Schedulable Entities." Count every human, every meeting room, and every shared "Round Robin" inbox that needs its own availability logic.