I'm Bee. I fix
broken CX systems.
I help B2B SaaS companies unify Community, Knowledge, Self-service, and Intelligence into one connected customer system — so customers can find the right answer, trust it, and keep moving without friction.
The audit or the
ongoing partner.
Start with a sharp diagnostic or bring me in as your embedded CX lead. The goal is the same: a customer experience people can trust, move through easily, and rarely have to think about.
CX Architecture Audit
I spend 60 minutes walking through your customer experience exactly the way your customers do: live, out loud, and without a guided tour. Then I show you exactly where the pavement cracks—where the experience breaks trust, creates friction, and forces customers to work harder than they should.
You get the recording, a written summary, and a prioritized fix list. One hour of footage worth more than a 40-page audit.
- →Live recorded walkthrough — Stress-testing the journey across your help center, search, AI bots, community, and docs.
- →Findability & AI spot check — Testing for accuracy, trust, and hallucinations when customers need immediate answers.
- →Shadow CX & Flow gap mapping — Identifying contradictions across siloed touchpoints and exactly where customer momentum breaks.
- →The Deliverables — The raw 60-minute footage, a written architectural summary, and a prioritized fix list.
No ongoing commitment · Audit fee fully credited if you continue to a fractional partnership
Fractional Experience Architect
I act as the principal architect for your digital CX — designing the systems between knowledge, community, self-service, and AI, and building where your team can't. I close the gap between strategy and production. So you get world-class CX that scales without world-class effort.
- →Experience infrastructure roadmap ownership — Mapping fragmented AI touchpoints and building the orchestration layer that connects them.
- →EX = CX alignment — Navigating ambiguous organizational boundaries across Product, Marketing, and Support to turn competing priorities into a single, executable CX plan.
- →Consolidation & Cleanup — Assessing your existing knowledge and chat surfaces to determine what to sunset, merge, or integrate into a single coherent path.
- →Knowledge architecture — KCS implementation, structured content, and article workflows that don't go stale.
- →Community system design — Positioning community as a core guidance layer (not a side room).
- →Self-service, AI & Automation — Designing and building the delivery mechanisms (chatbots, automated workflows, portals) and removing friction from the customer path.
- →The Intelligence layer — The telemetry of your CX: analytics, feedback loops, health scoring, and the signals that tell you exactly what to fix next.
- →High-leverage, async-first delivery — Dedicated Slack access for quick unblocks, plus deep monthly strategy reviews and written roadmaps.
3-month minimum · Rolling monthly after · 30-day cancellation
Strictly limited to 2 concurrent partners.
Currently booking for Q2 2026.
You don’t have a support problem.
You have experience debt.
Nobody architected this.
It accreted — one help center, one chatbot, one community migration, one workflow, one AI experiment, one "temporary" workaround at a time — into a customer experience no competent systems architect would have designed on purpose.
In software, there’s a name for this: technical debt.
In CX, it looks different. But it behaves the same way.
It’s experience debt: years of fragmented decisions, disconnected touchpoints, stale knowledge, and missing ownership quietly compounding into friction customers feel every time they need help, guidance, or confidence.
And underneath almost all of it is the same failure:
Context doesn’t survive the journey.
Customers arrive with a job to do and a specific moment they’re in — onboarding, troubleshooting, evaluating, replacing an admin, recovering momentum after something broke.
But most systems don’t carry that context forward.
- The help center doesn’t know what they already tried.
- The chatbot doesn’t understand where they are in the journey.
- The community has the practical answer, but it lives off to the side.
- Support gets the case after self-service already failed.
So customers do the stitching themselves.
- They re-explain.
- They re-search.
- They re-evaluate which answer to trust.
- They restart at every handoff.
That isn’t a content or ticket problem. It’s an architecture problem.
- → Search returns something, but not the thing the customer actually needs
- → The AI answer sounds plausible but weakens trust the moment it matters
- → The community contains the real answer, but it isn’t part of the official path
- → The docs are technically accurate but unusable in the moment of need
- → Customers hit a second login, second search, second navigation, second source of truth
- → Support exists partly to catch what self-service should have resolved upstream
- → Different teams own different touchpoints, but nobody owns the journey between them
- → Customers carry context through your system by hand just to get unstuck
Customers are doing work the experience should have done for them
When customers have to figure out where to go, which source to trust, what applies to their situation, or what step comes next, the system has already failed upstream.
That isn’t support operations. That’s broken experience infrastructure.
Context dies at the handoff
Most companies lose context between docs, search, community, AI, product, and support. Each touchpoint works locally. None of them work as a system.
Every transition costs the customer effort, confidence, and momentum.
AI is amplifying whatever truth problem already exists
If the knowledge underneath it is stale, contradictory, or disconnected from real customer workflows, AI just delivers bad guidance faster and with more confidence.
That’s not innovation. That’s scale applied to confusion.
No one owns the upstream system
Product owns the product. Docs own the docs. Support owns the queue. Marketing owns the story. Community gets treated like a side room. Nobody owns the full customer path between them.
That gap is where experience debt accumulates. That gap is where Shadow CX takes hold.
Teams building customer touchpoints without coordination, shared context, or system-level ownership.
Before AI, that created slow friction. Now it creates fast friction.
Any team can ship a new customer touchpoint in a week. Very few companies have designed how those touchpoints work together, how context moves between them, or how trust is maintained across the journey.
Most companies try to add delight before they’ve repaired continuity.
But customers don’t need more personality layered on top of fragmentation.
They need an experience that knows enough, connects enough, and holds together well enough to help them keep moving.
That’s the job of CX architecture: preserving context from first question to final resolution.
Not a framework I borrowed.
One I built.
Most companies don’t have a CX problem because they lack tools. They have a CX problem because the tools don’t behave like a system.
Every interaction makes the next one cheaper.
A good answer shouldn't die in one place. The best answers should improve your docs, search, chatbot, and the next customer's path through the experience all at once.
Read more →They have the pieces. They don't have the loops.
They treat community like a side room instead of part of the product experience. Marketing owns the story. Docs own the details. Support owns the queue. Community gets stuck in the middle, expected to drive engagement but not trusted to shape the customer journey.
Read more →Which loops are broken and where the leak is biggest.
The audit shows which parts of the experience feel disconnected, where customers lose confidence or momentum, and which fix will create the clearest downstream improvement first.
Read more →
I audit companies
publicly.
These reviews show how digital CX breaks in the real world: fragmented search, disconnected systems, weak guidance, and AI layered on top of knowledge gaps. No theory. Just the moments where customers lose trust, momentum, or both.
1Password
Everything is siloed. Help center search returns only support articles, not community answers, not Academy content, not docs. Separate logins. Separate domains. Every fork is a customer lost before they got their answer.
Spotify
Community and help center are fragmented subdomains with different UX, different logins, different search. The ideas board exists but only 1 item is marked "implemented." Customers are shouting into a void.
Next up
Drop a suggestion in the Hive Five or on X. If it's interesting to audit, I'll do it. The reviews go to 4,500+ subscribers before they land here.
Not a support leader.
An experience architect.
Customers don't come to your product looking for support. They come to get something done. Service is what happens when the experience breaks and pulls them out of flow.
I design and build the invisible systems that keep customers moving.
The best CX is like a smooth sidewalk: it lets customers get where they're going without forcing them to look at their feet. They shouldn't notice your infrastructure, they should just finish what they came to do.
That includes the layer most companies ignore: community as practical guidance, not just engagement.
Self-service that actually answers the question. Knowledge that doesn't go stale. AI that gives the right answer instead of a confident wrong one. Guidance that holds up the moment a customer needs it, not after they've given up and opened a ticket.
That's not support ops. It's experience infrastructure. And it lives upstream: before the confusion, before the handoff, before the ask.
I'm not here to build a buzzword-heavy AI vision from a blank page. I'm not here to hand you a roadmap and leave. I build the thing. I'm here to untangle complicated organizational situations, navigate legacy constraints, and build an orchestration layer that actually works in production.
Common questions
Is the CX Audit actually useful if we don't continue? +
Yes. It's not a disguised sales pitch; it's a pure diagnostic. You get an unedited recording of exactly where your customer journey breaks down, why momentum stalls, and where trust is lost. I hand you a prioritized fix list. Many teams take that architectural roadmap and execute it internally.
Do you only work with cybersecurity and B2B SaaS? +
I specialize in complex, technical B2B products where the gap between Marketing, Docs, and Support is the widest. If your product requires a community, a knowledge base, and self-service AI to succeed, the rules of experience infrastructure apply regardless of your specific vertical.
Can the audit roll into a fractional partnership? +
Yes. The $1,500 audit fee is fully credited toward your first month if we decide to work together. However, because I operate as an active practitioner rather than a full-time agency, I strictly limit my fractional partnerships to two companies at a time to guarantee high-leverage, focused impact.
How does the fractional partnership actually work? +
I don't sell hours; I sell architecture and outcomes. I operate as your async, high-leverage Experience Architect. I build the infrastructure roadmaps, orchestrate the connections between your four pillars (Community, Knowledge, Self-service, Intelligence), and guide your internal team on execution. We use a shared Slack channel for quick async unblocks and monthly strategic reviews to ensure the systems are compounding.
Are you a full-time consultant? +
No, and that is your biggest advantage. I currently lead digital CX strategy at an enterprise cybersecurity company. I am not an outside theorist relying on consulting playbooks from 2021; I am actively building, breaking, and fixing experience infrastructure at scale every single day. I bring that real-time, battle-tested expertise directly to my limited roster of fractional clients.
What specific platforms or tools do you work with? +
The tool matters far less than the system. Whether you use Zendesk, Salesforce, Discourse, Khoros, or custom LLM deployments, my job is to build the integration loops between them. I focus on how your self-service layer talks to your knowledge base, and how your community data feeds your AI models to create a smooth sidewalk for your customers.
Ready to start
You don't rise to your growth goals.
You fall to the level of your CX systems.
I work with teams that are ready to make the customer experience clearer, more connected, and easier to trust. If that's you, send me the problem and I'll review it asynchronously.