Microsoft Money was, by most measures, a good software product. It launched in 1991, eventually captured roughly 25 percent of the personal finance software market, and generated real revenue for a decade and a half. Users liked it. Reviewers consistently rated it ahead of competitors on interface design. It was profitable. Microsoft killed it in 2009 anyway.
The conventional explanation at the time was that Quicken had won the market and Money couldn’t close the gap. That’s partially true. But it misses the more instructive part of the story, which is that Microsoft didn’t kill Money because it was failing. It killed Money because the product had succeeded in a direction that no longer served Microsoft’s larger ambitions, and continuing to invest in it would have required doubling down on a category that was structurally incompatible with where the company was heading.
The Setup
By the mid-2000s, Microsoft was watching Google capture the advertising-driven web model and Apple redefine consumer hardware. The company’s own consumer software division was a collection of products that had been built for a shrinking segment: people who bought boxed software at retail stores, installed it on a single Windows PC, and updated it once a year by buying a new box.
Money was a perfect specimen of that model. It was a desktop application. Its revenue came from annual upgrades and occasional new-user purchases. Its data lived on your hard drive. It had no network effects, no subscription stickiness beyond habit, and no meaningful platform leverage. Every year Microsoft sold you Money was a year that didn’t build anything durable.
Meanwhile, Intuit, which owned Quicken, was beginning to figure out what the web meant for personal finance. Mint launched in 2006 and immediately demonstrated that aggregating financial accounts in a browser, for free, supported by targeted financial product offers, was a more scalable model than selling boxed software. Intuit acquired Mint in 2009 for roughly $170 million, signaling clearly where the category was going.
What Happened
Microsoft faced a choice that looked, on the surface, like a competitive question but was actually a strategic identity question. To compete in the direction the market was heading, it would have needed to build a free, ad-supported or lead-generation-based web product. That would have meant competing directly with banks and financial institutions that Microsoft was simultaneously courting for enterprise software relationships. It would have meant an advertising model in a category where Microsoft had no data advantage. And it would have meant cannibalizing Money’s existing paid revenue before the new model produced any.
The easier path was also the strategically correct one for Microsoft at that moment: exit cleanly, stop investing in a product that generated modest profits but no leverage, and redirect engineering toward things that could compound. Microsoft shut down Money in June 2009 and offered users a free migration tool to move data to Quicken.
The product had never failed. Its margins were reasonable. Its user satisfaction scores were solid. It died because the trajectory of its success led somewhere Microsoft didn’t want to go.
Why This Matters
The Money story is not unusual. It is actually a fairly common pattern in corporate software, and understanding it changes how you read product decisions that look, from the outside, like admissions of defeat.
Consider what happened with Google Reader. Launched in 2005, it became the dominant RSS reader, used by millions of engaged, technically sophisticated users. Google killed it in 2013. The stated reason was declining usage, which was real. But the underlying reason was that Reader’s success had pulled Google into maintaining a product that actively worked against its core interest. RSS is a decentralized protocol. It lets users consume content without visiting publisher sites and without Google’s intermediation. Reader’s most committed users were exactly the people least likely to click display ads. The product was succeeding at building an audience that was structurally misaligned with Google’s business.
Or consider Amazon’s Destinations project, a hotel booking service the company launched and killed within a year in 2015. Amazon could have kept investing. It had the traffic and the customer trust. But the unit economics of hotel bookings required competing with Booking.com and Expedia on customer acquisition and supply relationships. Winning would have required enormous investment in a category where Amazon had no structural advantage. The product wasn’t losing badly enough to make the kill decision obvious. Amazon made it anyway, because the ceiling of success wasn’t worth the cost of the climb.
What We Can Learn
The lesson is not that companies should be ruthless about killing products. It’s that the right framework for evaluating a product isn’t just current profitability or growth rate. The question is whether the product’s success trajectory leads somewhere valuable.
A product can be profitable and still be a trap. If winning requires you to become something you’re not, or if the fully-realized version of the product competes with a more important part of your business, or if the skills and assets required to win don’t transfer anywhere else, then the rational move is often to exit while you’re ahead. Staying in a market you can’t win on structural terms has its own economics, and they’re usually ugly.
For founders, the implication is sharper. A product that generates revenue in the wrong direction can be more dangerous than one that simply fails, because it consumes resources, creates organizational identity, and attracts customers whose needs eventually constrain your options. Your first customers, in particular, can define constraints you’ll spend years trying to escape. Microsoft Money had millions of users who expected a desktop application. Serving them well made pivoting to the web harder, not easier.
The right time to ask whether a product’s success leads somewhere useful is before the product succeeds, not after. By the time a product has users, revenue, and organizational advocates, the cost of killing it has risen dramatically and the honest strategic analysis has usually been replaced by attachment.
Microsoft Money is remembered, when it’s remembered at all, as a product that lost to Quicken. That’s a tidy narrative that teaches the wrong lesson. The real story is about a company that recognized, late but not too late, that it was winning a contest it hadn’t meant to enter. Killing Money wasn’t a concession. It was a decision. The distinction matters more than most corporate postmortems are willing to admit.
