About
Mathew Moxness is an investor, entrepreneur and operator. His work centers on real assets and private businesses — finding them, acquiring them, improving them and operating them with a long-term owner's perspective.
The work has a shape to it. Find something mispriced or poorly run. Understand what can go wrong before committing capital. Structure the transaction so the downside is survivable rather than theoretical. Then spend years on the unglamorous part: the operations, the reporting, the small corrections that compound.
Before real estate there was software. Websites, databases, hosting, search, internet businesses — enough of it to learn early that most of what an organization does is information moving from one place to another, usually badly, and that the cost of fixing that is almost always lower than it looks.
Those two threads stayed largely separate for years. They no longer are. Software and artificial intelligence have made research, underwriting, analysis and operational monitoring cheap enough to be continuous rather than occasional. That is a change in economics, not a change in identity. The questions worth asking about an asset are the same as they have always been; what has changed is how quickly and how cheaply they can be answered.
Increasingly the work involves building rather than buying. Where general-purpose software does not fit the operating problem, he develops purpose-built systems around what a business actually does — its data, its workflows, its operating rules, the decisions that recur — designed to research, monitor, analyze and support execution continuously.
The useful result is a tighter loop between what is happening inside a business, what the organization knows about it, and how quickly that information becomes a decision.
The objective is not to automate everything. It is to be honest about what people should remain responsible for, what software can be trusted to handle reliably, where continuous analysis genuinely improves on intermittent human attention, and where the combination beats either alone. Done carefully, the result is an organization that is faster, better informed and more capable than its size would suggest.
He tends to be early to new tools and slow to new conclusions. Most tools do not survive contact with a real operating problem. The few that do change what is worth attempting.
The approach underneath all of it is unremarkable to describe and difficult to actually do: understand the fundamentals, stay adaptable, and keep the attention on execution long after the interesting part is over.