Why Work With Me

I've been doing this for 30+ years. I've written assembly code for embedded systems and built SaaS platforms that handled millions of transactions. I've seen systems succeed and fail in predictable ways.

I'm not here to sell you Kubernetes or tell you to adopt microservices. I'm here to analyze your specific context and help you understand the actual trade-offs you're facing.

What I Do

I work with CTOs, VPs of Engineering, and technical founders on short-term engagements (2-6 weeks) to solve specific architectural problems.

Common engagements:

  • System audits - You inherited a mess or suspect you're building one. I analyze the architecture, identify risks, and document what's actually there versus what people think is there.
  • Scaling reviews - Your system works now, but you're worried about what breaks at 10x traffic. I map the bottlenecks, stress points, and decisions you'll need to make before they become fires.
  • Technical debt analysis - You know there's rot in the codebase but can't quantify it or prioritize it. I assess what's actually costing you velocity versus what's just annoying.
  • Architecture decisions - You're at a fork: rewrite vs refactor, monolith vs microservices, build vs buy. I analyze trade-offs without selling you a specific solution.

What I don't do:
I don't write production code for you. I don't manage teams. I don't sell you a framework or methodology. I analyze your specific system and help you make informed decisions.

How I Work

Week 1-2: I dig into your system. Code, docs, infrastructure, team conversations. I'm looking for what the system optimizes for versus what you think it optimizes for.

Week 3-4: I document findings. Architecture diagrams, failure modes, incentive structures, second-order effects. Written analysis, not slide decks.

Week 5-6: We discuss trade-offs and paths forward. I don't prescribe solutions—I give you the information you need to make your own decisions.

Deliverable: Written analysis of your system. Clear, specific, technical. No jargon. No recommendations disguised as "best practices."

Let’s talk