Launched this week
ZooWork lets you build, deploy, and deliver AI agents to teams or clients — experts start in the Builder UI, developers ship with the Managed Agent API. Turn your expertise into AI solutions built for real business operations.
Free Options
Launch Team / Built With
I love the product concept.
Imagine a founder could build an agent that drafts investor updates from approved company notes, then share it with teammates for review, that will be very helpful.
@justin2025 The approved notes are what make this work, since an update is only as good as what the founder has already signed off on. You'd load those notes into the Agent's knowledge base, write the update format and tone into its job description, and set it to run on a monthly schedule. The draft then goes to your teammates through a share link or Slack, and they review it before anything reaches investors. The knowledge base is free on ZooWork for a limited time, so it's a good moment to try it with last month's notes and see whether the draft sticks to them.
Can an expert update the agents knowledge without rebuilding the entire workflow ?
@dipanshu_kushwaha5 Your Agent can learn a new trick without you rebuilding the whole workflow. Try updating one piece of knowledge in the Builder, then ask about it in a fresh chat session and see for yourself. We don't charge extra for the knowledge base, either.
@ninghu The proposal Deck agent sounds useful. Can users build their own custom agents without coding?
@ninghu @rohit62661 You can. In ZooWork's Agent Builder, you describe how the work should be done in plain language, and the Agent is built from that conversation, no code needed. Building it isn't really the key part, though. What matters is that you can share it with your team or other users, so they get to use it too, not just you. You could try it with your own proposal workflow and share it with one teammate.
@ninghu @david_srp Got it.
No code setup and easy team sharing sound really useful
@rohit62661 Thanks, Rohit! That's the part we care about most: making an Agent useful to the rest of your team too.
the delivery part is what most agent builders miss. when the same agent is shared with two clients, how do you keep their files and conversation history separate?
@jeetendra_kumar2 If you give each client its own Agent, each gets an independent sandbox. If clients share one Agent, they share its sandbox too. Chat histories are separate for different sessions. For your two-client setup, I'd create one Agent per client and try each with a sample file.
@david_srp got it, one agent per client for isolation - can they share the same workflow template without sharing files?
Great idea! Is there a way for me to track/review the agent’s performance over time?
@khalidkhairx10 Our Managed Agent API gives you the trajectory of each run, so you can review how the Agent approached the task. I'd keep a few representative tasks and rerun them after changes to compare its behavior over time. We're also rolling out an evaluation mode to make that review and iteration more automated. Try one task you know well through the API and use its trajectory to spot something you'd improve.
Conngrats on the launch! What languages are the SDKs supporting now? Are there plans to support more languages?
@emad_khair Thanks, Emad! We have TypeScript and Python SDKs today, but these days I'd let Claude Code or Codex handle the integration in whatever language you're already using. Give it our API docs and one small task from your project, and let it get that first call working.
How do you handle updates to an agent that clients are already using? Can I test a new version before making it live for them?