Zaro
Build agents & apps on top of your context with one prompt.
1.2K followers
Build agents & apps on top of your context with one prompt.
1.2K followers
Zaro is where you can build working software from your scattered work. Everything you know is spread across Gmail, Slack, notes, and tabs that don't talk - Zaro pulls it into one place and lets you build apps from it in minutes: your research, your side projects, your plans, your decisions. Then they keep themselves updated, checking your connections every day so you don't have to. No code. No maintenance. No graveyard of prototypes you started and never finished.
archive.com
Looks incredible. What are the most common models you guys use?
Postage.to
@benigeri You can actually plug-in and out any model you want and not rely on our models, and the beauty of it is that the persistent memory continues without having to retrain / rebrief your new model
Zaro
Nikita - founding product engineer here 👋
JY mentioned agents running inside the apps. The part I got obsessed with is how that feels to actually use.
Most "agentic" tools are a chat box. You type, the work disappears somewhere you can't see, and you sit there hoping. We went the other way.
In Zaro the work shows up as something you can open - a workflow with real steps, or an app you can click into and edit. You change something and it re-runs. You're never stuck waiting on a black box to tell you what it did.
What still gets me, even though I helped build it, is that the gap between building software and using it basically disappears. You don't go hunting for the right tool and learn its buttons. You say what you want, the screen to do it appears, and if it's wrong you say what to fix. An internal tool used to mean a ticket and a sprint. Now it's a sentence.
The other thing: it all sits on one shared memory, so the apps don't go stale. Feed in a new kind of data and the app reshapes itself around it, without anyone redeploying. First time I watched one rebuild itself, I honestly didn't know how to feel about it.
Really proud of this one. Would love to hear how it lands for you, the bits that feel like magic and the bits that feel off. That kind of feedback is gold for us right now.
I would love a feature that suggests automations based on repeated behavior it sees across connected tools.
Postage.to
@barnaby_lloyd This is high on our wishlist too. The logic almost writes itself: if Zaro can already see the work flowing across your connected tools, it's perfectly placed to spot "you do this same thing every Monday" and offer to take it off your hands before you even ask. Proactive rather than waiting for you to describe it.
I can see small teams loving this if it really removes follow-ups, reporting, and handoff work without needing an ops specialist.
Postage.to
@subhash_kanagamani That's exactly the team we built it for. The whole premise is that you shouldn't need a dedicated ops person to get ops-level leverage, the follow-ups, the reporting, the handoffs are precisely the work that piles up on small teams because nobody officially owns it and everyone ends up doing a little of it badly.
The "if it really removes" part is the right way to hold us to it, that's the bar. Best way to find out is to point it at the most annoying recurring thing on your plate and see how far it gets. If you do give it a run, I'd genuinely love to hear where it delivers and where it falls short, that feedback from small teams is what sharpens it.
The “no graveyard of prototypes” line hit hard, who wrote the copy? 😂
Every no-code tool promises speed, but maintenance is where things usually die.
Postage.to
@ankur_jeswani Ha, I'll pass that on to the guilty party, they'll be thrilled it landed.
And you're pointing at the real thing. Speed to first build is the easy promise, everyone makes it. Maintenance is where tools actually go to die, the prototype works in the demo, then nobody wants to own it three months later when the data shifts or the workflow changes.
That's a big part of why we cared so much about apps adapting and staying stable rather than rotting the moment reality moves. Getting that part right is less flashy than the build-in-five-minutes pitch, but it's the part that decides whether something is still running next quarter.
Glad it resonated.
Postage.to
@ankur_jeswani Ha, I'll make sure the guilty party hears it landed, they'll be unbearable now.
And you're naming the real thing. Speed to first build is the easy promise, everyone makes it. Maintenance is where tools quietly go to die, the prototype shines in the demo, then nobody wants to own it three months later when the data shifts or the workflow moves. That's a big part of why we cared so much about apps staying stable and adapting rather than rotting the moment reality changes. Less flashy than build-it-in-five-minutes, but it's the part that decides whether something's still running next quarter. Glad it hit.
Congrats on the launch. Building working software from scattered context across Gmail, Slack and notes is a genuinely hard problem, most tools make you bring the context to them, Zaro flipping that is the right instinct.
One thing I'm curious about though, how does Zaro handle context that goes stale? Because the app you build on Monday based on your Slack threads is already partially outdated by Friday. If the underlying context shifts, does the app update automatically or does the user have to rebuild?
Because the value of "one prompt builds your app" breaks down fast if keeping it accurate requires the same effort as building it again from scratch.
This is a brilliant concept for unifying scattered workplace data! How does Zaro handle data privacy and security permissions when pulling from highly sensitive sources like Gmail or Slack? Congrats on launching! 🎉