AI & ML 4 min read

Viktor raises US$75 million to put an AI "coworker" inside Slack and Teams

A Warsaw-built startup called Viktor has raised US$75 million from Accel to grow an AI agent that lives inside Slack and Microsoft Teams and runs tasks across a company's connected tools. Three months after launch it is already on a US$15 million revenue run-rate.

Maya Lin
Digital Platforms Analyst
Published 2 Jun 2026, 11:16 AM (SGT)
Share:
Person messaging on a laptop chat app, illustrating an AI assistant working inside team chat tools. Person messaging on a laptop chat app, illustrating an AI assistant working inside team chat tools. Photo by Mikhail Nilov on Pexels
Advertisement

Viktor, a startup built out of Warsaw, has raised a US$75 million Series A led by Accel to grow an AI agent that works like a colleague inside Slack and Microsoft Teams. The round, reported by Fortune on 19 May, drew Bek Ventures, Kaya VC, Inovo VC and Tenacity Capital, plus a notable angel list.

What it does

Viktor sits in the chat tools people already use. Connect it to a company's services and it can answer questions and carry out tasks that span those systems, all from a Slack or Teams message. The bet is on meeting workers where they are rather than asking them to open one more app. Founders Fryderyk Wiatrowski and Peter Albert met at Meta, and the small engineering team is drawn from Meta, Google and Oxford.

US$75MSeries A, led by Accel
US$15MRevenue run-rate, 3 months in
2,000+Organisations using it

The traction

The early numbers are what pulled in the round. Three months after a February launch, Viktor reports a US$15 million annualised revenue run-rate and more than 2,000 organisations using the product, according to the funding report. These are company-reported figures. The angel list adds weight, with backing from Slack co-founders Stewart Butterfield and Cal Henderson and executives from Google DeepMind, Figma and ElevenLabs.

The read

The "AI coworker in chat" idea is crowded, and the incumbents own the chat surface — Slack belongs to Salesforce, Teams to Microsoft. Viktor's defence is speed and breadth of integration, getting useful before the platform owners ship their own version well. The revenue curve says it is working for now. Whether it survives Microsoft and Salesforce deciding to compete directly is the question every chat-layer startup eventually faces.

The numbers above are still the only numbers

The company-reported figures — a US$15 million run-rate and 2,000 organisations — were three months old at the time of writing and have not been updated. Viktor has published no updated traction figures since, and no third party has verified any of them.

That is unremarkable for a Series A company in its first year, but it is important not to assume the trajectory continued. A run-rate quoted ten weeks after launch describes a launch, not a business. The figure that would say something is retention across the organisations that installed it, and nobody has published that either.

The surface Viktor sits on kept consolidating

Viktor's defence was speed and breadth of integration against incumbents who own the chat surface. Both incumbents moved on that surface over the quarter.

Advertisement

Microsoft merged work and personal Copilot into a single app, with two identity contexts behind one icon and the data boundary maintained by an account indicator. That is Microsoft reducing the number of places a Teams user goes for assistance, which is the opposite of the fragmentation a third-party coworker relies on.

The integration layer also got cheaper for everyone. Agent Plugins 1.0.0 packaged Agent Skills and MCP servers into one portable directory that five competing vendors agreed on. Connecting an agent to a company's systems is becoming a specification rather than a product, and breadth of integration is a weaker moat when the connections are standardised.

The permissions question is the one to ask a chat coworker

The pitch is that from a single Slack message, Viktor can carry out tasks spanning a company's connected services. This describes a very wide permissions grant.

Reading what such a grant covers is harder than reading the configuration. An audit of a widely used agent toolkit found 26 of its 77 tools could spawn a process, though 22 of those only to install a missing dependency and four to run something the caller chose. The stated capability and the real exposure differed by a factor of six.

For a product that acts rather than just answers, installed with a single administrator's click, a buyer's first question should be about that gap. Nothing published since May has made it easier to check.

Correction, 18 October 2026: An earlier version reported more than 12,000 teams installed, a figure that could not be confirmed in the funding report or in Viktor's own announcement; it has been removed. A statement that Viktor had published nothing since May has been narrowed to traction figures.

Advertisement
Maya Lin
Digital Platforms Analyst

Maya Lin covers SaaS platforms, workflow automation, creator tools, and productivity software for RECATOOLS.

View author profile → · Editorial policy

About this byline Maya Lin is a RECATOOLS editorial persona used for platform and productivity coverage. Articles are produced and reviewed under RECATOOLS editorial supervision.

Corrections policy

Advertisement