I am a systems builder at heart and whether it be a MarTech platform, a website, or AI governance and implementation, I approach them all with the same mindset. Outputs are not limited by their inputs. They are limited by the system holding them together. Even old bananas can become banana bread when put through the right system, and that is how I build.
Take my portfolio site as an example. I developed my own physics-based design system; not because other systems would not have worked, but because I dared to ask "what if". What if I looked at a design system not in rules designed to prevent breaks but in rules designed to turn those breaks into design features. What if I thought ahead about what a builder would want to do and built a system that allowed and controlled it, instead of forcing them to implement ungoverned workarounds to achieve it. What if instead of the builder feeling like they left something on the table because the system prevented it, they instead had time to try even more and push creativity even further. How different would the output be if instead of saying no we asked what if. When I build systems I do not just build them to outcomes. I build them to the people using them.
That same mindset is what allowed me to function as the sole director, systems builder, editor, and administrator for the entire web presence of a $7B financial institution for six years. Seven lines of business, hundreds of pages, and a platform that was expected to grow. The systems I built to manage that complexity did not just keep things running, they bought me time. Time to build creatively alongside marketing, digital, and paid campaigns. Time to focus on growth initiatives, ADA improvements, and the things that make a website stand out rather than just function. That is what good systems do. They do not just produce the required output. They create the space to exceed it.
AI Workflow & Governance Design
Web Platform Architecture
CMS & DXP Ownership & Governance
Content Modeling & Taxonomy
Platform Migration & Launch
Process Audit & Gap Analysis
Stakeholder Management & Alignment
Marketing Operations & Workflow Design
Vendor & Agency Management
SEO Strategy & Execution
Conversion Rate Optimization
Release Management & QA
My technical background spans website builds across a range of modern web platforms. I recently completed custom builds on WordPress and a full headless stack utilizing Contentful and Next.js. For these builds I not only built the website but also created the systems needed to keep them running optimally into the future. On the other side of my skill set is the stewardship and procedural development of a $7B financial institution's digital experience platform built on the Sitefinity .NET CMS; turning it from a turnkey experience into a systems-first web presence. Organic search grew steadily from 15% to 27% of total sessions, matching the financial services industry benchmark. Engagement rate peaked at 65% against an industry average closer to 50%, and the platform maintained zero hours of unscheduled downtime across my entire six-year tenure.
I believe every system and system design project can be broken down into three parts: what goes into the system, the system itself, and what comes out of it. My first objective is always requirements gathering; understanding the inputs and the intended outcomes. What is the purpose, what are the constraints, who is it for, and what does a successful result look like. Once I have that foundation I design the simplest viable system that turns those inputs into the required outputs. Once I am confident the core system works, than I can start making it robust enough for the real world. That means building guardrails, intake governance, and operational procedures to keep inputs clean, surface and identify failure points early, and ensure outcomes maintain the required standard over time. Systems are always growing and evolving. Building them flexible enough to handle that growth while strict enough to consistently produce the right outputs is the objective I am always chasing.
I started using AI as an efficiency tool, generating algorithms, building basic CSS, and accelerating execution of my day to day workflows. As my AI maturity grew however so did my ability to create systems to govern it. I shifted from a builder who used AI to speed up coding and build efficiencies to an architect who creates a series of rules and governance systems for the AI to follow, ensuring intended outputs while reducing AI hallucination and the headaches that go with it. My real growth now is not just in utilizing AI but in reducing the token cost associated with each request by further developing the governance and rules to reduce processing cycles required to achieve a satisfactory outcome.
Creative Flow Architecture is a physics-based grid layout framework I designed from scratch because no existing methodology could achieve the creative flexibility I wanted without sacrificing structural integrity. Creative Flow Architecture was built the same way I build every system. I identified the problem, defined the intended output, and anticipated what a builder using the framework would actually want to do. Then I built rules around not just the output but around those interactions, designing the governance to work with the user rather than against them. I used AI not as a builder but as an engineering and physics expert, stress testing my thinking and working through the math required to make the framework structurally sound. Every governance decision, every rule, and every constraint made during that process is what this portfolio site runs on today.
I approached governance at HomeStreet Bank through two parallel principles. First, designing structured procedures built alongside the CMS itself to ensure process and platform were aligned from day one. Second, maintaining clearly defined expectations communicated to lines of business leaders, corporate leadership, and marketing stakeholders company wide. The governance and systems I put into place significantly reduced our reliance on external web vendors while giving me as the sole operator the freedom to focus not only on maintaining the platform's new high standards but on pursuing continuous growth through testing, development sprints, and feature implementation.
Growth starts internally before it shows up in any dashboard. At HomeStreet I simplified the content request funnel and established clear corporate-wide web standards so every page had a defined purpose from the start. Education pages educated, CTA pages drove clicks, no more double duty. That internal discipline is what made external performance possible. From there I aligned SEO and development efforts directly to active marketing and digital campaigns, turning what are often treated as separate channels into a single cohesive funnel. Keyword strategy was tied directly to business KPIs rather than traffic volume alone, pushing focused SEO efforts where the business needed growth rather than where rankings were easiest to win.
Stakeholder management was one of the more complex parts of owning a website at a regulated financial institution with multiple lines of business. My approach was proactive rather than reactive. I held bi-quarterly meetings with each line of business lead alongside their marketing counterpart, auditing all pages tied to their area, identifying content that needed immediate updates or was approaching a refresh, and having them submit a wish list ahead of each meeting. By staggering these meetings across the quarter I ensured every line of business had a dedicated voice without any single team dominating the roadmap. This structure largely eliminated competing priorities before they became conflicts. For high-demand real estate like the homepage hero, I let that direction flow from leadership. CEO, board, and director-level priorities set the hierarchy. Ultimately aligning the decision with organizational direction meant the decision was never mine to make unilaterally.
I am looking to move beyond simply owning operational platforms to designing the systems and procedures that govern them. Having been on both sides of that equation, operating inside an overly governed enterprise environment and rebuilding a largely ungoverned one from scratch, I have found that the best designed systems are the ones the users rarely have to interact with. Implementing systems that anticipate what the user will try to do before they do it and account for it in advance is where I get the most satisfaction. AI has influenced this shift not because it is removing the need for web managers entirely. I would argue, if anything, it is making them even more capable and, because of that, reducing reliance on external vendors. For me, however, it provided the toolkit I needed to fully understand my strengths and recognize that what I have always been drawn to in web development and platform ownership is the systems design behind it.