Autosana — self-healing software, finally.
Two friends. One massive problem. Every mobile app team in the world burning hours on QA scripts that break before the coffee gets cold. Yuvan Sundrani and Jason Steinberg decided enough was enough.
Yuvan Sundrani and Jason Steinberg have been building things together since middle school. Not metaphorically. Actual products. When they hit the startup world, they kept running into the same wall: mobile QA is a disaster.
Both worked as founding engineers at Shift Health and later at Storyit — enough reps on real mobile teams to understand exactly where development pipelines go to die. The culprit? Quality assurance. Specifically, the gap between how fast you can now build (thanks to AI coding tools) and how slow testing still is.
Cursor and Claude Code can 10x a developer's output. But when 70% of your time becomes QA? The math stops working. Someone needed to close that loop. Yuvan and Jason decided that someone would be them.
Yuvan is the kind of person who builds CO₂-powered web-shooters for fun. As a kid. His engineering instinct is visceral — products don't get designed, they get built, tested, broken, and rebuilt. He went from founding teams to CPO at a martech startup with seven-figure ARR, then back to Engineer #1 at an AI-therapy startup — all before founding Autosana.
Jason played club hockey at the University of Maryland and has been on the founding team of multiple mobile-first startups. He's worn every hat — engineering, ops, growth — which is exactly the skill set you need when you're building an agentic QA platform and telling the world that brittle test scripts are dead. Post-graduation, he biked across America. Two months. Because commitment is kind of his thing.
Autosana isn't a point solution. It's a platform vision — start with the hardest problem (mobile) and build outward. iOS and Android first, then web, then desktop, then richer validation layers. Every sprint, the moat gets deeper.
The infrastructure required to test real mobile apps — cloud device farms, visual understanding, non-deterministic flow handling — is genuinely hard. That's the moat competitors underestimate.
When Paul Graham writes a check and YC leads the batch, the valley listens. Autosana's investor list reads like a who's-who of everyone who understands why mobile QA is the most underbuilt layer of the entire software stack.
No dedicated QA team. Shipping daily. Autosana acts as your on-call QA engineer — without the salary, the Jira tickets, or the three-day turnaround.
Apps serving millions of users. Release every two weeks. Even $100B+ companies have abandoned brittle test scripts — Autosana gives them a better path forward.
Product managers and QA analysts who live in spreadsheets, not codebases. Autosana lets them run complex regression flows using nothing but plain English.
Using Cursor, Claude Code, or Copilot? Building 10x faster? Then you have a QA bottleneck. Autosana closes the loop so your velocity doesn't stop at the finish line.
Mobile apps with 100k+ users, complex regression flows, and teams spending real money on manual QA or brittle script maintenance. They're saving teams tens of thousands of dollars — they want to do it at scale.
Teams using AI dev tools and shipping every week. If you're using Cursor or Claude Code and your QA hasn't kept up — Autosana is exactly what fills that gap.
CI/CD platforms, dev toolchains, and mobile infrastructure providers. Autosana is framework-agnostic by design — integration partnerships strengthen the moat.
Headcount is growing. They're looking for engineers and operators who understand mobile infrastructure deeply — people who've felt the pain firsthand and want to fix it permanently.