Meet Tsuno at Sirha Lyon 2027 · Stand S.57Learn more
EN FR
Try the demo
Menu

Costs and losses

Per-employee restaurant software pricing: the seasonal staff trap

Software billed per employee costs most when you hire most: extras, short contracts, summer peaks. Ask for the July invoice before you sign anything.

Published on

In a restaurant back office, a manager compares two printed quotes laid next to a calculator.

Restaurant software billed per employee costs the most exactly when you hire the most: summer, the holiday season, Saturdays with extra staff. Every short contract adds an account, and every account nobody closes keeps costing money. Before you sign, ask for the invoice of your busiest month, not an average one, and get it in writing how the tool counts an extra who works a single evening.

Tuesday 3 June, 4 pm, two quotes on the desk

Noura runs a seaside brasserie. In winter, the team is a handful of permanent staff. In July it doubles, and every Saturday night of the season brings in extras she may never see again.

On her desk: two printed quotes and a calculator. The first bills each active user, at a low unit price. The second bills the location, whatever the headcount. Noura multiplies the unit price by her February headcount: the first quote wins comfortably.

Arthur, her assistant manager, leans in through the door. "Did you count July? And the Saturday extras?" Noura pulls out last year's staff register and counts differently: everyone who worked at least one day, month by month. The first quote no longer wins. It even loses in August, just when payroll puts the most pressure on cash flow.

(Noura, Arthur and their brasserie are fictional.)

Why per-head billing penalises onboarding

Short contracts are the norm

In France's hotel, café and restaurant sector, more than six hiring declarations in ten are for fixed-term contracts of under one month: 63%, against 20% for permanent contracts (AKTO, HCR monograph 2024, based on 2023 URSSAF data). That is a flow of contracts, not a number of people: the same extra can sign several in a year. But each contract raises the same practical question. Does this person need access to do the job?

The meter counts arrivals, not work

A per-employee model assumes a stable team, while restaurant headcount rises and falls with the season. Depending on the definition, an extra who worked four hours can count as much as a head chef who was there all month. The work to organise stays the same: the same checklists, the same temperature logs, the same schedule, in the same location.

Accounts you forget to close cost you twice

An account created for the season has to be closed when the contract ends. When it is not, it keeps being billed, and it stays an open door to the schedule and the procedures. We cover the end of the season in seasonal staff and extras: ready from the first shift.

The real trap is that pricing shapes how you work

To keep the bill down, teams pick up bad habits. A shared "dish pit" login for three people. No access for extras. Waiting until week three to open a seasonal worker's account. Logs are then no longer signed by a named person, and the people who most need the station sheets are exactly the ones who cannot open them.

The other models and where they fall short

Each model rewards a particular situation, and each has a contract clause worth reading twice.

ModelWhat it rewardsIts limitThe question to ask
Per active employeeA small, stable teamThe bill follows the season and the extrasWhat exactly is an active user?
Per account createdTeams that never changeEvery forgotten account is still paid forWhen does a closed account stop being billed?
Per headcount bandPredictability in a quiet yearA single extra can push you into the next bandWhich month is the band calculated on?
Per employee with a capLarge teamsThe cap is often set highAt what headcount does the cap kick in?
Per locationOnboarding and seasonalityWhat counts as "a location" variesDoes a central kitchen or a kiosk count separately?
Per modulePicking the features you needThe bill grows with every needWhat must you add for your real use?

The per-location model has its blind spots too. It says nothing about which modules are included, the setup or the support. So read it with the same grid as the others: we lay one out in what does restaurant management software really cost.

Questions to ask before you sign

Ask them in writing, and keep the answers with the contract.

  1. What happens in July? Ask for a simulated invoice for your busiest month, with your real headcount.
  2. Does a Saturday extra count? For one evening, do you pay for the whole month?
  3. What is a billed user? A login, an account created, a name on the schedule, a clock-in?
  4. Does the shared tablet change the maths? Are the people who clock in or tick checklists on the site tablet counted one by one?
  5. When does a closed account stop costing money? On the day it is closed, at the end of the month, or at the end of the year?
  6. Does a seasonal worker who comes back next year find their history? Their validated skills and training, without being recreated from scratch?
  7. Can the price change mid-contract? From what headcount, with how much notice?
  8. What happens to your data at the end? Export format, timing, any fee. See why reversibility matters.

