SPEC · OL–02
About

Three careers that made one practice.

Most people would describe my path as a jump from sales into software. I don't see it that way. I see three careers that naturally built on one another.

2005 — Commercial Foundation

Nearly a decade in enterprise sales

Working with multinational companies including Samsung, Panasonic, and Wrangler taught me how businesses actually buy, how customers evaluate value, and how organizations make investment decisions.

  • Negotiation
  • Forecasting
  • Channel management
  • Relationship management
Technical Foundation

Learning to build the thing itself

Curiosity eventually pulled me into software development. As a backend developer, I learned enough to have real conversations with engineers — not just relay requirements to them.

  • Laravel & PHP
  • SQL & APIs
  • Cloud deployment
  • Software architecture
Product Leadership

Where I found the work I actually love

Over time I gravitated toward working directly with founders. Managing timelines was never the favorite part. Helping people answer the harder questions was:

  • Who is this product really for?
  • What problem are we solving?
  • Why will customers buy it?
  • What belongs in the MVP — and what waits?
Philosophy

Building products that matter

I don't believe successful software starts with features.

It starts with understanding people.

Whenever I work with a founder, I try to answer five questions before we talk about technology at all. Technology changes. These questions don't.

  1. Who are we serving?
  2. What problem are we solving?
  3. Why would someone choose this product?
  4. What is the smallest product that delivers value?
  5. How can we build it efficiently?
What makes this different

It isn't Laravel. It isn't Agile. It isn't AI.

It's the combination — commercial experience, technical understanding, product discovery, and delivery leadership — that adds up to a founder partner.