I've spent fifteen years building the systems that sit underneath good customer experiences: the content architecture, the data orchestration, the operational workflows that most people never see and every good product depends on. I founded CR-WK in 2010 to do this work for enterprises and mission-driven organizations that needed their digital infrastructure to actually hold together, not just look good in a demo.

My approach starts from a simple observation. Most organizations don't have a shortage of tools. They have a shortage of coordination between the tools they already have. Marketing platforms, CRMs, content systems, and now AI layers, all bolted on separately, each producing value in isolation while the organization as a whole stays fragmented. I build the architecture that connects them, so intelligence and information move where they're needed instead of getting trapped in silos.

What I actually do:

Enterprise content architecture. Structuring how information is created, stored, governed, and surfaced across systems to ensure it remains usable as an organization scales. This is the unglamorous work that determines whether everything built on top of it holds up or quietly breaks down in eighteen months.

AI-assisted workflow design. I design and build practical AI integration into existing operations, from customer engagement platforms to internal knowledge systems. I wrote a white paper on this, "A Human-Centered Architecture for Coordinated Enterprise Intelligence," arguing that most enterprise AI deployments fail not because the technology is weak but because the architecture around it is fragmented. Human oversight stays permanent. Context comes before capability. That's the standard I build to.

Customer data and journey orchestration. Mapping how a customer actually moves through an organization's systems, then designing the data architecture that lets every touchpoint act on the same accurate picture of that person.

Digital transformation and marketing technology. Modernizing legacy systems and connecting marketing stacks so campaigns, content, and customer data reinforce each other instead of duplicating effort three different ways.

Recent work includes serving as sole architect on a large-scale customer engagement platform for a Fortune 500 hardware and technology company, where I authored the full technical and content architecture documentation myself. I've also run formation consulting engagements for mission-driven organizations building their operating systems from the ground up, applying the same structural thinking whether the client is an enterprise IT department or a nonprofit standing up its first real infrastructure.

My background isn't a straight line through corporate IT, and I think that's an asset. I managed enterprise systems and built SQL automation tools for an organic agriculture company. I did digital advertising architecture for automotive platforms. I spent nearly a decade in nonprofit governance and finance, eventually managing a seven-figure budget and authoring the financial policy manual for an intentional community organization. Each of those environments taught me the same lesson from a different angle: systems fail when the conditions underneath them are wrong, not because the people running them are careless. Fix the conditions and the outputs follow.

That's the philosophy behind everything I build. I don't lead with it on client work, but it tells you how I think about a project before I ever open a laptop. I'm not going to hand you a tool. I'm going to ask what conditions are producing your current results, then build the architecture that changes them.

How I work: direct, structured, and honest about scope. I'll tell you early if a project needs more foundational work before the visible feature can be built right, because that work is usually where the real value lies, even though it's the least exciting part to sell. I document as I go. I don't disappear for two weeks and reappear with a surprise. If something in the requirements doesn't make sense structurally, I'll say so before building it, not after.

I work well with organizations that already have some infrastructure in place and need it to actually work together, technical leads who want a collaborator rather than an order-taker, and teams tackling the unglamorous integration work that everyone knows needs to be done and nobody wants to own.

If you're dealing with fragmented systems, a customer data picture that doesn't reflect reality, or an AI initiative that's produced many demos but little coordinated value, that's the work I do. Happy to talk through what you're actually trying to fix before either of us commits to anything.
less