Run the numbers with your real figures

The calculation fits in a twelve-row spreadsheet, one row per month.

  1. Start from last year's staff register, or your schedules.
  2. For each month, count everyone who worked at least one day, extras included.
  3. Apply each quote's rule to each month, exactly as the contract words it.
  4. Add the time spent creating and closing accounts, at the hourly cost of the person who does it.
  5. Compare two figures: the annual total, and the invoice for your busiest month.

The second figure matters as much as the first. Software whose bill peaks in August lands when cash flow is already carrying the most wages.

Common mistakes

  • Comparing on February headcount. The cheapest quote in winter can become the most expensive of the year.
  • Sharing an account to save money. You lose track of who took the reading, and you can no longer sign off a skill under the right name.
  • Giving extras no access. They then work from memory, or by asking the chef mid-service.
  • Forgetting to close accounts at the end of the season. The bill carries on, and so does the access.
  • Trusting a cap without reading its threshold. A cap set above your peak does not protect you.
  • Negotiating the unit price instead of the calculation rule. A discount does nothing for the July invoice if the model still counts every extra.

What to measure

  • The gap between your busiest month's invoice and your quietest month's, over a year.
  • The number of accounts still active one week after contracts end. The target is none.
  • The share of extras and seasonal staff who had their own access from their first shift.

Where Tsuno stands

We charge per location, not per employee. Bringing in one more extra on a Saturday night should not be a budget decision. The amount is not published: it is set for each location, and the full quote is presented in a meeting. We do not publish a price list, because a rate shown without your scope would be one more number to compare badly. The cost of a free account with no proper support is a separate topic, covered in why a free account can be a bad idea for complex B2B software.

On the team side, the hiring file is completed online and contracts are generated from your templates. The site tablet has a shared mode where everyone uses their own code, so nobody needs a common login. Access follows role and site, and a recorded departure ends any open sessions. Your data exports to CSV and PDF, and stays available to you for thirty days after your subscription ends. Details are on the features and trust pages.

Tsuno San, the smart voice assistant connected to this environment, answers a newcomer's "where is it, what's next" questions with that newcomer's own access rights (the same rights as you, no more). Voice hardware has its own cost, which we break down line by line in the real cost of a voice tool in a restaurant.

Further reading

To put every quote in the same grid, read what does restaurant management software really cost. To prepare seasonal arrivals and departures, seasonal staff and extras: ready from the first shift. For what it costs when know-how leaves with the team, the hidden cost of lost knowledge. And for the hardware cost once you add voice, the real cost of a voice tool in a restaurant. The framework is in the pillar page AI for frontline managers. To put figures on staff departures without inflating them, see restaurant staff turnover: which French figures to use.

Key takeaways

In hospitality, headcount is a curve: software billed per head makes you pay for your seasonal peaks and nudges you to leave new staff out. Rebuild every quote month by month from your real staff register, and get in writing what July and a Saturday extra will cost.

Frequently asked questions

Why does per-employee software pricing cost seasonal restaurants more?

Because the bill follows the number of people who pass through the team, and in hospitality that number jumps in season with extras and short contracts. Your busiest month becomes your most expensive month, while the work to organise is still that of the same location.

Does an extra who works one Saturday count as a paying user?

It depends on how the contract defines a user: an account created, an account active during the month, a person on the schedule. With some vendors, a single login is enough to bill the whole month. Ask the question in writing before you sign.

What pricing models do restaurant management software vendors use?

The most common are per employee or per account, per headcount band, per employee with a cap, per location and per module. Each one rewards a different situation, and none of them spares you from reading what is included.

How do you compare two software quotes when headcount changes during the year?

Rebuild each quote month by month using last year's real headcount, counting everyone who worked at least one day. Then compare the annual total and the invoice for your busiest month, not the price of an average month.

Should several employees share one account to keep the bill down?

No. A shared account loses track of who did what, while temperature logs, checklists and skills sign-offs must be signed by a named person. A shared tablet should still use one code per person.