getviktor.com - Your AI Coworker that proactively executes tasks
by•
Your AI tools answer questions. Viktor does the work.
It lives in Slack, connects to 3,000+ tools across your entire 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, before anyone asks.
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. A coworker.
Replies
getviktor.com
I'm writing this from Dubai.
For the past three days, Iran has been firing rockets at the city. Flights are canceled. The airport is partially closed. I'm stuck in a hotel room watching smoke rise over Jebel Ali.
We launched Viktor anyway.
Think of your best coworker. We launched someone better. Maybe even better than you.
Viktor lives in your Slack, connects to 3,000+ tools, and does the actual work: reports, code, web apps, ad campaigns.
While I've been stuck here watching the news, Viktor posted 28 real-time missile updates to our team Slack, tracked every team member's flight status, and told us when to shelter in place. Then it ran our ads, flagged a spend anomaly, and shipped a PR to our codebase. Nobody asked it to.
Over 1,000 teams use Viktor. Backed by Daniel Gross, Nat Friedman, and the founder of ElevenLabs. Salesforce lists us in their app store.
You can't make this up.
Fryderyk, co-founder.
P.S. Viktor is coming to Microsoft Teams very soon. Very.
@fwiatrowskiHey Fryderyk. What does setting Viktor up look like for a team with no coding experience? Is it easy to get started?
getviktor.com
@kimberly_ross Zero coding needed on your end - that's the whole idea. Viktor does the coding for you. You just talk to it in Slack (Teams soon too) like you'd talk to a coworker.
Setup is literally:
Install Viktor
Connect your tools (we have +3000 integrations)
Start asking it things:
"Pull yesterday's revenue numbers."
"Monitor what competitors are posting."
"Build me a dashboard for X."
Viktor figures out the how.
Our growth team here has zero engineering background and they're some of the heaviest users. They run ad campaigns, generate reports, automate outreach workflows - all by just describing what they need in plain English.
The learning curve is basically the same as onboarding a new teammate. You explain what you need, it asks clarifying questions if something's unclear, and then it just does it. Most teams are up and running within a day.
Wispr Flow
I run growth at Wispr Flow, so I spend most of my time deep in AI tools and automation. I'd been following Fryderyk and the Zeta Labs team since Jace, their AI email assistant, and was impressed by how fast they shipped product.
When Fryderyk showed me Viktor, it clicked immediately. I'd been spending hours building automations in Claude Code - stitching together context, writing scripts, trying to make things persistent and scheduled. Viktor did all of that natively. It just lives in Slack, already has the context from your tools and conversations, and runs on its own.
But the thing that genuinely blew me away was the proactive behavior. Viktor doesn't just wait for you to ask. It observes how your team works, chimes in when it spots something relevant, and suggests automations you didn't think to set up. I've never seen an AI tool take initiative like that.
I ended up advising the team on growth strategy because I believe this is how every team will work within a few years. Not another tab. Not another tool. A coworker that lives where your team already communicates.
If you're skeptical, give it your worst task. That's what convinced me.
getviktor.com
@mswulinski The Claude Code comparison is one of the best ways I've heard it explained. People were essentially building Viktor by hand, every time. We just made it permanent. "Give it your worst task" is going on the website. Thank you for believing in this early.
Launched Viktor on my GTM stack (Lemlist + GA4 + Internal Database). Viktor managed to find a few mistakes (mine, unfortunately), helped me analyze which outbound campaigns worked best for which persona, then proposed a few fixes to better attribute traffic (I hadn't added UTMs for our outbound campaigns). When I ghosted him for a day, Viktor told me we cannot wait on this, generated its own UTMs, and asked for permission to apply all of them.
Would recommend, 10 out of 10.
getviktor.com
@lil_bsz "Viktor told me we cannot wait on this" is the line we're going to use everywhere.
That's exactly what a good coworker does. Not wait for you to come back. Not send a reminder. Just tell you the work needs to happen and ask for the green light.
Glad the UTMs are sorted. What's the next thing on your list?
Product Hunt
Wispr Flow
getviktor.com
@curiouskitty Great question - this was honestly one of the hardest things to get right. A few things that make it work:
First, Viktor accumulates context over time rather than reacting to every single event. It builds up observations across channels and only surfaces something when it crosses a significance threshold. So it's not pinging you every time a metric moves - it waits until a pattern actually forms. Like "3 customers mentioned the same issue this week" or "this campaign's CPA drifted 20% above target over the last 4 days."
Second, there's a clear hierarchy of when to speak vs stay silent. Direct questions and anomalies that need action - always. Interesting patterns - only when they're actionable. General observations - almost never. The bar is basically "would a smart coworker tap you on the shoulder for this?"
And the feedback loop is pretty natural since it lives in Slack. If a message gets ignored or someone tells it to chill, it learns. If something it flagged leads to action, it learns that too. Over time it calibrates to each team's noise tolerance.
We've been running it internally for months and the spam problem is genuinely solved. Most days it sends maybe 2-3 proactive messages across the whole team. Quality over quantity.
I use Viktor daily for managing support. When a ticket comes in, it gets forwarded in Slack automatically and tags Viktor - it pulls up the customer's account in Stripe, checks activity in PostHog, searches for related bugs in Linear, analyzes code base, and drafts a response. What used to be a 20-30 min investigation per ticket now takes under 2. Absolute game changer.
getviktor.com
getviktor.com
Viktor submitted a PR while one of our engineers was on vacation. It read the codebase, found the issue, wrote the fix, opened the PR with a proper description. The engineer approved it from his phone. That was a Wednesday
@darthwade true, the proactive part caught me off guard. I expected to always have to ask it for things. Instead it started noticing patterns on its own and flagging stuff before I even knew about it (approving a PR from your phone while on vacation is wild though)
Can't wait to try it!
getviktor.com
@pablo_simko 🙌 Excited for you to try Viktor, if you share what you’re hoping to do with it, I'm happy to point you to the best starting place. Also, we'd love any feedback once you’ve had a chance to play with it!
◯˚GitStart
Good luck to the team being stuck in Dubai! Hope you're safe 🙏
Then, congrats on the launch! I'm curious, is there any technical challenge you solved and can openly talk about? And is adding your own API key on the roadmap or against the vision?
Asking because it's not obvious to me what's best between a) closed source and better outputs but being chained to a system that burns thousands a month and b) somewhat lower quality output? (although agentic OSS is progressing insanely fast) but no added margin on token and possibility to run things on your own hardware. Or maybe I'm just not ICP 😄.
Thank you!
I'm on the support team and one morning Viktor just dropped a list in Slack - it had gone through PostHog, found 12 accounts that hadn't logged in for two weeks with open tickets, and cross-referenced Stripe to flag which ones were paying customers. Nobody asked it to do this. It just noticed they were slipping through the cracks before I did.
getviktor.com
I have been using Jace for a while, a tool from the same team and when Viktor came into the scene, I also ran it and I love it! I've run out of credits, but it's pretty credit efficient and useful.
Really really recommend this tool and its team!
getviktor.com
@josh_littler This made my day. A Jace user who came over to Viktor on their own and ran out of credits is exactly the signal we needed today. DM me your email. I'll sort the credits.
@toni_olendzki Thanks! I emailed you via your support email :)
Great work though, really! Congrats!