Your AI tools answer questions. Viktor does the work. It lives in Slack and Microsoft Teams, connects to 3,200+ tools across your stack, and acts on its own. It watches how your team works, spots problems before anyone notices, and proposes automations built around how your company actually works. It manages campaigns, builds apps, delivers reports, and writes code. And it runs for weeks without losing context, learning your company deeper every day. Not a chatbot. An AI employee.
This is the 4th launch from viktor.com. View more
Viktor for Microsoft Teams
Launching today
An autonomous AI employee that lives in Microsoft Teams and does real work across 3,000+ tools: reports, reconciliations, approvals, recurring ops. Not a copilot that drafts and waits. It ships. Live today, $100 in credits, no card.
Free Options
Launch Team / Built With
ChatGPT by OpenAI
Manus
Claude Code
Claude Cowork Projects
viktor.com
Hey Product Hunt, Fryd here, one of the founders.
We spent three years on a stubborn bet: build an AI that does the work, not one more assistant that drafts something and waits for you to finish it. It worked. Viktor has been doing real jobs for 30,000+ companies inside Slack, and in the last 10 weeks it crossed a $15M run rate. Today it moves to where most of the working world actually is: Microsoft Teams.
Viktor is an autonomous AI employee. You @mention it in a channel and it does the thing end to end: closes the books overnight, reconciles the payouts and flags the one that is wrong, screens applicants and books the calls, builds the board deck from six tools that do not talk to each other. It connects to 3,200+ integrations, so it works across your whole stack, not just Microsoft's.
What we care about:
- It ships finished work, not suggestions.
- It asks before anything irreversible, and pushes back when you are about to make a mistake.
- No per-seat tax. Start with $100 in credits, no card.
We will be in the comments all day. Tell us where it impresses you and where it falls short, we read every word. The question I am most curious about: what would you hand Viktor first?
Get started: viktor.com
viktor.com
Hi everyone, I do growth at Viktor.
Slightly funny thing about launching our Microsoft Teams version here: Product Hunt is the most early-adopter room on the internet, and the reason we built for Teams is to leave that room. Most of the working world is not in a Slack workspace ranking AI tools. They are in Teams doing the accounting, running ops, answering customers. Viktor is for them now too.
Here is the thing that reframed it for me. You do not prompt-engineer Viktor. You brief him.
Plain language, the way you would brief a sharp new hire. No clever syntax, no blank box daring you to be smart. You describe the outcome and he comes back with the finished thing, not a draft to clean up.
That is also why Teams matters. The people who never wanted to learn "prompting" are exactly the people who get the most out of an employee they can just talk to.
Same Viktor, same 3,000+ tools, now living where your company already works. Brief him, see what comes back.
Would love your honest reactions, especially the unflattering ones.
Pluno
Viktor is amazing. Was super fast to set up, and everyone in our team adopted it quickly after seeing it work for others on Slack.
Mostly love it for user analytics, and getting insights by connecting the data from all the tools we use.
@korbinian_abstreiter crazy to think how the landscape changed for analytics in the last months
viktor.com
I'm one of the founders of Viktor, working on the technical side.
Viktor runs real scheduled jobs reliably, shows its work, and stops to ask before anything irreversible. The Teams launch was a genuine lift on the permissions and admin side, and it came out IT-friendly by design. Happy to go as deep on the architecture as anyone wants.
@viktor.com is the best employee you can add to your team right now. We felt it directly at 500 Stories: in April–May, Viktor helped us scale revenue from one client 5x, while keeping delivery under control across 2,074h of production, 202 deliverables
The more work moved through Viktor, the more obvious it became: this is not another AI assistant, it actually helps the team ship. So happy to see Viktor coming to Microsoft Teams. Huge congrats @fwiatrowski and team.
Hi, simple question - what is a difference between copilot and viktor?
@igor_gnot1 For me, the difference is ownership. A copilot helps you draft, search, or suggest what to do next. Viktor actually takes work off your plate.
3200 integrations plus weeks of unattended runtime inside microsoft teams is enterprise level blast radius if even one of those connections gets misused. "asks before anything irreversible" is one sentence holding a lot of weight when the agent touches this much of the stack