$229B in AI revenue. Stocks moved only when a disclosed revenue line appeared. Even Wall Street pays on receipts now.

AI made writing checks cheap. it did not make senior engineering time cheap. the real cost shows up when experienced engineers lose mornings inside triage loops that should already have a clear path to resolution

the hidden org problem in AI-generated browser testing: nobody explicitly owns the ambiguity loop the failure happens everyone sees red and the team loses time deciding whether it’s app, test, infra, or config the slowdown isn’t the issue itself it’s unclear ownership of the path to resolution

AI didn’t make browser failures more expensive. It made ambiguity more expensive. The real tax isn’t a broken test. It’s the time engineering teams lose figuring out whether the failure is a real regression or just suite drift after the UI changed.

The teams actually getting leverage from AI coding aren’t the ones generating the most tests. They’re the ones shortening the time between code being written and confidence being restored. The moment verification becomes a separate maintenance workflow, the old QA bottleneck just reappears inside engineering. The real unlock is keeping browser validation inside the coding loop itself

AI agents can generate 100 browser tests in minutes the real tax starts 2 weeks later selectors drift UI shifts flows get reworked now an engineering manager owns a flaky suite nobody asked for that maintenance burden is becoming the hidden cost of AI coding velocity

We eliminated 85% of the manual UI testing we used to do before every merge. Now we're giving the tool away for free. Today we're launching Shiplight MCP. One line install, and your coding agent can verify its own work in a real browser before you ever look at it. Write the code. Navigate the UI. Take screenshots. Catch regressions. All in one agent loop. Works with Claude Code, Cursor, and Codex. Completely free and token-efficient. The bottleneck in agentic development isn't writing code anymore. It's verifying it. We're closing that gap. Quick Start 👉 docs.shiplight.ai/getting-st… Demo 👉 youtube.com/watch?v=YRw2ud9t…

Last week, we came out of stealth. The amount of support and messages I got surprised me. In a good way. Thanks to everyone who reached out. It also made me notice something else. A year ago, after 12 years building at Facebook, Snap, and Airbnb, I decided to become a founder. I wanted to write down why I made that choice, in case it’s useful to someone who’s sitting with a similar decision. My reason wasn’t glamour, status, or a vision of a big exit. It was regret avoidance. I kept coming back to a simple question: would I regret not trying more than trying and having it not work? For me, the answer was clearly yes. I realized I wanted this part of my life to be about building. Not just a product or a company, but a way of working and learning that felt honest. I was more afraid of never starting than of failing. And I was okay with the idea that even if this never turned into something massive, it would still be worth doing. If I’m being honest, I’m comfortable committing the next ten years of my life to this. Learning, making mistakes, and becoming someone I wouldn’t become any other way. Before starting, I tried to prepare. I watched every YC video. Read VC blogs. Listened to startup podcasts. As an engineer, I tried to engineer the process. I thought that if I understood enough, I’d be ready. That turned out to be the wrong model. Everyone has a plan until they get punched in the face. Most people think the hard part of being a founder is the workload. The long hours and the constant context switching. But that isn't the hard part. That’s just effort, and effort is predictable. The hard part is the emotional side, and you don’t really understand it until you’re in it. It’s the identity shift and the pressure that comes from owning decisions that actually matter. Decisions with no clear right answer. Decisions you can’t delegate. Decisions where real people and real outcomes are on the line. You don’t train for that in advance. You learn it by carrying it. And you also don’t know where this leads. That used to bother me more than I wanted to admit. Now I see it as the whole point. I don’t know how this story ends, and that’s fine. For now, I’m focused on building and seeing where the journey takes me.

🚀 Today we’re coming out of stealth and unveiling @ShiplightAI, the most reliable AI-native testing platform that scales E2E test coverage with near-zero maintenance. For years, software teams have accepted a painful tradeoff: Move fast and risk breaking production, or slow down under the weight of brittle tests and endless QA maintenance. AI-assisted coding makes this gap even wider. Modern teams ship faster than ever. Products change daily. Yet testing is still stuck in a world of scripts, manual upkeep, and fragile workflows that collapse the moment your UI changes, making testing the new bottleneck. Feng and I built @ShiplightAI to make testing a force multiplier for modern software teams. As AI accelerates coding, autonomous, reliable testing closes the loop from code to confident releases. Our goal is simple but ambitious: Make test coverage effortless, and teams can ship with confidence anytime. This mission is personal for us. Throughout our careers, we’ve always been obsessed with building high-quality software that lasts. We’re already trusted by some of the most innovative, fast-moving teams. Seeing Shiplight earn their trust and transform their release cycles is the strongest signal that we’re building something real. We’re grateful to be backed by Pear VC (Shravan Reddy, Mar Hershenson) and Embedding VC (Roger Luo), along with incredible angels like Oliver Jung. We’re just getting started, and we can’t wait to partner with more teams who are building fast and care deeply about quality. 👉 Book a demo: shiplight.ai/demo #AI #SoftwareEngineering #QAAutomation #ShiplightAI #AgenticAI