I build systems that make complex work easier to understand, trace, and act on. My 30 years in enterprise technology and 18 in payments shape how I connect assurance, software, and the people responsible for the work.
I ask questions, think out loud, and enjoy a good back-and-forth. An unexpected connection or a shared laugh can be part of getting somewhere useful.
PCI and SOC programs bring separate business units, shared services, overlapping requirements and several kinds of review into the same work. When ownership or status is unclear, the operating picture becomes hard to trust.
I built an enterprise compliance view in Hyperproof connecting business units and shared services while preserving original sources, explicit ownership, review states, and the distinction between submitted and accepted evidence.
Separately, I built systems using Hyperproof, Snowflake and Arctic embeddings with a natural-language layer for owner workload and evidence questions. Source-linked responses and confidence information support control-intent investigation and human review.
I also developed an AWS Bedrock/Claude workbench for AI-assisted evidence analysis. My approach combines a deterministic core, AI-assisted evaluation and a human review gate. Potential gaps are leads for investigation.
How I build: I use AI-assisted development while remaining responsible for architecture, validation and review decisions. I care whether outputs can be explained, limits are visible, and conclusions can be traced back to their sources.
My operating experience includes more than 150 audits, PCI/SOC assurance across 13 business units and five enterprise-wide shared services, approximately 70 control owners, and 12 engagements in the 2025 cycle.
My current focus is enterprise intelligence, assurance technology and AI systems that preserve context and make the next responsible action clear.
Read the professional experienceOn a farm in Illinois, I learned that normal has a sound. A ventilation fan changing pitch meant asking what had changed, what depended on it, and what might happen next.
My father explained how things worked and gave me room to try, observe and revise. That curiosity carried into a TRS-80, the Grounded Zero bulletin board, telephony, and enterprise technology. The habit of tracing dependencies stayed useful.
Read the full systems-lineage story ↗A farm, a bulletin board, a call center, and a payments business give you different things to figure out. Each has people who know a part of the story you need to hear.
That is part of what I enjoy: ask a question, hear another perspective, and follow the connection. The technical detail can get fairly specific. Occasionally, so can the joke.
What’s the part of the problem that nobody owns?
Tell me where it gets complicated. You don’t need to have the whole thing figured out before we talk.
Start a conversation →