Per-Seat vs Flat Pricing for Time Tracking

You run 40 volunteers through a food pantry on a Saturday, and 12 of them show up once and never come back. If your time tracking tool charges $4 per person per month, you are paying for those 12 forever, or you are spending your Sunday deactivating names to stay under a seat limit. That is the real cost of the pricing model, and it has nothing to do with whether the software tracks hours well.

The two models you will run into are per-seat and flat. The difference decides your bill more than any feature does, so it is worth understanding exactly how each one behaves as your roster changes.

What per-seat pricing actually charges you for

Under a per-seat pricing model, you pay for each active user or worker in the system, usually per month. Ten people, ten seats. Add an eleventh, your bill goes up. The number on the invoice moves with your headcount, not with how much anyone works.

This model was built for software where every user logs in and does real work inside the tool all day: a CRM, a design app, a code editor. There, a seat maps cleanly to a person getting value. One login, one paying user, fair enough.

Time tracking for a trust-based team breaks that assumption. Your workers do not live in the software. They tap a name, they clock out, they leave. A seat that costs the same as a full CRM login is charging you full price for someone who touches the tool for four seconds a shift.

Why per-seat punishes volunteer and hourly teams specifically

Three things about your roster make per-seat expensive in ways it never was for the office teams the model was designed for.

First, turnover. Event crews change every festival. Restaurant staff cycle through a season. A tutoring center adds ten students' worth of tutors in September and loses half by summer. Every one of those people needs a seat for the weeks they work, and every seat is a recurring charge you have to remember to cancel.

Second, size. Volunteer rosters run large and shallow. You might have 150 names on the books and 30 active on any given week. Per-seat pricing does not care that only 30 clocked in. If all 150 have accounts, you pay for 150, or you spend administrative time pruning the list to keep the bill honest.

Third, the trust model itself. Kangaroo Clock is built for teams where workers clock in without accounts or logins. There is no seat to assign because there is no user record in the ordinary sense. A worker taps their name on a shared tablet, scans a posted QR code, or opens a personal link. Charging per seat would mean inventing accounts just to bill for them, which defeats the whole point of no-login tracking.

Where flat pricing wins, and where per-seat is fine

Flat pricing charges one price regardless of headcount. Ten workers or 500, the number does not move. For a team whose roster swings with the season, this removes the entire question of who to deactivate and when. You add names as fast as people show up and never think about the bill again.

Kangaroo Clock uses flat pricing with no per-seat fees, and it is free for everyone at launch, so a new volunteer coordinator can add a whole spring roster on Monday without a budget conversation. You can start a free workspace and put 60 names in it the same afternoon.

Per-seat is not always the wrong choice, and pretending otherwise would be dishonest. If your team is small, stable, and every person genuinely works inside the software all day, per-seat can cost less than a flat plan. A five-person agency where nobody comes or goes might pay less on a $4-per-seat tool than on a $40 flat plan. The math only turns against you when headcount is large, volatile, or made up of people who barely use the tool.

Here is the quick way to tell which side you are on:

The hidden costs that do not show on the invoice

Per-seat pricing creates work beyond the money. Somebody has to own the seat count. That person deactivates the volunteers who stopped coming, argues with a vendor about whether an inactive seat still counts, and does a headcount audit before renewal. On a shifting roster that is a standing chore, and it produces a subtle pressure to under-count your own team so the bill stays down.

Flat pricing removes that chore. It also removes a bad incentive: you never have to decide whether one more volunteer is worth adding to the system. Add everyone. The report is more accurate because you are not hiding people from your own tool to save money. When you pull a CSV export for payroll or grant reporting, the distinct-worker count reflects everyone who actually showed up, not everyone you were willing to pay a seat for.

There is a related honesty point worth naming. A tool that charges per seat has a financial reason to want more seats, which can push toward account-heavy, login-heavy designs. A flat tool does not care how many names you add, so it can stay simple. If you want to see how no-login clock-in feels before you decide, walk through the live kiosk demo and imagine your Saturday crew tapping through it.

Pick the model that matches your roster, not the one with the lowest sticker per user. If your headcount is stable and small, run the per-seat math and it may win. If your names come and go, or your workers never log in at all, flat pricing is the one that stays cheap as you grow. Add the whole roster and get on with your day.