> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Per user or per entity: how licensing shapes your cost
- URL: https://blog.jestor.com/per-user-or-per-entity-licensing/
- Published: 2026-09-16T18:52:11.000Z
- Updated: 2026-09-16T18:52:11.000Z
- Author: Bruno Bannach

Choosing between **per user or per entity licensing** determines what happens to your software bill as the company grows. Per user pricing scales with headcount. Per entity pricing scales with legal structure, which is a completely different curve, and it is the one that surprises holdings and franchises.

## Why the model matters more than the rate

Two vendors quoting similar monthly rates can produce bills that diverge by an order of magnitude after three years, purely because of what they count.

A group that opens units without hiring proportionally will pay far more under an entity model, for work that has not increased.

Where the models diverge most:

- Holdings with several companies under one operation
- Franchise networks adding units
- Groups running headquarters plus branches
- Businesses that open a new entity per project or property
- Companies with more accounts than employees

## How each model behaves

| Situation                 | Per user    | Per entity |
| ------------------------- | ----------- | ---------- |
| Hiring five people        | Cost rises  | No change  |
| Opening ten units         | No change   | Cost rises |
| Consolidating a group     | Predictable | Multiplies |
| Seasonal team growth      | Adjustable  | No change  |
| Same team, more companies | Flat        | Grows      |

## Questions to ask before signing

1. **What exactly is the billing unit**, in writing.
2. **Is there any charge per connected account** to an external system.
3. **What happens when we add a legal entity** without adding people.
4. **Can seats be reassigned** when someone leaves.
5. **Is there a minimum** that applies regardless of usage.
6. **Model three years of your actual growth plan**, not a generic curve.

## Why this deserves attention during selection

Pricing structure is negotiated once and lived with for years. It is also the part of a contract that is easiest to check and most often skipped, because a monthly figure feels comparable when the units behind it are not.

## Why choose Jestor

**Jestor** charges per user. A group can connect two **Omie** accounts or four hundred without additional cost per legal entity, which means consolidating a holding, a franchise network or a portfolio into one environment is a structural decision rather than a budget one. There is also an unlimited user option for companies that prefer to put everyone in the account.

## Frequently Asked Questions

### Does Jestor charge per connected ERP account?

No. Pricing follows users, not the number of connected accounts or legal entities. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Which model suits a franchise network?

Per user, since franchises grow by adding units rather than proportional headcount.

### What should I confirm in writing?

The exact billing unit and whether any charge applies per connected account.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.