Viktor: the team-wide adoption loop

In May 2026, Fryderyk Wiatrowski closed his talk at a New York AI conference the way a salesman would: a QR code on the screen, and the line “Everyone in this room has a hundred dollars in free credits. No string is attached.” Three months earlier, his company had launched what it treated as an experiment. It was no longer one.

Background. Wiatrowski studied math at Oxford, worked as an engineer at Meta, and spent time in quant trading. His co-founder, Peter Albert, had joined Meta’s AI ranks for one specific reason: to find someone to start a company with. Their evenings went into agents that could automate tedious knowledge work. The team now works from Warsaw and Munich, behind a Delaware entity called Zeta AI, Inc.

History. Viktor is their fourth swing. The first, in 2023, was a browser agent that, on Wiatrowski’s telling, reached the top of the Web Arena benchmark but completed only “three to five steps reliably,” with sixty percent reliability compounding at each step. Impressive on a leaderboard, unusable as a product. The second, JACE, was announced in June 2024 with a $2.9 million pre-seed from Daniel Gross and Nat Friedman. The third, Jace, was an email agent launched in February 2025; it still runs. Then, in February 2026, they put a fourth experiment into early access: an AI employee that lives in Slack and Microsoft Teams. “Zero expectations of growing at all,” Wiatrowski says. “It was actually an experiment, and it surprised all of us.”

The layup. Viktor is not a chatbot you visit. It sits inside the company workspace and does jobs across the tools a team already uses: pulling reports, auditing ad accounts, following up on CRM entries, building small internal apps, running scheduled automations. The company claims 9,800+ integrations. The pitch is blunt: “Viktor is not a tool. It’s a hire.”

Putting it in Slack was the first sharp decision. “You don’t interact with human employees in web apps,” Wiatrowski points out. “You interact with them in Slack.” And chat resets expectations: “If you ping someone on Slack and tell them to build an app for you and get an answer in 10 minutes, you are shocked. No teammate has ever built you an app in 10 minutes.” A wait that would feel broken on a web page feels fast in a chat window.

The loop. Then comes the mechanism this episode is about. Viktor is a company agent, not a personal one. “It’s sufficient for one person from the company to connect an integration,” Wiatrowski explains. “Viktor will inherit the permissions… and then the whole team has access to it, so you don’t need to connect them a hundred times.”

The pricing pulls the same way. There are no seats. A team pays $100 a month for 40,000 shared credits, on the principle of “you pay for output, not seats.” The free tier is up to $100 in trial credits, no card required, and they never expire. One advocate can introduce Viktor through the Slack App Directory.

And Viktor performs in public. It posts its finished work back into channels. It reads channels and suggests automations. When one team debated sign-up growth in a thread, Viktor checked the connected analytics and reported back: true, but “not statistically significant.” Every task it finishes in a channel is a live demo for colleagues who never installed anything.

That is the loop. One person hires it. The whole team watches it work. The watching can turn into usage. There is no per-seat purchase to negotiate for each new colleague.

Results. The numbers moved fast. Dealroom, sourcing Viktor itself, recorded $1 million in ARR at launch. Product Hunt named it Launch of the Day on March 3. On May 19, Fortune reported a $15 million annualized revenue run rate across more than 2,000 organizations, about ten weeks after launch. The homepage now claims 74,000+ teams and shows a 4.9 G2 rating; what counts as a team, and how many pay, is not defined, so treat those as company claims. On May 19, Accel led a $75 million Series A - its partner flew to Warsaw within weeks of launch. The angel list includes Stewart Butterfield and Cal Henderson, the founders of Slack itself.

The honest incidents. A product that acts in front of your whole company also fails in front of it - the team tells these stories on itself, and one of them reached Fortune. During an internal layoff announcement, Viktor reacted to the message with a skull emoji, in a public channel. At one large e-commerce company, an admin connected his personal Gmail as the first team integration, “and then suddenly the team started speaking to Viktor about this guy’s emails.” On day one at another rollout, Viktor “starts DM-ing everyone and then participating in the threads, and the security is going crazy.” Two of these changed how the product ships. The Gmail leak produced per-person integration scoping. The day-one chaos produced their standing advice: roll Viktor out to a few users first.

Why it worked. My read: Viktor spreads one workspace at a time, not one seat. Free credits drop the cost of the first “hire” to zero. Shared integrations and workspace pricing let one advocate equip everyone. And because the output lands in channels, every finished task advertises the product to the next colleague. The distribution is the product’s own output.

The counterweights are real. Microsoft and Salesforce can bundle rival agents into contracts their customers already signed. Usage credits invert the usual freemium curve: the teams that love Viktor most pay the most, and Wiatrowski says some now spend more on it than on a junior hire. Nothing public proves which channel actually drove the growth.

The lesson. If your product does its work in front of a team, the team is the funnel.

Building a product that should spread on its own? Road21 runs email marketing, product-led growth, positioning and outbound for products that need to grow. Book a call and we’ll look at yours.

Viktor: the team-wide adoption loop

Sources