The earliest version of this work was hands-on. Agency years at Starkmedia, designing and delivering websites and CMS-driven solutions across industries. Mechanical Engineering coursework at MSOE before that. Founding the school’s first lacrosse club. Running youth programs.

None of it was architecture in name. All of it was design under constraint. The habit that lasted from those years was the discipline of finishing a build on a deadline and learning the difference between systems that work and systems that look like they do.

Gloo was the inflection point. Moving from individual application work into enterprise architecture meant a different unit of design: domain boundaries, API contracts, service interaction models, portfolio-level delivery structures. SAFe came with it.

The lesson that carried forward was that screens and tables follow from the system, not the other way around. By the time I left Gloo I was already drawing the line between business intent and the implementation layer beneath it.

The freelance years were where the practice became my own. Reusable TypeScript MVC frameworks. Config-driven application patterns. Hierarchical knowledge centers connecting strategy content, operational assets, and integrations.

At Nymbl the work shifted toward the customer-facing edge: solution design workshops, technology assessments, analysis of alternatives, technical discovery, demo engineering, and implementation planning. The same architectural discipline, surfaced to clients as a set of structured advisory engagements.

As part of the executive leadership team at Nymbl, the focus shifted from individual functions to company-wide scaling. We co-led Nymbl’s growth from 5 to 75+ FTEs and contractors, building the structure, roles, and delivery pipelines needed to support rapid scale.

The Solutions Engineering function and GTM motion grew alongside it. The pre-sales operating system we built became the repeatable backbone that scaled services revenue from $1.5M to $9.2M in three years.

The work at Nymbl converged into a model I had been circling for years. Value streams. Workflows. Business objects. Interfaces. Rules. Validation points. Metrics. Governance. Not as a slide deck. As a formalized execution model that the company operated from.

PADRE was the GTM expression of it. The Solution Architect work was the engineering expression. The IT Manager work was the corporate and compliance expression. SOC 2 Type II was the trust expression. AI workflow design was the leverage expression. The shape was the same: design the model, then encode it.

Oso Group is the productized form of that model. Independent advisory work focused on enterprise architecture, AI-enabled delivery, and Business Operating System design for workflow-heavy businesses.

The writing on this site is the public-facing version of the thinking. I am most interested in roles and companies working on the durable execution layer underneath these systems. The runtime that knows how to wait, retry, resume, escalate, and remember is the natural fit for the architecture I have been designing.