Viktor vs win.sh: Two Operating Models
Viktor centers an AI assistant embedded in Slack and Microsoft Teams. win.sh runs a 24/7 business loop inside an authority matrix.
Founder, Task Machine
The easiest agent to adopt is one that shows up where the team already talks. Viktor lives in Slack and Microsoft Teams, so asking it for a report feels like asking a colleague. win.sh works away from the team's chat: it watches the business's accounts and sends a summary each morning.
Viktor is an AI assistant inside Slack and Microsoft Teams. Team members ask it for work in a channel, it connects to 3,200+ tools, and it runs scheduled tasks and creates reports from there. win.sh watches the accounts you connect around the clock, proposes the next move, acts inside an authority matrix you set, and sends a brief each morning.
How do Viktor and win.sh compare?
| Dimension | Viktor | win.sh |
|---|---|---|
| Core abstraction | A chat request or scheduled task handled inside the team conversation | A 24/7 loop that monitors connected business accounts and acts |
| Human role | Ask in a channel, set schedules, and review the result in chat | Set rules per type of work, then review decisions and receipts |
| Execution | Hosted assistant connected to 3,200+ tools from Slack or Teams | Cloud sandboxes connected to accounts the customer owns |
| Strongest fit | Immediate adoption, because the work stays in the chat platform | Founders who want the business watched with little daily involvement |
| Recurring work | Scheduled tasks and reports posted back into chat | Runs continuously, with recurring workflows and a morning brief |
| Control | Requests, channel context, schedules, and review in the thread | Approval gates, authority levels, a hard budget cap, and receipts |
| Main cost | A chat thread is a weak record of process state, gates, and decisions across jobs | The loop acts before the brief, so much of the review happens afterwards |
| Commercial model | Free to start with up to $100 of credits, then Team at $100 a month | Self-serve monthly budget from $50 to $10,000, no revenue share |
Prices and features were checked against each vendor's own pages on 6 October 2026.
Who does Viktor fit?
Viktor fits a team that wants an assistant without a new tool to learn. Someone asks in a channel for last week's sales numbers or a summary of open support tickets, and the answer arrives in the same thread where the team can discuss it. Scheduled tasks bring the Monday report without anyone asking.
Chat makes adoption easy and record-keeping hard. Approvals, failed runs, and the state of a recurring job end up as messages in different channels, and finding out who signed off on what means searching threads.
Who does win.sh fit?
win.sh fits founders who want the business watched without anyone having to ask. It monitors accounts such as Stripe or Plausible around the clock, proposes or takes the next step, and reports through a Telegram brief and the Decisions tab each morning.
Its control is set per type of work, approvals, edits, and rejections become rules, and spending, outreach, publishing, and sensitive changes wait at approval gates. Spending has a hard monthly ceiling, and win.sh takes no cut of revenue. Its morning brief arrives on Telegram, and its work is mostly reviewed after the fact.
Where does each product put human control?
Viktor puts control in the conversation. People ask, read, and react in the thread, so oversight is only as good as the team's habit of reading the channel.
win.sh governs through standing policy set outside any conversation. Its authority matrix decides what each type of work may do alone, and approval gates stop risky categories before they run. A useful test is a request that needs sign-off from someone outside the channel, such as a finance approval for a supplier payment, and where each product would route it.
Where does Task Machine fit?
Task Machine keeps conversation for direction and gives decisions their own place. You decide in Chat, approve in one Inbox that holds every approval, question, and failed check with its context, and steer in Tasks, where each recurring job has an owner and a run history. Workflows run as explicit graphs with approval, question, and verifier steps, so a sign-off reaches the right person instead of the nearest channel.
Task Machine fits when the recurring work has grown past what a chat thread can track. For a team that only wants an assistant inside Slack or Teams, Viktor is the quicker start.
Which should you choose?
Choose Viktor if your team lives in Slack or Teams and wants an assistant there for requests and scheduled reports. Choose win.sh if you want the business watched without anyone asking in a channel, with a brief each morning. Choose Task Machine if recurring work needs owners, approvals routed to the right person, and a record outside chat.