Per-seat or flat: what a CRM really costs once the whole company needs a login

Per-seat pricing charges a monthly amount for every person with a login. Flat workspace pricing charges one amount for the whole team up to a user cap. For a sales team of three, the difference is small. For a company of forty that wants sales, delivery, operations and finance in one system, the difference decides who gets access at all.

This article compares the two models with worked numbers, lists the costs that never appear on a pricing page, and gives a method for pricing the company you will be in two years rather than the team you have today.

How the two pricing models work

Per-seat pricing is simple to read: price per user per month, multiplied by users. It became the default for SaaS because it scales with the customer, and for tools only one department uses, such as a design tool, it is fair. The vendor's revenue grows when you hire.

Flat workspace pricing charges for the workspace, usually in tiers defined by a user cap, the modules included and usage allowances. Adding a person under the cap is free. The vendor's revenue grows when you need more capability or outgrow a cap, not with each hire.

The two models create opposite incentives inside your company. Per-seat pricing makes every new login a budget decision. Flat pricing makes access a permissions decision, which is where it belongs.

Seat rationing: the cost that is not on the invoice

When each login costs money, companies ration them. Sales gets seats because the CRM was bought for sales. Everyone else gets workarounds:

• The project manager receives a weekly export of won deals and re-types the scope into another tool.
• The warehouse learns about orders from an email, and nobody knows if the email was read.
• Finance asks sales for the deal value and the agreed payment terms, again, every month.
• Support cannot see that the angry customer is in the middle of a large renewal.
• Two salespeople share one login to save a seat, and the activity history stops meaning anything.

Each workaround costs minutes a day and introduces errors. More importantly, it means the CRM never becomes the single place where the company knows what it promised to whom. The licence saving is visible on one line of the budget; the cost is spread across every department's week.

Worked comparison at four team sizes

The table compares an illustrative per-seat CRM at $50 per user per month with Nextora's flat plans. The $50 figure is an assumption for illustration; substitute the real quote you have in hand. Nextora prices are the published monthly list prices on the pricing page.

The comparison is not complete without modules. A per-seat CRM usually covers sales; project management, inventory, invoicing and a shared inbox are separate products, each with its own per-seat price. On a flat plan you choose the hubs you need: Starter includes two, Growth five, Scale all of them, and an extra hub costs $29 a month. Annual billing takes 25% off.

Be honest about where per-seat wins. A two-person consultancy that needs only a contact list and a pipeline, and will stay at two people, can find per-seat plans below $99 a month. Flat pricing pays off once access spreads beyond a handful of people or beyond the sales team.

The line items to check on any pricing page

List price is the smallest part of most CRM decisions. Before comparing, collect these for every vendor on the shortlist:

1. Minimum seats and billing term. Some advertised prices require annual billing or a minimum number of users.
2. Tier jumps. If one feature you need sits in a higher tier, does every seat move to the higher price?
3. Module add-ons. Marketing, service, projects, quoting and inventory are often separate products with separate seats.
4. Record and contact limits. Marketing tools in particular price by contacts as well as users.
5. AI usage. Is AI included, metered, or a per-user add-on? What happens when the allowance runs out?
6. API and integrations. Is API access included on your tier? What do the connectors to your other tools cost?
7. Storage and backups. How much file storage is included, and how long are backups kept?
8. Exit costs. Can you export everything, including files and history, without a fee?

Usage-based charges: the third model hiding inside both

Neither model is pure any more. Most CRMs now add a usage component on top of seats or tiers, and AI made it common. Typical meters are AI requests or credits, marketing contacts, emails sent, API calls, storage and automation runs. Usage pricing is fair in principle, since you pay for what you consume, but it is the hardest line to forecast.

Three questions keep usage charges predictable:

• Is the allowance pooled or per user? A pool shared by the workspace absorbs uneven use: one heavy user and ten light ones balance out. Per-user allowances strand unused capacity with the light users.
• What happens at the limit? A hard stop, an automatic overage charge and a prompt to top up are three very different experiences. Find out before the end of a busy month.
• Can you see consumption as it happens? A balance you can check beside the feature, with a projection of when it runs out, prevents surprises. A figure on next month's invoice does not.

When comparing vendors, estimate usage at your 12-month headcount and add it to the subscription line. For AI in particular, ask which features consume credits and which are free. Summaries and searches are cheap; generating whole automations or long documents costs more.

How to price the company you will be in two years

Software decisions outlive the team that made them. A CRM chosen for five salespeople is usually still there when the company has thirty people and three departments, because migrating is painful. Price for that company:

1. Write the headcount plan for the next 24 months by department.
2. Mark which departments need access to customer, deal, project or order data.
3. List the modules each department needs: CRM, projects, inventory and invoicing, conversations, analytics.
4. Price each option at month 1, month 12 and month 24, including the separate tools it does not replace.
5. Add the integration cost of connecting those tools, in money or in someone's time.

The answer often changes between month 1 and month 24. A per-seat CRM that is cheapest today can be the most expensive option by the time operations and finance need logins, especially once separate tools for projects and inventory are added on top.

How Nextora prices a workspace

Nextora charges per workspace, not per person. There are three plans, all with the same price in US dollars and euros:

• Starter: $99 a month, up to 50 users, 2 hubs, 40,000 AI credits a month, backups kept 7 days.
• Growth: $249 a month, up to 250 users, 5 hubs, 120,000 AI credits a month, backups kept 30 days.
• Scale: $499 a month, up to 500 users, every hub, 300,000 AI credits a month, backups kept 90 days.

Hubs are the product areas: Sales (the CRM and the shared inbox), Projects, ERP, Marketing, AI Chatbot, Automation, Analytics and AI teammates; Marketing and AI Chatbot build on Sales. Contacts and companies, tasks, team chat, the calendar and booking, forms, e-signatures and the AI assistant come with every plan. An extra hub on any plan costs $29 a month. AI credits are a pool for the whole workspace; extra credits can be bought in any amount, with bonus credits on larger top-ups. Paid workspaces are hosted in the EU, each on its own dedicated server. Every plan starts with a 14-day free trial.

What people can see and do is controlled by roles, not by licences. A warehouse lead can see orders and stock without seeing pipeline values; a finance manager can see invoices without editing deals. Designing CRM roles and permissions explains how to set that up before the team grows.

A short decision guide

• Choose per-seat if only a small, stable sales team will ever use the system and you already have separate tools for everything else that you are happy with.
• Choose flat if more than a handful of people need access, if departments beyond sales should work on the same records, or if headcount is growing.
• Either way, price the whole stack, not one product, and price it at your 24-month headcount.

Cost is one half of the decision; the other is what the system has to hold. CRM vs ERP explains when sales software stops being enough, and single-tenant vs multi-tenant SaaS covers what a dedicated server per workspace changes.