FOUNDER PERSPECTIVE
Every Number Has a Story—and a Source
Understanding the evidence behind a number is part of understanding the number itself.
By Brian Holman · Founder & CEO, Dezota LLC
A number on a screen can look settled. It has a label, perhaps a currency symbol, and often two reassuring decimal places. Yet understanding it may depend on questions the screen has not answered: Where did it come from? What date does it represent? Does it cover the whole account? What information was unavailable when it was calculated? I believe those questions belong close to the result, where people can use them.
Consider a deliberately simple example. A statement shows an account balance of $100,000 at the beginning of a period and $112,000 at the end. We can calculate that the balance increased by $12,000. If the owner deposited $10,000 during that period, however, the entire increase cannot be described as investment growth. Subtracting that known deposit leaves a $2,000 difference to understand. That subtraction alone does not establish a rate of return: the timing of activity and any other relevant flows, costs, or differences in the records still matter.
This is why the meaning of a number matters as much as its arithmetic. A reported value tells us what a source recorded within a particular scope and at a particular time. A calculated value applies a method to inputs. An estimated value depends on assumptions or incomplete information. These descriptions can overlap—a calculation may also be an estimate—and none of them automatically establishes that the underlying records are complete or correct.
My work on complex financial systems reinforced the importance of keeping these distinctions visible. When two records disagree, a useful next step is to understand the difference. The records may cover different dates, include different activity, or answer different questions. Sometimes the available information is insufficient. A discrepancy deserves investigation; it does not, on its own, prove that an institution or a person made a mistake.
At Dezota, that perspective informs how we are developing WealthProof. The principles in our approach to financial clarity call for keeping source information distinguishable from our interpretations, making relevant assumptions recognizable, and leaving unsupported results unavailable. A missing value should not quietly become zero, and a plausible explanation should not become a transaction that the records never established. These are standards for the work as it evolves, rather than a claim that every financial situation is already supported.
Making those distinctions accessible is also a design challenge. People should be able to begin with an understandable overview and examine the supporting details when a question matters to them. A concise explanation of a date, a limitation, or a calculation can be more helpful than a dense screen full of figures. Simplicity earns its place when it helps someone understand the information without concealing something important.
For me, this is a practical measure of financial software: can a person ask a reasonable question about a result and find a meaningful explanation? WealthProof is being developed as an analysis tool, not a financial advisor. Its purpose is to help people understand their records and ask better questions, including in conversations with professionals. A number becomes more useful when the person reading it can understand both what it supports and where its limits begin.