I’ve been building and fixing operational systems my entire career.
The tools have changed. The problems haven’t.

Most people who end up in RevOps came from sales or marketing. I came from both, and from a decade running professional kitchens before that.

I started in marketing and creative direction. City marketing director, creative services manager, advertising coordinator, years of understanding how you communicate a brand, run campaigns, and build the visibility that turns into revenue. That background still shapes how I think. I’m not just fixing your CRM data. I understand why that data exists and what it’s supposed to do for your business.

Then I spent over a decade as an Executive Chef and Chef de Cuisine across Colorado. If that sounds like a detour, it wasn’t. A professional kitchen is a systems operation running under real-time pressure. Bad process costs money immediately. You can’t fix it after service, you fix it before, or you absorb the loss. That discipline, building workflows that don’t fail under pressure, designing systems for people who don’t have time to read instructions, is exactly what I bring to automation and operations work.

The digital systems career grew out of all of it. I spent seven years as the sole digital systems authority for a global e-commerce skincare brand, five of those years owning HubSpot completely. I ran the full CRM migration from scratch. I built and maintained the WooCommerce integration. I reconciled the CRM against QuickBooks at the invoice level, across multi-currency transactions, for years. I extended the platform with Make and n8n when HubSpot hit its ceiling.

That experience is the origin of Basëthic. I built it because I kept seeing the same problems, systems that were technically running but quietly misaligned, data that nobody trusted, gaps between tools that created manual work nobody budgeted for. The fix is almost never a new tool. It’s connecting the ones you already have.

More recently I’ve been building deeper into AI-assisted automation. DatumLock is a personal project I’ve been developing, a structured knowledge architecture for AI-assisted project development that keeps LLM workflows tethered to defined parameters rather than drifting on scope. LociOS is the larger system being built on top of it. These aren’t client offerings yet, but they reflect where I believe operational intelligence is heading and where my technical work is focused.

I work with companies in the $2M to $50M range, typically businesses that have accumulated the right tools but haven’t fully connected them. If your data is right but your systems don’t talk to each other, that’s the problem I solve.