Finance  ·  Analytical systems  ·  Research

I build analytical systems that make complex financial decisions easier to understand.

Understanding comes first. Software is simply the medium.

Private credit
Private equity
Capital structures
Portfolio analytics
M&A

Selected work

Things I've built

Each project is a way to explore a question, not a finished product.
More on the way
FRAMEWORK · SCHEMATIC Performing — marked at par Grey zone — accruing, marked below par Non-accrual — officially distressed the question: does the grey zone hide stress the headline non-accrual rate never shows?

Distress Lens

A data investigation into the gap between reported and economic health across private-credit portfolios — built from public filings, industry-level only.

In progressComing soon

Credit thesis

A written investment memo on a single name — the piece where the judgment does the work and the model just supports it.

PlannedOn the bench

More questions than projects

New explorations land here as I chase them down. If you're working on an interesting financial problem, that's often where the next one starts.

Start a conversation
How I think

A framework for every analysis

01Question
Start with a real problem worth understanding.
02Framework
Break it into core drivers.
03Model
Translate it into deterministic logic.
04Stress
Change assumptions; find the breaking points.
05Interpret
Derive the insight that matters.
06Communicate
Make it clear, concise and honest.
Questions I'm exploring
What actually determines how much covenant flexibility a lender gives up?
When does leverage stop creating value and start destroying it?
How much do capital-structure choices change what recovers in a default?
Can a fund's own marks reveal stress before the non-accrual rate does?
How should portfolio-level credit risk actually be visualised?
I'm always chasing a new question.
If you're working on something interesting, I'd like to hear about it.

Principles that guide my work

Deterministic over opaque

If I can't explain the number, I don't use it.

Explain before predict

Understanding today beats a forecast I can't defend.

Every assumption visible

A model is only as honest as the assumptions behind it.

Judgment over automation

AI does the work; the judgment stays mine.

I don't build models to predict the future. I build them to understand what breaks first.


About

I work in investment research and private markets, and I enjoy the intersection of finance, software and analytical thinking.

Whenever I hit a financial problem that feels difficult to reason about, I tend to end up building something to understand it — sometimes a model, sometimes code, sometimes both. The goal is never the software. It's the understanding.

Let's talk about finance, models or ideas.

I value a thoughtful conversation over networking. If you're working on an interesting problem — or you think differently about an assumption I've made — I'd genuinely like to hear about it.