Some of my thoughts making a computer use product as a YC S26 startup founder
A bit of context - we’re building computer use agents for operations heavy work in enterprise at Zomma. Something I’ve been thinking about a lot lately is how to actually design this product. Let me be honest, enterprise deployment really sucks - they’re slow, everyone’s flow is different, SO MANY back and forths - but I think it’s a problem worth solving. Our customers can do a lot more when they don’t have to worry about just grunt work :)
So what actually matters for CUA in enterprise:
- Demos are great and all but those are still just the happy path - what happens when it fails
- Design human in the loop but do it without causing reviewers fatigue? (Really need to figure this one out)
- Passwords, 2fa, accounts?? Like sure there are ways we do this right now but it still feels forced - too much friction for the end user
- How should success be measured for these agents? Do we just put Zomma on a PIP if it doesn’t get a job done😭 - this matters a lot for pricing
- How should you interact with Zomma and at what frequency? - kind of ties in with the 2nd point
Well all of this to say I think CUA is the future (debate me in the comments). It’s probably infeasible to expect everyone in the near term to build out API’s and headless counterparts for their legacy and internal systems so why not just use it like it was designed to be used. Also if it was price people are worried about; it’s only getting cheaper…🤷♂️
Anyways go follow the company page - @ZommaLabs