Anthropic launches Claude Tag: Why did it first help competitors increase registrations?

On June 23, after Anthropic launched its native Slack AI agent Claude Tag, it directly collided with the startup Viktor, which focuses on "AI employees." However, internal data later disclosed by Viktor's founder showed that this seemingly risky competitor launch instead became one of Viktor's strongest growth moments since its inception.

The conflict drew attention because both sides are vying for the same enterprise entry point: putting AI into collaboration tools like Slack and Microsoft Teams, not just to answer questions but to read team context, receive tasks, call tools, and execute work asynchronously—like an "AI colleague" permanently residing in the company workspace. If foundational model companies like Anthropic and OpenAI start building application-layer products themselves, the key question for the market is whether startups that rely on their model ecosystems will be squeezed or validated.

After Being "Copied" by a Giant, First Buy the Giant's Search Terms

Viktor founder Fryd was not surprised by Anthropic's entry. In his response article, he wrote that from the company's first day, almost everyone asked the same question: What if Anthropic launches a competing product?

Viktor's answer was not to block it but to leverage the attention it brings for customer acquisition.

On the day of Claude Tag's launch, Viktor said it started Google Ads brand campaigns, bidding on keywords related to "Claude Tag," directing users searching for Claude Tag, multi-agent agents, AI employees, and similar terms to Viktor's own landing page. The founder's explanation was direct: Anthropic educates the market, and Viktor captures the demand.

This is a classic launch-day traffic hijacking strategy. For a small company, the challenge is often not just building a product but making the market aware that the category exists. Previously, few people proactively searched for concepts like "multi-collaboration AI employee." When a large frontier model company releases a similar product, search demand is concentratedly created.

Viktor claimed that on that day, there was no customer exodus as outsiders imagined. The company actively encouraged some customers to try Claude Tag and then decide whether to switch. According to the founder, on launch day, Viktor lost 5 customers while gaining 407 registrations. The company did not disclose the percentage of these registrations that eventually converted to paying users.

This is the most interesting contrast in the conflict: a big company launching a competing product is certainly a threat, but the attention it brings can also become a free demand-generation engine for small companies.

Viktor Says It's Not the Same Product as Claude Tag

Viktor repeatedly emphasized that the two are not exactly the same product.

Anthropic's official page shows that Claude Tag is currently available for Claude Enterprise and Team users, allowing them to tag Claude in Slack, enabling Claude to read thread context, execute long tasks or scheduled tasks, and manage permissions via Agent Identity. TechCrunch and TechRepublic also reported that the product is still in beta, focusing on integrating Claude into Slack workflows.

Viktor's comparison article describes Claude Tag as a Slack-only beta, bound to Claude Opus 4.8, with about 14 connectors, no free tier, and primarily providing output based on recent conversations in Slack channels. Since this comparison comes from a direct competitor, the functional differences are better seen as Viktor's product positioning statement rather than a neutral review.

Viktor positions itself as a more complete "AI employee": supporting Slack and Microsoft Teams, capable of connecting to over 3,000 tools, and allowing users to choose different models. Officially and as previously introduced by Accel, Viktor runs within enterprise collaboration tools, with the goal not just of replying in threads but of delivering presentations, dashboards, spreadsheets, or advertising campaigns, and executing tasks via a browser.

This narrative aims to answer a survival question: when a model company builds a similar application, can an application-layer company retain users through narrower positioning, faster iteration, and more complete workflows?

The founder uses the example of Ford and General Motors to explain his judgment. A single standardized product may not necessarily capture the entire market; different customers need different forms. In the AI employee scenario, agents in Slack, cross-tool employees, developer-oriented components, and button-style products for business teams may correspond to different buyers.

Viktor's key message is that Anthropic's entry is not the endgame but pushes a previously vague category in front of the market.

The Real Divergence Lies in Enterprise Context

Beyond product features, Viktor focuses competition on two layers: model choice and enterprise context.

The first layer is the model. Viktor's judgment is that Anthropic's own application naturally binds to Anthropic's models. Once OpenAI, Google, or other vendors release stronger models, independent applications can switch underlying models, while model companies' own products find it harder to break that binding.

This is not a new issue. AI application companies like Cursor, Perplexity, and Granola face a similar situation: they use the capabilities of large model companies while competing with those same companies at the application layer. The common defense for application companies is that they are not just a "model wrapper" but integrate multiple models, product experiences, workflows, and customer needs into an end-to-end product.

The second layer is enterprise context. Viktor believes that the truly hard-to-migrate asset in the future is not the model itself but the operational memory accumulated by the enterprise in the AI system, including customer commitments, exception workflows, past attempts, team preferences, tool permissions, and cross-project knowledge.

If this context is locked into a particular model vendor's agent layer, enterprises may not be renting intelligence but buying back their own operational memory from the supplier. Therefore, Viktor describes itself as "renting the best intelligence but owning your own context."

This narrative has obvious self-defense overtones. Model companies not only have models but also brands, capital, enterprise customer relationships, and distribution. By placing Claude Tag within the Claude product system, Anthropic may divert self-service customer acquisition from application companies, but in enterprise sales, the larger Claude brand could also bring trust advantages.

Giant Validates the Track but Squeezes Enterprise Orders

Viktor does not portray this as a pure victory.

The founder admitted in the response that the self-service market can leverage advertising and traffic tactics to ride the wave of growth, but the enterprise market is more complex, and enterprises are the primary site for global knowledge work. For enterprise customers, purchasing an AI employee is not just about trying a tool; it also involves security, permissions, compliance, integration, data retention, and long-term vendor selection. On these issues, large model companies have natural advantages.

He also stated bluntly that Anthropic is Viktor's biggest competitor and the greatest threat to its mission. The new registrations on launch day are not enough to change that judgment.

This makes the conflict a microcosm of AI application-layer startups: when foundational model companies not only sell "engines" but also start building "vehicles," downstream companies are forced to prove they are not interchangeable interfaces. They need to acquire customers faster, integrate deeper into workflows, combine multiple models more effectively, and convince customers that their context and business memory will not be locked into a single model ecosystem.

Anthropic's launch of Claude Tag did bring traffic and category validation to Viktor. But at the same time, this action pushed the company into more direct competition. The giant educates the market, but it also comes to capture it. For a startup like Viktor, the short-term issue is not whether it gets killed but whether it can turn launch-day buzz into long-term retention and real enterprise orders.