← All stories
Inkling· 2009

Inkling

A Canadian Apple insider quit his dream job on a Friday, filed incorporation papers by Monday, then spent nearly a decade learning the hardest lesson in startups — that being right about the technology and wrong about the customer are not mutually exclusive.

Matt MacInnis · 16 min read

Inkling, YC Founder Story

Company: Inkling Founder: Matt MacInnis (CEO), Josh Forman (VP Product), Robert Cromwell (VP Engineering) YC Batch: 2009 Industry: EdTech → Enterprise SaaS / Deskless Workforce Founded: August 2009 | Acquired: February 2018 (Marlin Equity Partners) Total Funding Raised: $95 Million Key Clients at Exit: McDonald's, Whole Foods, Comcast, KPMG, Roche



The One-Line Summary

A Canadian Apple insider quit his dream job on a Friday, filed incorporation papers by Monday, then spent nearly a decade learning the hardest lesson in startups, that being right about the technology and wrong about the customer are not mutually exclusive.


Lens 1, The Before State

Who Was Matt MacInnis Before Inkling?

Matt MacInnis grew up in a small town in Canada with an entrepreneurial streak that got him called to the principal's office in high school, for selling hand-warmers made from apple juice cans and light bulbs. He ran a government-loan-backed business in his senior year. The hustle was always there. The platform hadn't arrived yet.

That platform came when an Apple campus rep visited his Harvard computer science class in 1998, during his freshman year. She mentioned they were recruiting. MacInnis, a self-described Apple nerd, walked up after class and introduced himself. That five-minute conversation changed the next decade of his life.

He spent eight years at Apple, eventually working in education marketing and helping expand Apple's reach into schools. He was on the inside when the iPhone launched. He was on the inside as the iPad was being developed. He watched, up close, how Apple thought about turning clunky, complicated technology into something elegant and human.

By 2009, MacInnis had a green card, eight years of Apple seniority, a senior title, and a front-row seat to what was coming next. Most people in that position would have stayed. MacInnis quit.

The Personal Pain He Was Living

The frustration wasn't about MacInnis personally, it was something he observed as an industry-wide failure. Every time he looked at how content was being delivered to learners, students, employees, professionals, he saw the same broken pattern: static text, printed on dead paper, already out of date the moment it left the printer.

He had seen what the iPhone did to the phone industry. He knew what the iPad was going to do to portable computing. And he kept asking the same question: why hasn't anyone done for the book what Apple did for the phone?

The book, as a format, had barely changed in 500 years. The textbook was the worst offender: heavy, expensive, out of date, non-interactive, and impossible to update. MacInnis didn't just see a problem. He saw a platform moment, a convergence of a new device (iPad), a broken format (print textbooks), and no one building the bridge between them.

Why He Almost Didn't Start

The Apple gravitational pull is real. MacInnis described it plainly: Apple is the kind of place where the resources just keep coming because the model keeps working. Job security, prestige, world-class colleagues, meaningful work. Leaving that for a startup is genuinely frightening, not because of financial risk, but because of identity risk. At Apple, you know who you are.

He admitted to spending the weekend after quitting staring at himself in the mirror asking: "What the hell did I just do?"

But there was also a specific, practical window: the iPad was about to be announced publicly. Once it launched, the opportunity to be first would close fast. MacInnis knew that every month he waited at Apple was a month someone else had to get ahead of him in a market he could see more clearly than almost anyone outside Cupertino.

Key Insight for Aspiring Founders

Insider knowledge is a competitive moat, but only if you act while it's still an advantage. MacInnis saw the iPad before the world did. That information had a shelf life. Most people with inside information wait until it feels "safe" to move. By then, the window is gone. The best time to act on what you know is when the knowledge is most asymmetric.


Lens 2, The Idea Origin

How the Idea Was Actually Born

The genesis is unusually clean: MacInnis was inside Apple, watching the iPad development, and realised there were no good tools to create beautiful, interactive digital content for it. Desktop publishing had Adobe. The iPad had nothing equivalent.

His goal, as he described it, was explicit: "Do for the iPad what Adobe did for desktop publishing."

That's a remarkably precise founding vision. He wasn't trying to "disrupt education" in the abstract. He had a specific product category (publishing tools), a specific platform (iPad), and a specific historical precedent (Adobe's role in print). That precision, rare in early-stage founding pitches, likely made the YC application unusually compelling.

The original name he had in mind reflects his ambition: Inkling is defined in the dictionary as "a slight indication or suggestion... a vague notion." MacInnis chose it deliberately for its modesty, a quiet hint of what was coming, not a declaration.

The First Version and Its Fatal Flaw

Inkling's first product, launched in August 2010, was genuinely impressive by any standard. They built interactive, multimedia e-book versions of textbooks for the iPad: embedded videos, interactive animations, quizzes built into the content, notes you could share with classmates. The experience was beautiful.

The hypothesis was this: digital, beautiful, interactive, updatable textbooks are the future. Static, paper-based textbooks are not sufficient.

Half of that hypothesis turned out to be true. The other half, the part about who would pay for them and how, was wrong. Publishers, who controlled the content, were still making enormous revenue from print. They had no competitive pressure to innovate. Students, who might have wanted better books, weren't willing to pay full price for a digital version when they could get a used print copy for less.

MacInnis was honest about what came next: "It took us many millions of dollars and many years to prove that."

The Signal That It Was Actually Working (Just Not Where They Expected)

The real breakthrough came not from students at all. It came from Starbucks.

Starbucks got wind of Inkling's technology and reached out to ask whether it could transfer its binder-bound employee training content onto digital tablets. It was an inbound request, unsolicited, from a company in a completely different industry. When MacInnis looked at what Starbucks was describing, he saw it everywhere: McDonald's had the same problem. Whole Foods had the same problem. Airlines, hospitals, hotel chains, pharmaceutical field reps, millions of "deskless workers" who needed reference materials, training manuals, and procedure guides on mobile devices, but were being served by PDFs uploaded to SharePoint.

The textbook market had rejected Inkling. The enterprise deskless workforce market was calling it, unprompted.

The Pattern This Follows

Inkling follows one of the most important, and most painful, startup archetypes: right technology, wrong initial customer. The infrastructure they built for interactive digital textbooks was genuinely powerful. But it took an unexpected inbound inquiry from a Fortune 500 company to reveal who would actually pay full price for it. The lesson: sometimes the market that validates you is not the market you built for.

Founder Stories · Members Only

You've read your 5 free stories this month.

The next YC application you write could be the one that gets in. Don't stop learning from the founders who already did it.

$5/month

Cancel anytime. Less than one bad coffee.

Unlock Every Founder Story →
  • 1000+ deeply-researched YC founder stories
  • Unfiltered Lens breakdowns: what worked, what failed
  • 2 new founder deep-dives every week
  • Full Q&A library + application teardowns

Not ready? Keep exploring, free

More stories every week.

Get 2 free stories in your inbox each week.