About Luhn
Why the name. Why the discipline. Why accountability. What we operate now.
In 1958, an IBM researcher named Hans Peter Luhn published A Business Intelligence System. He proposed an automatic system that would gather, abstract, and route information to the people in an organization who needed it — calibrated to their specific decisions. It was the first time the phrase business intelligence entered the technical literature with the meaning we recognize today.
Luhn also published, in 1954, the algorithm that validates credit card numbers. It catches the typo when two digits are transposed. Seventy years later it is still in continuous use. His real contribution wasn't a faster system. It was a system that knew when it was wrong.
We named this company Luhn for that lineage: information compressed for the people who need it, calibrated against error, and accountable for being wrong.
The phrase business intelligence appeared in print earlier, in 1865, in Richard Millar Devens's Cyclopædia of Commercial and Business Anecdotes. Devens described Sir Henry Furnese — an 18th-century English banker who built his fortune by gathering information across Europe and acting on it before competitors could. The phrase has been a description of edge-through-information ever since.
Luhn formalized the practice as a system. We sit in both traditions.
Most market narratives in multifamily and proptech are written with conviction first and evidence second. They look authoritative the day they publish. They are rarely revisited when they turn out wrong.
Luhn inverts that. Every brief carries an evidence boundary, a counter-signal, tracked predictions, and a revision history. When a thesis weakens, the public record shows it weakening. When a prediction fails, the failure is published. The accountability is the product.
The lineage is not nostalgia. It is the operating standard of the current product.
- 01Information compressed for decision-makersBriefs are written for operators, capital, and counsel — not for impression count.
- 02Source proximity over volumeSource quality is weighted by publisher proximity to the source event, not by feed configuration.
- 03Explicit evidence boundariesEvery brief states what it does not claim. The line between observed events and posture is drawn, not implied.
- 04Predictions tracked over timeEvery brief carries monitorable Watch Next events. Outcomes are published — including the ones that fail to materialize.
- 05Corrections preserved, not hiddenRevisions to a published brief remain on the public record. The original claim and the correction are both inspectable.
For the discipline in full — read the methodology →