WorkClaw
Collaborative, proactive AI coworkers who work in Slack
766 followers
Collaborative, proactive AI coworkers who work in Slack
766 followers
Meet the AI team for your team. WorkClaws are collaborative, proactive AI coworkers who work in Slack and Microsoft Teams just like every other colleague. They're fully customizable to get work done your way by learning skills and routines. Unlike most AI products that pair one person with one assistant, WorkClaws can collaborate 24/7 with your whole team. Each Claw has a job title, a manager in your org chart, and a cloud-hosted ClawOS computer with the ability to access more than 3,000 apps.
Interactive
Free Options
Launch Team / Built With
Curious how learning skills and routines actually works under the hood is this more like fine tuning per org or is it closer to a Claw building its own internal playbook from observing how the team works over time?
WorkClaw
@ana_popescu2 We are built on top of OpenClaw, and so we use a lot of the infrastructure built there. And each Claude does build its own internal playbook with guidance from its human manager.
Genuinely curious about the economics here are you pricing per Claw like a headcount or per seat/usage like typical SaaS? The AI coworker framing kind of implies the former which would be a bold pricing model.
WorkClaw
@carlos_leonardo1 We are pricing it purely on AI usage and cloud hosting. That is the fairest way to price a product like this so that pricing is died to usage.
access to 3,000+ apps is a big surface area and the actual hard part isn't connecting to that many apps, it's knowing which app to use for which task without a human specifying it every time. curious whether a Claw figures that routing out itself from context or whether someone has to explicitly configure which apps it's allowed to touch for which routines
WorkClaw
@ansari_adin It is not connected to 3,000 apps out of the box. You can connect different Claws to a different set of apps depending on which jobs it needs to take on. The usual sequencing is: create a Claw, connect some apps, and then give it skills and instructions on how to use those apps to accomplish its work.
WorkClaw
@ansari_adin @ammonbrown you can control which apps to connect just like you control what apps to give to a new employee. Over time, they can set themselves up too if you give them a browser or email.
What happens when two Claws on the same team disagree about how to execute a task? Is there an escalation path or does one just defer to org hierarchy the way a human would defer to their manager?
WorkClaw
@andrew_paul11 We've actually seen them negotiate between each other to some degree. If they collide in Slack, they will talk to each other and read each other's messages and realize that the other has taken the task. They do a good job of coordinating between each other because they have communication channels.
What's the onboarding experience like for a new Claw versus a new human hire? Is there an equivalent of a 30 60 90 day ramp or is it closer to instant productivity from day one?
WorkClaw
@daniel_juan2 good question! we try to make it instant productivity from day one but they get better with more training like a person!
With access to that many integrated apps how do you handle the inevitable API changes or outages on the other end? Does a Claw degrade gracefully if one of its 3,000 connected tools goes down or does it just stall?
WorkClaw
@new_user___10520260379921a76fc2d64 We use a third party that manages the connections for us via a secure OAuth bridge. Worst case scenario, point your Claw at the updated API documentation and tell it to update itself! 😁
Wingman Studio
Is this basically just OpenClaw or something else?
WorkClaw
@david_sipos While we are based on OpenClaw, it is effectively a team, admin, and security layer on top of a modified version of it. We saw some of the drawbacks of OpenClaw, such as the memory confusion, context drift, and lack of team access controls and decided to take the great features of OpenClaw (always-on, autonomous, proactive, etc) and make those available to the enterprise in a controlled environment.
Wingman Studio
@ammonbrown I see, thank you for clarifying this.
WorkClaw
@david_sipos Of course! We owe a lot to the foundation that @steipete built and are proud to be part of the OpenClaw ecosystem!