System architecture analysis

Find the problems before your users do.

30+ years building, breaking, and fixing complex systems. I analyze what you have, identify where it's headed, and help you decide what to do about it.

Hero
30+ years building production systems I've built systems from scratch and inherited disasters I analyze systems, not sell solutions

What makes analysis different:

  • I look at what the system actually does, not what the docs say
  • I identify incentive structures and second-order effects
  • I document trade-offs, not prescribe "best practices"

Why 30 years matters:

I've seen the same architectural patterns succeed and fail across decades. Enterprise applications. Web applications. SaaS platforms. The technology changes but the failure modes don't.

I know where systems drift because I've watched it happen in slow motion. I can spot the gap between "what we built" and "what we actually need" because I've been on both sides of that gap.

Experience

Billivio - Usage metering and entitlement system

Tracks and enforces usage limits for pay-per-use products. Taught me how payment flows create race conditions.

Visit Billivio.com

Daklens - CSV data cleaning tool

Transforms messy data exports into clean files. Taught me that data import is where most systems actually break.

Try Daklens.com

JustHTML.dev - No-npm developer community and methodology

A community platform and resource hub for developers building without frontend frameworks. Taught me that dependency bloat is an architectural decision, not a tooling inevitability — and that the npm supply chain is a systemic risk most developers inherit without choosing.

Visit JustHTML.dev
See what building these taught me about architecture

Join the list

Get practical notes on architecture, systems, and where they tend to break — no spam.

Have a project in mind?

Send a note. I read everything.