How much do Slack AI employees like Viktor or Claude Tag cost for an agency?

The sticker is not the agency bill

Agencies asking what a Slack AI employee costs are usually mixing three meters. Workspace billing (Viktor) is one shared pool. Per-seat billing (Lindy, and Claude Team seats) multiplies by everyone who uses it. Usage billing (Claude Tag channel work) has no published per-task price, so the bill is the spend limit you fund. Slack Connect is a fourth line: shared client channels sit on Pro and above.

The job in a 3-to-30 person shop is a hire in the channel where client work already happens, not another chatbot tab. Slack has no native owner on a thread, so a 9pm ask can sit while three people each assume someone else replied. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. What that hire is, as a job, is on the AI employee page for a marketing agency.

People shopping this prompt often treat Viktor as $50 per seat. It is not. Viktor's own plans page bills the workspace. A 10-person shop on the $50 plan still pays $50 for the employee, plus Slack. A priced set of swaps is on Viktor alternatives for an agency. The Claude Tag job split is on Claude Tag vs an AI employee.

Published prices, October 2026

Every figure below is from the vendor's own pricing page or docs, read 13 October 2026. Quote-only stays quote-only. Concrete has no public price.

What a 10-person agency actually pays

These rows use the published unit prices above, for ten people, with Slack billed annually. If the shop already pays Pro, drop the $72.50 Slack line. Claude Tag still needs a funded usage balance on top of seats; Anthropic does not publish a per-task cost, so that line cannot be filled from the pricing page.

Viktor says 20,000 credits is roughly 40 to 200 tasks, and a quick Slack question might cost 50 to 100 credits. Lindy's everyday asks are 2 to 250 credits. Those are vendor ranges, not a forecast of one agency's month.

What each sticker buys

Pay for the job you actually have. A cheap catch-up tool is not an employee. An employee that executes across apps is not a send gate in a client channel. Each row names the job, the product that wins it, and why.

The caveats that change the bill

The failure mode agencies name first is an AI that talks to the client unsupervised. One wrong reply can cost the account. That is a larger number than any row above. Put the send gate in writing before you install anything in a Slack Connect channel. How to run an agent there is on using an AI agent in a Slack channel shared with a client.

Claude Tag's variable line is usage. Anthropic publishes no per-task cost. Team has no usage balance until it is funded, and Claude will not reply in channels until it is. Reading a channel, deciding whether to reply, and short replies from what Claude already knows bill nothing. A working session it starts from the channel is billed, including work it picks up on its own when Respond automatically is on, which is the default. Set a spend limit before launch and watch the per-channel breakdown.

Claude Tag is off in Slack Connect by default (Restrict), and it posts no notice there. An Owner can set Channel only. Then it answers with no memory, no workspace search, no org instructions, and no routines. People from the other company can talk to it. Everyone in the channel can read what it posts. Guests cannot approve a tool request. That is usually the wrong surface for a client channel, whatever the usage line says.

Lindy waits for approval on outside impact, with Always allow on each connected account. Viktor asks for confirmation before high-stakes actions such as sending email. Concrete has no auto-send mode: a person taps Send, or nothing goes out. A send-gate teammate is on an AI assistant that drafts replies and waits for approval. Taking more clients without a new salary is a different split, on how a 10-person agency handles more clients without hiring an account manager.

A practical setup for a 3-to-30 person shop

This is the boring version that holds when the owner is still the account manager for most clients. Pin it next to the bill, not after the first usage spike.

• Name the meter. Workspace, per-seat, or usage. A $50 workspace hire and a $30 seat are not comparable until you multiply the seat by everyone who @mentions it.
• Start with what you already pay. Slack Pro is the floor for Slack Connect. If Claude Team is already on the card, Tag is the cheapest add for internal channels, then the usage line is the risk. Adding a per-seat agent on top of that is a second bill.
• Fund a cap before anyone tags it. Claude Tag needs a funded usage balance and a spend limit on Team before it replies in channels. Viktor and Lindy pause when the credit pool runs out. Pause is cheaper than an unbounded invoice.
• Keep client-facing send on a tap. Lookups, summaries, and internal tags can run. Anything the client will see waits. If the vendor offers Auto, Always allow, or Respond automatically, leave that off in Slack Connect.
• Do not put Claude Tag in the client channel by default. Restrict is the default and posts no notice. Channel only turns it on with no memory and no routines, and guests can read every post. That is a different product from a hire the client cannot see drafting.
• Keep drafts off the shared thread. People in a Slack Connect channel can see bot messages. A public chase shows the client you are chasing your own team.