AI agent pricing per seat vs pooled credits: what a 10 person team pays

Short answer: giving ten people access to an AI agent platform costs $0 on Gumloop, $299.90 a month on Lindy Plus, and $50 plus a Salesforce edition on Agentforce, before anyone runs a single task. All three then pool the actual usage into one shared balance, which is why the seat line is the part of the quote that varies most and predicts your bill least. Every figure below was read from the vendors' own pages between August 11 and September 6, 2026, from a United States address.

Last updated September 2026. We sell a flat rate AI agent with no seats and no credit meter, so we have a stake in this. Check every number against the vendor pages we name.

The two questions a seat price cannot answer

When a team of ten evaluates an agent platform, the quote that comes back has two independent parts, and almost every comparison article only covers the first. The first part is what it costs to let someone in. The second is what it costs when that person actually does something. On a pooled credit model those are genuinely unrelated numbers, and the second one is the one that grows.

Here is what ten people costs on each platform on published rates, split into those two parts.

The spread on the seat line is the striking part. Ten people is free on one platform and $299.90 on another, and the free one is not the cheap one by accident: Gumloop deliberately gives away access and charges for consumption instead. Its Pro plan includes unlimited seats and unlimited teams, all drawing on a single organization credit pool, and we set out the whole rate card on our Gumloop pricing breakdown.

What does a Slack message cost on each platform

It depends on the vendor, and the two answers are opposites. On Lindy, mentioning the agent in a Slack channel makes you a billed seat: Lindy defines a seat as anyone who uses it, whether they sign up, join the workspace, or mention it in Slack. On Gumloop, triggering a workflow from Slack bills the trigger owner rather than the sender.

That is worth sitting with, because it is the same surface producing opposite results. On Lindy, the way to grow an invoice without deciding to is to put the agent somewhere colleagues can see it working, and each of them who says hello takes a seat. Teammates arriving through Slack get one free week first, and that week is one time per person, so the finance consequence arrives a month after the enthusiasm does. We priced the full ladder on our Lindy pricing page.

On Gumloop the cost lands on whoever built the trigger. Nobody who uses the agent creates a charge for themselves, but the colleague who wired it up carries the consumption of everyone who pulls it. Neither design is wrong. They just fail differently, and which one suits you depends on whether you would rather meter access or meter work.

Why pooled credits make the seat count the wrong thing to optimize

Every platform in the table above pools consumption. Gumloop runs one organization pool that web chat, Slack and API usage all draw on. Lindy adds each seat's allowance to a single workspace balance anyone can spend from, and its own documentation notes that the shared Slack agent consumes more of it than anyone's private messages. Microsoft sells prepaid capacity to the tenant rather than to people. Salesforce meters at the org.

The practical effect is that the tenth person costs you nothing until they do something, and then they can cost you everything. One person running deep research on a shared pool can spend a team's month, and no seat count anywhere in your contract will have predicted it. This is why we keep saying that the useful question is not how cheap the seat is but what the seat requires underneath it and what it can spend once it is in.

Two defences are worth setting up on day one rather than after the first surprising invoice. Set per user spending caps, which Gumloop exposes in permission groups and Lindy exposes as admin allocations. And decide deliberately whether overage is switched on, because the vendors differ sharply here: Gumloop leaves overage off until you enable it and then caps it, defaulting to $5,000 a period, while HubSpot's Breeze credits automatically upgrade your contract for the remainder of the term. The full set of failure modes is on our AI agent pricing page.

How much does Microsoft Copilot Studio cost for a team of 10

The $200 pack is tenant wide, so ten people do not multiply it. What multiplies is the licensing underneath: Microsoft 365 Copilot is $30 per user per month paid yearly, and the seats are the reason Copilot Studio quotes land far above the pack price. Ten licensed users is $300 a month before a single credit is spent, and we break the routes apart on our Copilot Studio pricing page.

This is the pattern that catches people comparing agent platforms against each other. The headline number is a platform fee on Microsoft and Salesforce, and a seat fee on Lindy, and neither is the whole bill. Agentforce needs a $5 per user licence and a Salesforce edition beneath it. The only figure in the table that is genuinely complete on its own is a flat one.

Is it cheaper to self host instead

Sometimes, if you have the person. n8n is free to run yourself and genuinely capable, and for a team that already has someone technical it removes the seat question entirely. The honest cost is not the licence, it is that somebody now owns a server, its updates, its backups and its 2am failures, so budget for provisioning and maintaining that infrastructure rather than pretending self hosted means free. If nobody on the team wants that job, self hosting is the most expensive option in this article and the invoice simply arrives as someone's time instead.

Which model should a 10 person team pick

Work backwards from how your usage is shaped rather than from the price list. If usage will be spiky and concentrated in two or three people, pay for access cheaply and meter the work, which is what Gumloop's unlimited seats and $37 floor are built for. If usage will be broad, shallow and predictable across the whole team, per seat pricing stops punishing you for spikes and Lindy's pooled allowance across ten Plus seats is 30,000 credits a month for $299.90.

If the work is recurring and rule shaped, though, neither model is the right answer, because both charge you again every week for a job whose shape you already know. That is the case for a flat rate: WorkAgent is $149 a month with no seats, no pool, no orchestration fee and no per person arithmetic, so ten people and one person cost the same and a heavy month and a light month cost the same. The split worth making before you buy anything is between work that follows a rule and work that needs judgement. Put the rule shaped half somewhere the meter does not run, and keep a metered builder for the genuinely open ended half if you have one.

The one number to take into the vendor call

Ask each vendor what your bill looks like in the month one person decides to run everything through the agent. On Gumloop, ask where the overage cap is set and confirm it is not at the $5,000 default. On Lindy, ask how many people will end up mentioning it in Slack and multiply. On Microsoft and Salesforce, ask what licensing is required underneath before the platform fee applies at all. None of those questions is about the seat price, and all of them will matter more to you in month nine than the seat price did in month one.