Delos vs win.sh: Two Operating Models
Delos centers role-based AI workers with professional identities. win.sh runs a 24/7 business loop inside an authority matrix.
Founder, Task Machine
Hiring an AI worker for a role and switching on a loop that watches the whole business are two different bets. The first gives one goal a dedicated owner with its own email and phone. The second gives the business one system that decides what needs doing next. Delos and win.sh make those two bets.
Delos, a French company, sells specialized AI workers for roles across sales, marketing, finance, content, design, engineering, legal, and operations. Each worker has a name and its own email, phone, and digital computer, plus skills and memory, works inside tools such as Slack, Teams, Salesforce, Notion, HubSpot, and Jira, and pursues a goal you set. win.sh runs a 24/7 loop over the accounts you connect and acts inside an authority matrix you set.
How do Delos and win.sh compare?
| Dimension | Delos | win.sh |
|---|---|---|
| Core abstraction | A goal owned by a role-based AI worker | A 24/7 loop that monitors connected business accounts and acts |
| Human role | Set the goal, connect tools, follow activity, and handle escalations | Set rules per type of work, then review decisions and receipts |
| Execution | Hosted workers with professional identities in Slack, Teams, and more than 3,000 tools | Cloud sandboxes connected to accounts the customer owns |
| Strongest fit | A role that benefits from its own email, phone, memory, and tool access | Founders who want the business watched with little daily involvement |
| Recurring work | The worker pursues its goal around the clock and keeps role context | Runs continuously, with recurring workflows and a morning brief |
| Control | Goals, access boundaries, activity, and escalation | Approval gates, authority levels, a hard budget cap, and receipts |
| Main cost | A process that crosses several roles or approvals is harder to follow | The loop acts before the brief, so much of the review happens afterwards |
| Commercial model | Team plan at €50 per month for 40,000 credits, with tailored Enterprise pricing | 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 Delos fit?
Delos fits a company that wants one recognizable role filled quickly, such as a sales development worker that prospects, emails, and follows up under its own name. Setup takes minutes, the worker joins the channels the team already uses, and it decides how to reach the goal with the tools it has, escalating when it needs a person.
Goal-based control suits a contained role. When a process crosses roles, for example a lead that becomes a contract and then an invoice, the handoffs and approvals between workers are harder to see. Before you choose, check how a missing input or a failed check would reach you.
Who does win.sh fit?
win.sh fits a founder who wants the whole business watched instead of one role staffed. It monitors accounts such as Stripe, Plausible, or Google Search Console around the clock, proposes or takes the next step, and reports through a Telegram brief and the Decisions tab each morning.
Its authority is set per type of work, approvals, edits, and rejections become rules, and spending, outreach, publishing, and sensitive changes wait at approval gates. A hard monthly budget caps spending, and no share of revenue is taken. It acts through your connected accounts, and much of its work is reviewed after it runs.
Where does each product put human control?
Delos puts control in the goal and the escalation. You define the outcome and the access, the worker chooses its steps, and it comes back when it needs you, so the boundary is only as clear as the goal you wrote.
win.sh puts control in standing policy for the whole business, with limits set by type of work instead of by role. Test both against a message that should not go out, such as a sales email quoting a discount nobody approved, and see where each product would have stopped it.
Where does Task Machine fit?
Task Machine puts the process at the center instead of the worker or the loop. People and agents share tasks, each recurring job runs as an explicit workflow with approval, question, and verifier steps, and handoffs between agents stay visible as steps in that workflow. You decide in Chat, approve in one Inbox, and steer in Tasks, and agents act through accounts the business owns.
Task Machine is stronger when ownership, handoffs, and review points must stay readable across several people and agents. Delos sets up a single role faster and gives it its own email and phone.
Which should you choose?
Choose Delos if one specialized role should own a goal and its own email, phone, and channel presence matters. Choose win.sh if the whole business needs watching around the clock and one role filled is not enough. Choose Task Machine if the work crosses roles and people, and every handoff and approval should be visible in one place.