Trigger.io, YC Founder Story

Company: Trigger.io (originally named "Trigger") Founders: Amir Nathoo, James Brady, Patrick Buckley YC Batch: Winter 2008 (W08) Industry: Developer Tools / Mobile Infrastructure Founded: 2008 | Went Inactive: ~2013 Total Funding: ~$1.8M (YC, SV Angel, Streamlined Ventures, Hinge Capital, 500 Global) Outcome: Founders joined Square (acquired); company deadpooled Headquartered: San Francisco, CA

---

⚠️ Why This Story Matters More Than Most

Trigger.io is one of the most instructive stories in this entire collection, not because it succeeded, but because it didn't.

The founders got into YC. They raised from top investors. They built real product that real developers used. They grew 10X in a single year. And then the market moved under their feet, and the company went quiet.

This is what YC acceptance looks like when the timing isn't right. Understanding why Trigger.io stalled is just as valuable as understanding why Stripe soared. Because the same pattern, smart founders, real problem, good execution, can lead to very different outcomes depending on one variable: whether the market you're betting on is about to expand or about to collapse.

---

---

The One-Line Summary

Three Cambridge and MIT-educated engineers left corporate jobs at IBM to build the simplest way for web developers to create native mobile apps, got into YC, raised money, grew fast, and then watched the entire HTML5-vs-native debate kill their market before they could outlast it.

---

Lens 1, The Before State

Who Were They Before YC?

Amir Nathoo grew up with a persistent itch he couldn't scratch: he always wanted to start his own company. After studying Computer Science at the University of Cambridge, one of the world's most competitive technical programs, he did what most ambitious graduates do when they lack a clear path to entrepreneurship: he joined a large, safe company. IBM.

For five years, Amir worked at IBM first in software development, then in consultancy. It was stable, well-paid, and intellectually decent work. But it wasn't what he actually wanted to be doing. His colleague James Brady, also at IBM, felt the same pull.

Patrick Buckley came from a different direction, Amir had known him through St John's College at Cambridge, where Patrick had spent time on an MIT exchange program. The three of them orbited the same world of technical ambition and corporate impatience.

In 2007, Amir finally made the move. He left IBM with James Brady, brought in Patrick Buckley, and the three of them set out to find something worth building.

The Personal Pain They Were Solving

The iPhone App Store launched in July 2008, just as Trigger's founders were going through YC. The timing was electric. Suddenly, millions of web developers who had spent years building websites in HTML and JavaScript were being told that the future was "native apps", which required learning Objective-C for iOS or Java for Android. Two completely new languages. Two separate codebases. Two entirely different development toolchains.

The founders looked at this problem from the inside, as developers themselves, and felt the absurdity of it clearly. Web developers were already skilled. They already knew JavaScript. The question they kept asking was: why should learning to build a mobile app feel like learning to drive a tractor after years of driving a car?

Why They Were an Unlikely Bet

Three British engineers, Cambridge graduates who had spent their careers at IBM, pitching a Silicon Valley accelerator about a mobile development tool in 2008. The iPhone App Store had just opened. Nobody knew yet how big mobile would get. Nobody knew if HTML5 could ever match native performance. The whole bet was on a technology trend that hadn't proven itself yet.

They "didn't look like" the archetypal YC founders, no prior exits, no Stanford/MIT pedigree, no existing startup experience. They were IBM consultants who had an idea and the technical skill to build it.

Key Insight for Aspiring Founders

Corporate experience is not a disqualifier, it's often what gives you the clearest view of what's broken. Amir spent five years watching enterprises struggle with software complexity before he had the confidence to simplify it. The frustration you accumulate at a big company is fuel, not a weakness.

---

Lens 2, The Idea Origin

How the Idea Actually Started

When Amir, James, and Patrick first started working together in 2007, they didn't immediately land on mobile development tools. They were exploring different product ideas and looking for investment. What they had was technical depth, a shared frustration with developer tooling complexity, and the ambition to build something that abstracted away unnecessary difficulty.

The iPhone App Store's launch in mid-2008 crystallised their direction. Suddenly there was a massive, fast-growing market, mobile apps, with an enormous distribution problem. Web developers were the largest pool of technical talent in the world, and virtually none of them could participate in the mobile app revolution without learning entirely new languages from scratch. The gap between "I can build a great web app" and "I can build a great mobile app" was enormous, artificial, and, most importantly, fixable.

The insight was elegant: web developers don't need to learn native development. They need a bridge. A JavaScript API that talks to native device features, camera, contacts, GPS, push notifications, so developers can write in the language they already know and get native results on the other side.

The First Version, "Forge"

Trigger.io's core product was called Forge, a development framework and cloud build service. A developer would write their app in HTML5 and JavaScript using Trigger's Forge API, which gave them access to native features. The cloud build service would then compile that code into actual native apps for iOS and Android, without the developer ever needing to open Xcode or set up an Android development environment.

Early on, the company also built a cross-platform browser extension framework, allowing developers to build add-ons for Chrome, Firefox, Safari, and Internet Explorer from a single codebase. This was actually their starting point before Forge became the primary focus. The browser extension product was later open-sourced as OpenForge.

The first version was scrappy but functional. Developers could write once and get a working app on multiple platforms. That was the promise, and for a certain category of apps, it genuinely delivered.

The Signal That Validated It

By 2013, Trigger.io announced 10X growth in a single year for its Forge platform. Developers were using it to build real apps, StockTwits, Fetchnotes, NeedAnAccountant.org, and some were reporting that users who downloaded their Trigger-powered apps actually complimented them on "switching to native." The abstraction was working well enough that users couldn't tell the difference.

Alex Schiff, co-founder of Fetchnotes, said directly: "Trigger is the first mobile HTML5 framework we've tried that delivers the performance we need. We had several people email us after we launched our new Trigger-powered apps complimenting us on our 'switch to native.'"

The Pattern This Follows

Trigger.io fits the "abstraction layer" idea archetype, the same category as Stripe (payments abstraction), Heroku (server abstraction), and Twilio (telecom abstraction). The pattern is: find a category where the complexity is disproportionate to the value it produces for developers, then build the layer that hides the complexity. This is a genuinely powerful YC idea type. The risk, as Trigger.io discovered, is that the underlying platform can shift in ways that invalidate the abstraction.

---

Lens 3, The Application Anatomy

How They Got Into YC

Amir Nathoo's account of getting into YC is one of the most candid and revealing in the W08 cohort. He wrote: "We sought investment for our product ideas and were surprised when this came quickly from Y Combinator, a seed investment fund that was just getting started in Silicon Valley. They were far faster and less risk-averse than the British investors we were speaking to, they flew us out and wrote us a $20K cheque after speaking with us for 20 minutes."