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

01

Execution over ideas

An idea is worth little until it has been tested in the market.

02

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.

03

Hide the complexity

A customer who has to think about the plumbing is a customer the product has failed.

04

Build for many, not one

Infrastructure built well can serve hundreds of businesses instead of a single customer.

05

No discount for geography

Technology built in an emerging market should perform to the same standard as anywhere else.

06

Failure is data

A company that hasn't hit a hard problem yet hasn't really been tested.

These principles are shared in person, at events and in the classroom.

See speaking engagements