Why did Anthropic's launch of Claude Tag first boost competitors' registrations?

On June 23, Anthropic launched its native Slack AI agent, Claude Tag, directly colliding with the startup Viktor, which focuses on "AI employees." However, internal data later disclosed by Viktor's founder revealed that this seemingly dangerous competitor release actually became one of Viktor's strongest growth moments since its launch.

The conflict has drawn attention because both are fighting 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, functioning like an "AI colleague" permanently in the company workspace. If foundational model companies like Anthropic and OpenAI start building application-layer products themselves, the question the market most wants to see is whether startups that rely on their model ecosystems are being 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 first day of the company's launch, 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 Claude Tag was released, Viktor said it launched Google Ads brand campaigns, bidding on keywords related to "Claude Tag," directing users searching for Claude Tag, multi-agent agents, AI employees, etc., to Viktor's own landing page. The founder's statement was direct: Anthropic educates the market, and Viktor captures the demand.

This is a typical launch day intercept strategy. For a small company, the difficulty is often not just building a product, but making the market aware of the category's existence. Few people had actively searched for concepts like "multi-collaboration AI employee" before. When a large frontier model company releases a similar product, search demand is collectively generated.

Viktor claimed that day did not see the customer exodus outsiders imagined. The company actively encouraged some customers to try Claude Tag first before deciding whether to switch. According to the founder, on launch day, Viktor lost 5 customers while gaining 407 new sign-ups. The company did not disclose the conversion rate of these sign-ups into paying users.

This is the most interesting contrast in the conflict: A big tech competitor is certainly a threat, but the attention it brings can also become a free demand generator for small companies.

Viktor says it's not the same product as Claude Tag

Viktor repeatedly emphasizes that the two are not entirely identical products.

Anthropic's official page shows that Claude Tag is currently available to Claude Enterprise and Team users. It allows tagging 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 bringing Claude into Slack workflows.

Viktor's comparison piece describes Claude Tag as a Slack-only beta, tied to Claude Opus 4.8, with about 14 connectors, no free tier, and mainly providing output based on recent Slack channel conversations. Since this comparison comes from a direct competitor, the functional differences are better viewed as Viktor's product positioning statement rather than a neutral evaluation.

Viktor positions itself as a more complete "AI employee": supporting both Slack and Microsoft Teams, connecting to over 3,000 tools, and allowing users to choose different models. According to Viktor's official statements and Accel's previous introduction, Viktor runs in enterprise collaboration tools, aiming not just to reply within threads, but to deliver presentations, dashboards, spreadsheets, or advertising campaigns, and execute tasks via a browser.

This narrative addresses 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 Ford and GM as examples to explain his judgment. A single standardized product may not capture the entire market; different customers need different forms. In the AI employee scenario, agents within Slack, cross-tool employees, developer-oriented components, button-based products for business teams—these may correspond to different buyers.

Viktor's core message is that Anthropic's entry is not the endgame, but rather pushes a previously vague category to the forefront of the market.

The real divergence is in enterprise context

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

The first layer is the model. Viktor argues that Anthropic's own application is naturally bound to Anthropic's models. If OpenAI, Google, or other vendors release stronger models, independent applications can switch underlying models, while the model company's own product finds it harder to break free from such binding.

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

The second layer is enterprise context. Viktor believes that the truly hard-to-migrate element in the future is not the model itself, but the operational memory an enterprise accumulates within an AI system, including customer commitments, abnormal processes, historical attempts, team preferences, tool permissions, and cross-project knowledge.

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

This narrative carries clear self-defense undertones. Foundational model companies have not only models but also brand, capital, enterprise customer relationships, and distribution channels. By placing Claude Tag within the Claude product ecosystem, Anthropic may divert self-service customer acquisition from application companies, but in enterprise sales, the larger Claude brand could also bring trust advantages.

Giants validate the track, but also squeeze enterprise orders

Viktor does not frame this as an unqualified victory.

In his response, the founder acknowledges that the self-service market can leverage advertising and traffic tactics for growth, but the enterprise market is more complex, and enterprise is where most global knowledge work happens. For enterprise customers, buying an AI employee involves not just trying a tool but also security, permissions, compliance, integration, data retention, and long-term supplier choices. In these areas, large model companies have natural advantages.

He also states frankly that Anthropic is Viktor's biggest competitor and the biggest threat to its mission. The launch-day sign-ups are not enough to change that assessment.

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 replaceable interfaces. They need faster customer acquisition, deeper integration into workflows, better multi-model integration, and to 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 Viktor traffic and category validation. But the same move also pushed the company into more direct competition. The giant helps educate the market, but at the cost of also competing for market share. For startups like Viktor, the short-term question is not whether they are killed, but whether they can turn launch-day hype into long-term retention and real enterprise orders.