11 / Philosophy
Complexity should live underneath the experience, never inside it.
A systems thinker
Looking past the product to the architecture underneath it
Whatever the problem, his instinct is the same: look at what it sits on top of. A payment problem becomes a question about payment infrastructure. A startup problem becomes a question about what surrounds the founder.
He's drawn to platforms that create leverage for many businesses at once, more than to any single product.
Technology and regulation
Engineering and regulation cannot be treated as separate disciplines
In ordinary software, an outage means a customer can't open an app. In financial infrastructure, it can mean a payment fails to settle or a business can't reach its own funds. The stakes are different.
Moagi treats reliability, security, redundancy, auditability and regulatory compliance as requirements from day one, not features added later. The product's architecture has to match the institution's.
Leadership
A founder needs enough conviction to pursue an ambitious vision, and enough honesty to admit when someone else can execute part of it better.
What he believes
Execution over ideas
An idea is worth little until it has been tested in the market.
Fix the system, not the symptom
A product solves one problem. The infrastructure underneath it can solve the same problem for everyone who comes after.
Hide the complexity
A customer who has to think about the plumbing is a customer the product has failed.
Build for many, not one
Infrastructure built well can serve hundreds of businesses instead of a single customer.
No discount for geography
Technology built in an emerging market should perform to the same standard as anywhere else.
Failure is data
A company that hasn't hit a hard problem yet hasn't really been tested.
How I Think
I start with the system, not the symptom. When something isn't working, the visible version of the problem is usually downstream of a constraint that hasn't been named yet. I'd rather spend the first hour finding that constraint than the first week reacting to its symptoms.
Technology is rarely the entire problem, or the entire solution. The hard part is almost always connecting it to customers, regulation, operations and distribution, and I've learned to be suspicious of any plan that treats the technical build as the main risk.
Infrastructure creates leverage. A product helps one customer. A platform helps a group of them. Infrastructure helps the companies that come after you too, which is why I keep being drawn back to it regardless of the industry.
Complexity should be absorbed by the system, not pushed onto the person using it. If a customer has to understand what's happening underneath, the thing I built hasn't done its job yet.
Access changes outcomes. The right mentor, network or introduction can change a company's trajectory as much as any single product decision. I don't think that's a soft idea. I think it's infrastructure too.
How I Work
I start with constraints. Before I design anything, I want to know what's actually preventing the current system from working, as opposed to what looks like the obvious gap.
I think in systems. Technology, regulation, economics, people and operations are connected, and a change in one usually shows up somewhere else later. I try to see that before it happens rather than after.
I build quickly enough to learn. A plan only produces real evidence once it meets a market, a regulator or a customer, so I'd rather get to that contact point faster and adjust than refine a plan in isolation for longer than necessary.
I prefer leverage over repetition. Where possible, I want the same unit of work to produce a larger outcome the second and third time, which is a large part of why infrastructure appeals to me more than one-off builds.
I want what I build to outlive my involvement in it. A company or a system that depends permanently on one person in the middle of it hasn't actually been finished.
What I Know Now
As an engineer, the job was to make the system work. As a founder, the job became making the business work, which is a different and harder problem, because a working system doesn't guarantee a working company around it.
As an executive, the job shifted again, toward making the organisation work: the part where talented people, process and incentives either compound each other or quietly work against each other.
As someone building infrastructure now, the job has shifted once more, toward making it possible for other organisations to work, which is the furthest I've gotten yet from the original, narrower version of "build the thing."
Each stage didn't replace the one before it. It was built on top of it. I still think like an engineer. I just point it at bigger objects now.
Things I Got Wrong
I underestimated distribution early on. A technically good product does not automatically have a path to the people who need it, and I learned that the expensive way, more than once.
I overestimated what technology alone could solve. Some of the hardest problems I've run into were organisational rather than technical, and I spent more time than I should have looking for a technical fix to a people or process problem.
I learned that founders can become bottlenecks, including me. Hiring someone talented is not the same as building a functioning organisation around them, and a company that routes every real decision through one person is slower than it looks from outside.
I learned that speed without direction is just motion. Moving fast felt like progress for longer than it actually was progress, on more than one occasion.
I learned that organisational debt accumulates the same way technical debt does: quietly, and it gets more expensive the longer it's left alone. Capital can buy time against both. It doesn't substitute for fixing either.
None of this is framed as regret. Failure is information, not identity, and each of these is a lesson I've since built into how I start the next thing.