Crossing $50 million in annualized revenue in seven months is either proof Viktor nailed the moment… or a warning sign that businesses are buying “AI help” faster than they’re thinking through what it will actually do to their day-to-day work.
Because let’s be honest: tools that promise to “automate daily business tasks” inside Slack and Microsoft Teams are not small utilities. They sit right in the stream of how people talk, decide, and get things done. If you control that stream, you can grow very fast. You can also make a mess very fast.
What’s been shared publicly is pretty simple. Viktor launched an AI software product about seven months ago. It automates daily business tasks inside tools like Slack, and it’s expanding into Microsoft Teams. The claim is it has crossed $50 million in annualized revenue and is used by more than 63,000 teams.
That’s a real milestone. It also tells you what companies are hungry for right now: less busywork, fewer tabs, fewer pings that require a human brain. People are exhausted. Managers want faster updates. Executives want dashboards without begging five people for a status report. An AI assistant living inside chat sounds like the cleanest solution in the world.
But I don’t think the core story here is “AI is useful.” Of course it is. The story is that the buying decision for these tools is getting dangerously easy.
Picture a mid-size company where project updates are a daily ritual. Someone spends 30 minutes chasing progress, copying notes into a doc, and posting a summary in Slack. Viktor comes in and says: the bot can do that. Everyone claps. That person gets 30 minutes back. Sounds like a win.
Until you realize that the work wasn’t just typing. It was judgment. It was noticing that the project is “fine” in the update but actually melting down in the details. It was knowing which team will panic if you phrase something the wrong way. If the automation smooths everything into neat, confident summaries, the team might feel calmer while the real risk quietly grows.
Now imagine the opposite scenario. You’re a scrappy team drowning in admin. You don’t have time to write clean handoffs or dig through threads to find decisions. An assistant that can pull context, draft responses, and turn chaos into an action list could be the difference between shipping and stalling. In that world, Viktor isn’t replacing judgment. It’s rescuing it. It gives humans room to think again.
Both outcomes are possible. The difference is how companies use it—and whether they admit what’s being traded away.
The number that jumps out to me isn’t the revenue. It’s the “inside Slack and Teams” part. That’s where informal power lives. Not the org chart. The real work: quick decisions, side conversations, “can you do me a favor,” “we’ll just ship it,” “let’s not escalate.” If an AI tool becomes the default way tasks get created, assigned, and summarized, it starts shaping the culture. It can quietly reward speed over clarity, or visibility over truth, or confidence over accuracy.
And once a company depends on it, the switching cost isn’t technical. It’s social. People will forget how to do the old thing. New hires will learn the bot workflow instead of learning the business. That’s sticky growth. It’s also a kind of lock-in that should make buyers more cautious than they are.
There’s also the incentive problem no one likes to say out loud: when a tool sells “automation,” it benefits when you route more and more work through it. But not all work should be routed through it. Some conversations should stay human. Some decisions should stay slow. Some messy context should not be “cleaned up” into a tidy summary.
If you’re a manager, this can go two ways. You can use it as a support—draft the update, then you edit it and own it. Or you can use it as a shield—let the bot “handle comms,” then act surprised when people are confused or trust breaks. The second version will be tempting, especially in places where leaders already hide behind process.
And yes, I can hear the counterargument: “We already have garbage communication. Anything is better than the current chaos.” Fair. In a lot of teams, the baseline is broken. But “better than broken” is not the same as “safe” or “wise.” If you automate a broken system, you don’t fix it. You scale it.
Viktor moving from Slack into Microsoft Teams matters because it signals ambition beyond a niche crowd. If it works across the biggest chat platforms, it becomes less of a tool and more of a layer. That’s how you get $50 million annualized revenue fast. It’s also how you end up responsible for how work feels for a lot of people who didn’t choose you directly.
I’m not rooting against Viktor. I’m rooting against the lazy version of this future, where companies treat “AI in chat” like a harmless add-on. It’s not harmless. It changes habits. It changes accountability. It changes what people notice and what they ignore.
So the real question isn’t whether Viktor can grow from here—it probably can—it’s whether companies buying these tools are willing to set real boundaries on what should never be automated inside the place where trust gets built every day: What parts of work do you think should stay stubbornly human, even if automation is cheaper and faster?