What an App User Costs on Softr, and Where the Steps Are

Softr sells something only one of its competitors also offers: a bill you can calculate before you start. Because it meters people rather than activity, you can count your intended users, apply published rates, and know the number. On a shortlist of no-code app builders where two of four vendors bill by consumption, that certainty is the product.

The catch is not hidden and it is not unfair. It is simply that per-user pricing does not rise smoothly. It rises in steps, and the steps are large.

Three kinds of user

Softr divides logins into three categories, and each carries a different price.

A builder can edit the application itself. This is you, your colleague who builds screens, your agency. Builders are the most expensive category and you need very few of them.

A team user is internal — staff with a login who use the app rather than build it. Operations people, account managers, the person who processes the requests.

A client user is external — a customer, supplier, member or contractor. These are the cheapest per head and normally the most numerous, which is the correct shape for a portal.

Getting somebody into the wrong category is the most common way to overspend on Softr, and it happens most often with contractors and part-time staff, who feel internal and can frequently be modelled as client users without losing anything they need.

The published plans

From Softr's own documentation: Free gives up to three builders and five users with no team-versus-client split. Basic costs $19 monthly on annual billing or $25 month-to-month, and carries a single builder alongside five team and five client seats. Pro is $99 annually or $119 monthly, with two builders, ten team users expandable to fifty and fifty client users expandable to 250. Business is $329 annually or $395 monthly, with three builders, thirty team users expandable to a hundred and a hundred client users expandable to 500. Enterprise is quoted on request.

One provenance note, because it matters for a page like this: Softr's public pricing page renders its table in JavaScript and would not yield it to our fetch, so the figures above come from Softr's help documentation. Third-party price trackers for this product disagree with each other and with both, which is a good reason to check the vendor's own page before you sign.

What an extra head actually costs

Within a plan, Softr publishes the rates for additional users.

On Pro: $3 per extra team user up to fifty, and $1 per extra client user up to 250.

On Business: $5 per extra team user up to a hundred, and $2 per extra client user up to 500.

Softr also documents that extra users are billed monthly even if your base plan is annual. That is a small sentence with a real effect on a spreadsheet: your base is a predictable annual commitment and your growth is a monthly variable sitting beside it.

At a dollar a head, the marginal client user on Pro is close to free in any business where a portal user is also a paying customer. This is the part of Softr's pricing that is genuinely generous, and it is worth noticing before fixating on the headline plan price.

Where the steps are, and why they hurt

Here is the arithmetic that decides Softr's real cost, and it has almost nothing to do with the per-head rates.

Basic includes five client users. Your sixth client does not cost one dollar. It costs the move from Basic to Pro — from $19 a month to $99 a month, annually billed. That is a step of roughly five times, triggered by a single additional person, and a client portal reaches it the day it signs a sixth client.

The Pro-to-Business step is the same shape. Pro's client users expand to 250 at a dollar each; the 251st requires Business at $329. If you are at 250 client users and paying $99 plus $200 in extras, you are already near the Business base price — but Business includes only 100 client users and charges $2 for each one beyond, so the 251st client takes the bill to $631. The step is steeper than it looks, and you should have modelled it rather than met it.

The general rule for per-user pricing, on Softr and anywhere else: find the boundary you are closest to and plan for the month you cross it. Growth on this model does not hurt gradually. It is free, free, free, and then it is a five-fold increase on a Tuesday.

Working out your number before you build

Five minutes with a piece of paper is enough.

1. Count builders. Almost always one or two. If it is more, ask whether everyone editing really needs to.
2. Count staff logins. Be honest about who genuinely needs to be in the tool rather than who would like to be.
3. Count external people at launch, and at your twelve-month target. Two numbers, not one.
4. Place both numbers against the plan allowances. Note which plan each lands in and how much headroom is left.
5. Add the extras. Anything above the included allowance, at the published rate, billed monthly.

The output is a real figure. Not a range, not an estimate, not a "depends on usage" — an actual monthly cost you can take to whoever approves it. Only Adalo, with its flat fee per published app, can also do that, and it is the main reason Softr survives comparison with tools that do far more.

When this model is the wrong one

Per-user pricing fails in exactly one situation, and it fails completely: an audience you cannot count.

Anything with public sign-up, anything consumer-facing, anything where success means an unbounded number of accounts — on a per-user meter, that is not a budget but an open-ended commitment. Five hundred unexpected sign-ups is a wonderful week and an unpleasant invoice.

For those apps the flat published-app fee is the right shape, which in this category means looking at Adalo instead. For a portal with named clients, Softr's meter is not merely acceptable — it is the reason to choose it. The platform assessment is in the Softr review, and the comparison of all four meters is in the four meters.