Viktor vs Claude: Credits per Workspace or Usage per Channel
By Joris van Huët
Enterprise Interim CMO & Marketing Leader · 15+ years · 50+ orgs
Published
2026-10-26
The short answer: if your team works in Microsoft Teams, or wants an AI coworker in Slack without buying seats, Viktor fits: it starts with up to $100 of free credits and its Team plan is $100 a month for 40,000 credits shared by the workspace (Viktor pricing). If your company already pays for Claude Team, at $25 a standard seat billed monthly for 2 to 150 people, Claude Tag puts @Claude in your Slack channels and bills channel work by usage to the organisation, under a spend limit an Owner sets (Claude pricing, Claude Tag overview). Both checked on 26 October 2026. Choose Viktor if your job is an AI coworker across chat apps on one credit pool; choose Claude if your job is Slack work for a team already on Claude.
Disclosure: I may earn a commission through some links on this site. It does not change what this page says.
This pair is usually a question about which AI coworker sits in the team's channels. On Anthropic's side that product is Claude Tag, which replaced Claude in Slack on 3 August 2026: you tag @Claude into a thread, it works under its own identity with the tools an admin connected, the exchange stays visible to the channel, and it can follow up on its own (What is Claude Tag?). Viktor does the same job from the other direction: a coworker you message in Slack, Microsoft Teams, Discord or its web app, paid from one credit balance per workspace (plans and credits). For Claude as a personal assistant, see Gumloop vs Claude.
Work out four things before the pilot:
- The fixed cost before any usage. For example, six people on Claude Team standard seats pay 6 x $25 = $150 a month billed monthly, or 6 x $20 = $120 on annual billing, and channel work then draws on a usage balance the organisation funds (Claude pricing, Claude Tag overview). Viktor has no seat price; the workspace buys credits, $100 for 40,000 on Team (Viktor pricing).
- The chat app you already use. Claude Tag works in Slack today. Viktor works in Slack, Microsoft Teams and Discord. A company on Teams alone has one candidate.
- Who will connect the tools. On Claude Tag, an Owner sets connectors for all of Slack, a workspace or a channel; on Viktor, members connect apps unless an admin restricts it (integration permissions).
- The spend you will watch. Claude Tag shows spend per channel against its limits and alerts admins at 75% and 95% (What is Claude Tag?); Viktor messages the payer at 70% and 90% of credits and lists the cost of each conversation and scheduled task (check usage).
The record
| Viktor | Claude Tag | |
|---|---|---|
| Where it works | Slack, Microsoft Teams, Discord, web app (talk to Viktor) | Slack (overview) |
| Which plans include it | Every plan, the free one included | Team and Enterprise, in beta; not Free, Pro or Max |
| How work is paid for | Shared credits at $25 per 10,000 (plans and credits) | Channel work from the organisation's usage balance; one-to-one DMs on the sender's own seat |
| Who sets it up | Admins choose the plan; members can connect tools | A Primary Owner or Owner only; the Admin role cannot |
| Spend controls | Auto top-ups with a monthly limit; per-user caps on Enterprise (running out of credits) | Organisation limit, a default limit per channel, and per-channel limits (restrict access) |
| Before it acts with your accounts | Per-tool levels and approval cards (approvals) | Personal connectors ask first; Allow with review holds each result (personal connectors) |
How they differ
One app or several
Claude Tag lives in Slack and in Anthropic's first-party service only; it is not offered on individual plans or third-party deployments (overview). Viktor installs in Slack or Microsoft Teams and can join a Discord server; its Teams approval cards lack only the always-approve option (approvals).
Who holds the keys
Claude Tag is centralised. An Owner pairs the Slack workspace, funds the balance, sets the limit and decides which credentials each channel inherits, and a private channel can hold extra connections (What is Claude Tag?). Viktor spreads the setup out: whoever connects an app decides whether the team can use it, and admins can switch off new connections by members (integration permissions). Central suits a security team; spread suits a team starting on Monday.
How a busy month is billed
Viktor pauses at zero credits and resumes when an admin adds a plan, a top-up or an auto top-up (running out of credits). Claude Tag declines work that would go over a limit rather than cutting it short, and the blocked person can ask an admin for more from inside Slack (What is Claude Tag?).
Chasing launch sign-offs, by agent
The job: a launch waits on legal for the landing-page claims and on design for the hero image, and the marketing lead spends two mornings a week chasing. In Claude Tag, one message in the project channel sets a follow-up that runs until the approval lands: check the review every weekday, nudge the reviewer after two quiet weekdays, and post when it is approved, with "done" defined as approved rather than commented on (track projects). On Viktor, a reminder can come back to the thread only if nobody has replied, and a weekday scheduled task can post a standing digest; Viktor test-runs a new task with chat messages captured and writes blocked (reminders, scheduled tasks). On both, the decision stays human. The agent nudges and reports; legal and design approve.
Prices, checked on 26 October 2026
From Claude's pricing page, its Team and Enterprise tab, Viktor's pricing page and its plans guide, in USD per month:
| Option | Billed monthly | Billed annually | What comes with it |
|---|---|---|---|
| Claude Team, standard seat | $25 | $20 | @Claude in Slack; channel work billed as usage |
| Claude Team, premium seat | $125 | $100 | 5x the usage of a standard seat |
| Claude Enterprise | Not listed | $20 a seat, 20-seat minimum | Plus usage at API rates |
| Viktor Free | $0 | Not offered | Up to $100 of credits |
| Viktor Team | $100 | Not offered | 40,000 shared credits |
| Viktor, smallest listed plan | $50 | Not offered | 20,000 credits; some workspaces start at $100 |
Two of Claude Tag's defaults open the meter wide. Its access toggle starts off, so anyone in the paired Slack workspace can hand Claude channel work billed to the organisation, even without a Claude account, and the setup screen preselects a $2,500 monthly spend limit unless one already exists (restrict access, setup). Both settings suit a vendor paid by usage. For a pilot, pick the $500 option on the same screen and switch on Restrict to your organization if contractors share your Slack.
Choose Viktor if your job is
- An AI coworker in Microsoft Teams or Discord, or in Slack without buying seats.
- Scheduled and event-driven work across many connected tools, from one credit pool.
- Reports and small internal apps the coworker builds and hosts itself.
Choose Claude if your job is
- @Claude in Slack for a company already on Claude Team or Enterprise.
- Channel work with budgets an Owner sets per channel.
- Turning threads into docs, tickets and follow-ups, with the whole exchange visible to the channel.
The free route
Viktor's starter credits need no card (Viktor pricing), enough for the sign-off chase on one launch. Claude's Free plan has no @Claude, so its free step is manual: paste the project thread into a free chat and ask for a digest of blockers and owners (Claude pricing). If the digest is what was missing, the remaining question is who pays for it in the channel.
FAQ
Is Claude Tag the same as Claude in Slack?
It replaced it. Claude in Slack switched over to Claude Tag on 3 August 2026, and an Owner opts the organisation in to move across (What is Claude Tag?).
Does everyone in Slack need a Claude seat?
Not for channels. Channel work bills by usage to the organisation's balance; a one-to-one DM from someone with a connected Claude account runs on that person's seat instead (overview).
Does Viktor ask before it changes things?
For sensitive actions, yes: it prepares a draft and posts an approval card, and each tool can be set to run automatically, ask for confirmation or stay off (approvals).
ABOUT THE AUTHOR
I am Joris van Huët, an enterprise interim CMO. 15+ years, 50+ organizations, including ING, P&G, Nestlé, BNP Paribas, WeTransfer and Vinted. I take on innovation projects (venture building, design sprints), agentic marketing (setting up and running AI agents) and hands-on multi-channel work. See the track record.
I wrote and published this with AI assistance, and I answer for it. Claims about my own experience are limited to the track record above, and a statistic links to its source or is labelled as an example. I sell interim and fractional CMO work, which is why this site exists. How this site is written.
A senior operator doing the work: campaigns, channels, CRM and AI agents, live from day one.