A Strange Subject for History
Historians write about wars and revolutions. They write about the rise and fall of states, about plagues and trade routes, about the slow grinding of economies and the sudden turns of politics. They do not, as a rule, write about planning software. The phrase itself sounds faintly absurd — what could be less worthy of historical attention than a tool for building budgets?
And yet here we are.
Few software products have survived as long as TM1. It was born in the same year the personal computer was finding its feet, and it is still in use more than four decades later. That is an extraordinary span for any piece of software, and it raises a question I think is genuinely interesting: why should anyone care about the history of a planning system?
I first encountered TM1 in 2011, shortly after completing a degree in modern history. My professional life took me into consulting, but my interest in historical questions never disappeared. TM1 became an unusual bridge between those worlds: a software product old enough to have a history, yet still alive enough to be studied through the people and organizations that use it today.
This publication exists to answer that question. And this first post is my attempt to justify the asking. Think of it not as the first chapter of a history but as its preface — the part where an author explains why the book needed to be written at all. The chapters, the dates, the technical turns, the personalities: all of that comes later. For now I only want to make the case that the subject is worth the trouble.
Most Software Disappears
Begin with a puzzle, because there is one.
Software is, by its nature, temporary. This is easy to forget in the moment, when whatever tool we depend on feels permanent and indispensable, but the historical record is brutal. Applications that once defined entire industries are gone. Platforms that seemed like the foundation of everything — operating systems, file formats, whole categories of hardware — have come and gone within a single career. The spreadsheet that made the IBM PC indispensable to business, Lotus 1-2-3, was for years the most important application in the world; it is now discontinued, a museum piece. The normal fate of software is not survival. It is obsolescence, then disappearance, then a faint memory among the people who once used it.
This is the rule. Most software dies, and most of it dies quickly. A decade is a long life; two decades is rare; four is almost unheard of.
TM1 did not die.
That is the central mystery of this entire project, and it is worth sitting with before we explain anything else. Something that should have vanished — that by every actuarial expectation of its kind should have been replaced three or four times over — is still here. Before we ask what TM1 is or how it works, we should ask the prior and more puzzling question: how is it that it still exists at all?
Born at the Dawn of Personal Computing
To feel the strangeness of that survival, you have to picture the world TM1 was born into.
The year was 1983. The IBM PC was new. Lotus 1-2-3 had just arrived and was about to make the spreadsheet the reason businesses bought computers at all. Personal computing was, for the first time, putting real computational power on the desks of ordinary office workers rather than locking it away in the glass rooms of the mainframe. It was a moment of genuine democratization, and also of genuine chaos — nobody yet knew which of these tools and ideas would last and which were fads.
TM1 emerged at exactly this moment. This is the first thing to understand about it, and it matters more than it might seem. TM1 did not survive into the spreadsheet age; it was born into it, a native of the earliest days of personal computing. It is roughly as old as the very idea of a computer on every desk. Whatever it became later, it began as a creature of 1983 — and almost everything else from that world is gone.
A Survivor of Every Transition
Here is the heart of the matter, and the reason a historian should look twice.
In the four decades since 1983, business computing has been remade not once but repeatedly. Each remaking was a kind of extinction event, and each one swept away products that had seemed essential. Consider the sequence.
There was the era of personal computing itself — the isolated machine on the desk, the floppy disk, the spreadsheet. TM1 was born here. Then computing moved off the desk and onto the network, into the age of client-server systems in the 1990s, where data lived centrally and many users shared it. TM1 made that move. Then came the rise of enterprise planning, when budgeting and forecasting stopped being a back-office spreadsheet exercise and became a coordinated, organization-wide discipline. TM1 was there. Then the great consolidation of business intelligence, when analytics tools were swallowed into vast integrated suites. TM1 passed through it. Then the cloud, which dissolved the very notion of software you install and run on your own hardware. TM1 is there too, under a newer product identity. And now the age of artificial intelligence, which promises once again to transform how organizations forecast and decide. TM1 is present for this transition as well.
The point of this list is not the detail — every one of these eras gets its due elsewhere. The point is the continuity. Each of these transitions killed countless products that could not make the jump. Most software cannot cross even one of these boundaries. TM1 has crossed all of them. A thing that has survived every major transformation of its field is not an ordinary thing, and it is not an accident. It is a phenomenon that asks to be explained.
TM1 as a Historical Lens
And now the argument that I think makes this publication worth writing, rather than merely a long act of nostalgia.
TM1 is interesting because it survived. But it is valuable — to a historian — because of what its survival lets us see. A product that has been embedded in the financial machinery of organizations for forty years is, in effect, a recording instrument. To trace its history is to trace the history of everything that used it.
Watch TM1 across these decades and you are really watching the finance department change: from a room full of clerks reconciling figures by hand, to analysts with spreadsheets, to integrated planning teams, to whatever they are becoming now. You are watching planning itself change — from an annual ritual to a continuous, data-soaked process. You are watching management practice change, and the assumptions about how organizations should be steered. And you are watching, perhaps most interestingly of all, the changing relationship between people and the machines they use to think. TM1 sits at the exact point where human judgment meets computational power in the act of planning. Forty years of that meeting is forty years of history about how we make decisions.
This is the historian’s wager: that the obscure, technical, unglamorous subject turns out to be a window onto something much larger. TM1 is that kind of window.
Why OLAP Matters
If TM1 is the visible subject of this publication, OLAP is often the hidden one.
Most people outside the field have never heard the term, and even many who use the software could not define it. Yet OLAP was one of the genuinely influential ideas in the history of business computing — the idea that you could hold data along many dimensions at once and explore it freely and interactively, rather than running a report and waiting. It quietly reshaped how organizations look at their own numbers.
I will not try to explain it technically here; that would be the wrong kind of post. I only want to establish that it matters — that beneath the story of one long-lived product there is a story about an idea, and that the idea is at least as interesting as the software that carried it.
TM1 in Brief
- 1983 — Sinper founded; TM1 announced.
- 1996 — Applix acquires Sinper.
- 2007 — Cognos acquires Applix.
- 2008 — IBM acquires Cognos.
- 2016 — IBM rebrands the platform as IBM Planning Analytics.
What TM1 Fanboy Is
A word, finally, about what this is and is not.
TM1 Fanboy is not a tutorial site. It will not teach you to build a model or troubleshoot a server. It is not IBM documentation, and it is not a consulting shopfront dressed up as a blog. There are good places for all of those things, and this is not one of them.
What this is, instead, is an attempt to take TM1 and OLAP seriously as historical subjects — to treat a piece of enterprise software with the same curiosity, source criticism, and care that a historian would bring to any other artifact of the recent past. The name carries a wink, I know. “Fanboy” admits the affection; it does not excuse the rigor. The affection is why I am writing; the rigor is what I hope makes it worth reading.
A Question Worth Asking
So I will end not with an answer but with the question this whole publication is built around.
Why did TM1 survive when so much else disappeared? Why this product, of all the thousands that were born in the early 1980s and did not live to see the next decade, let alone the next four? The answer is not obvious. It may not even be single. But it is worth investigating, patiently and properly, and that investigation is what TM1 Fanboy is for.
The first step is to go back to the beginning — to a moment before OLAP had a name, before client-server and the cloud, before anyone could have guessed that this small, strange tool would still be here forty years later. To understand why TM1 survived, we have to understand why it made sense in the first place.
Which is exactly where the series begins.