Work
Grouped by the kind of problem rather than by technology. Each entry states what I personally owned, what coding agents implemented, and whether the evidence behind it is public source, a sanitized account of a private production system, or supporting work.
Agents that can act
The useful version of an AI assistant can do more than answer questions. The dangerous version can change real systems without reliable authorization, confirmation, or outcome semantics. I designed DCE's agent workflows around that tension.
Role Product designer and requirements owner for agent behaviour and safety
Read the case study
I did not want an AI assistant that merely remembered facts about the business. I wanted a governed operating layer that could read the correct sources, execute repeatable playbooks, produce auditable work, know which actions required approval, and refuse to guess when the evidence was insufficient.
Role Designer and owner of the operating model; the human approver in every workflow
Read the case study
Tooling other systems depend on
A multi-provider MCP server that gives an agent normalized, read-first access to four pay-per-call platforms — Ringba, Retreaver, TrackDrive and CallGrid — with PII masking, caching, audit logging and a deliberately gated write posture.
Role Product owner; defined the tool surface, safety posture and provider normalization, and directed implementation.
View the repository
An accounts-payable and accounts-receivable tool surface over BILL, covering vendor, customer, invoice and reporting workflows — with money movement separately gated, disabled by default, and MFA-required for the higher-risk payment functions.
Role Defined the tool boundaries and the payment-gating requirements; directed implementation.
Private repository — described here, not linked.
Executive scale
Executive ownership of a $15M marketing budget and a five-person cross-functional organization spanning marketing, technical operations, customer service and financial operations — with the COO as a direct report, five developers on CRM integration work, and a partner ecosystem of roughly 200 organizations.
Role Chief Marketing Officer on the executive leadership team, reporting to the CEO.
Case study in progress. Figures are scale and scope only — NDA limits prevent publishing revenue, CPA or margin.
Smaller, still real
Public source
The marketing site for the marketplace, and the design and engineering baseline this portfolio is adapted from. Supporting evidence of compliance-aware product specification, performance discipline and accessibility as build gates rather than aspirations.
Public source
A checkers implementation, written so I could teach my son the game. Small, finished, and here because a portfolio composed entirely of production infrastructure tells you nothing about the person.