Code to community to customer experience
At my core, I want to help people get unstuck and do their best work.
Over time, that became a specific conviction in my natural habitat, the digital world. When customers struggle digitally, the problem is usually not the person. It’s the system around them.
That conviction is what I bring to my day job, and every engagement, whether it’s a five-day diagnostic or a six-month fractional build.
“You don’t rise to the level of your growth goals. You fall to the level of your customer experience systems.”
FROM INTERNET COMMUNITIES TO CX SYSTEMS.
I came to this work through community, long before “community” or “CX” were job titles.
I started building websites at 13 and learned the internet from the inside out: forums, IRC, file-sharing scenes, web design boards, and online communities where reputation was earned by being useful.
I have been hooked on the web and self-taught from the beginning. That still shapes how I work.
In cybersecurity, I spent years in the communities around Bugcrowd, HackerOne, NahamSec, and Unsupervised Learning, not as a vendor, but as someone who showed up, moderated, and helped build the spaces where researchers actually got work done.
That gave me a front-row seat to how people actually experience products: where they get stuck, what they misunderstand, what they avoid, and how much invisible labor they take on just to keep moving.
At the same time, I was building the technical foundation underneath that work: web development, systems thinking, security research, writing, automation, and digital operations.
That combination is what eventually pulled me into customer experience: the human pattern recognition from community, and the systems instinct from building on the web.
CONVICTIONS
- • Customers should not have to become the integration layer between your teams and tools.
- • Better self-service moves the system closer to the customer’s intent.
- • Every re-login, re-explanation, and dead-end search is a tax your customers pay for your architecture choices, and it shows up on your cost-to-serve.
- • You don’t rise to the level of your growth goals. You fall to the level of your customer experience systems.
- • A system that doesn’t learn from its own friction will repeat every failure at the scale of every new customer.
- • AI doesn’t fail because the model is weak. It fails because the knowledge, routing, escalation, and governance underneath it are broken.
- • CX is a product, not a department.
- • A good fix should become infrastructure, not another workaround.
- • Don’t accept the defaults.
THE PATH HERE
Building toward CX systems architecture.
Built and broke web apps, automations, and digital systems for startups and independent clients for a decade. Includes front-end engineering on Federacy, a pentest and bug bounty platform, researcher dashboards, submission workflows, and payout systems.
Owned the researcher-facing help system across Zendesk, Discord, and Discourse for a technical cybersecurity audience. Unified three surfaces into an intent-based architecture. 10% ticket volume reduction, 25% fewer repeat questions.
Own the digital support roadmap across community, knowledge, self-service, AI, and Salesforce-based experiences for an enterprise cybersecurity platform. This is where I apply the full system: CX architecture across community, self-service, knowledge, AI, communication, and Salesforce-based customer experiences, built to lower cost-to-serve and hold operationally.
WHERE THE WORK LIVES
I help technical software teams design and build the systems customers rely on after they buy — through Intent Gap Diagnostics and fractional CX systems architecture engagements.
See what your customers actually experience →Every Monday to 4,500+ readers who care about security, technology, community, AI, and building a life on the internet.
Subscribe to Hive Five →Detailed, outside-in walkthroughs of real companies’ customer experiences: what works, what breaks, and what the underlying system is optimizing for.
Read the latest review →OUTSIDE OF WORK
Outside of work, I’m a family man who loves cooking, usually without a recipe, though I can follow one when needed. I read widely about how other operators think and work. I enjoy biographies, documentaries, anime, hip-hop, metal from time to time, and weird corners of the internet that still feel handmade.
I share most of this and more in my weekly Hive Five newsletter. If I’m honest, I’m still glued to a laptop most of the time. I’m drawn to how people think and work, and I want to share that with you. I also nerd out on workflow setups, the apps people use and how they make them their own.
The best way to start is the Intent Gap Diagnostic.
I’ll walk your customer experience the way a customer does, map where intent and system diverge, and show you what to fix first, and what it’s costing you. No access required.
If you want to see how I think before you reach out, start with the Resources.
Intent Gap Diagnostic · 5-day turnaround · no access required
Resources →