The Epiphany Bridge, Applied: How I Sell Medical Device Cybersecurity And How I Lead

Russell Brunson calls it the epiphany bridge. The move is simple, and almost nobody in cybersecurity does it. Instead of pitching your framework, your certifications, or your service catalog, you retell the exact moment your belief changed, in enough scene detail that the listener feels the shift you felt. They do not walk away with your conclusion; they walk away having relived the moment that produced it. That is why they change behavior, and why a features list never gets them there.

I have run this in two arenas that look nothing alike from the outside. Selling medical device cybersecurity at Blue Goat Cyber, and leading the people who deliver it. Both arenas got dramatically easier the second I stopped opening with the answer and started opening with the moment.

Why The Feature Pitch Fails

The wrong pitch, and the one I gave for years, goes like this. We do premarket cybersecurity for FDA submissions. Threat modeling. SBOM. Postmarket monitoring. Penetration testing under FDA guidance.

Every word is true. Buyers nod. Nobody buys.

They do not buy because a features list asks the buyer to do the hardest cognitive work in the room, which is to assemble your capabilities into a story about their problem. Under stress, nobody does that. They default to whatever story they walked in with, which is usually "cybersecurity is a compliance task, we will bolt it on before submission, our documentation vendor can probably handle it." Your feature list does not compete with that story. It sits next to it.

The epiphany bridge replaces the story. Not by arguing against it, which triggers defense, but by giving the buyer a new scene that reorganizes their thinking on its own.

The Blue Goat Cyber Version

Here is the version I actually use now, compressed. The full version has more scene, and takes about three minutes.

Old belief, the one almost every device team walks in with. Cybersecurity is a compliance checkbox you finish before the submission ships.

The moment. Sit with me in a conference room in 2019. Class II device, second submission cycle, a team of very good engineers who had done everything their documentation vendor told them to do. The FDA reviewer's response was not a redline. It was a Refuse to Accept letter, and the specific line was about threat modeling that did not match the architecture the device actually shipped. Nine months of runway, gone in a single email. The founder in that room did not need a lecture about SBOM. He needed to see, in that scene, that the reason he had just lost nine months was not that his team was lazy. It was that the entire industry had trained him to treat cyber as documentation, and documentation cannot survive contact with a reviewer who reads code.

New belief. Medical device cybersecurity is a submission-quality problem, not a paperwork problem. Treat it like engineering and the FDA clears you. Treat it like a checkbox and you burn a cycle.

The bridge. That is why my team at Blue Goat Cyber runs it as engineering, and why we have supported 250+ FDA submissions with zero failing to clear on cybersecurity.

Notice what did not happen in that pitch. I did not list services. I did not name a framework. I did not compare us to a competitor. The buyer's belief moved because they lived through the scene, and by the time the number lands at the end, they are already inside the new frame. The features get to show up later, on a scoping call, where they belong.

The reason this works, and the reason I wish I had run it a decade earlier, is that in cybersecurity we have trained ourselves to sound smart instead of sound true. The epiphany bridge is what true sounds like on a sales call.

The Leadership Version

The same mechanic, pointed inward, is the reason The Secure Methodology actually gets adopted by teams instead of shelved next to the other frameworks.

Most leadership advice fails for the exact reason most cybersecurity pitches fail. It is delivered as a rule. Listen more. Give feedback. Assume good intent. Rules do not move people. The story of the moment the leader learned the rule does.

When I coach an engineer stuck in "smartest person in the room" mode, the underlying skill gap is almost always cognitive versus affective empathy. The intervention is not the label. The label is the thing I named a book after, and it still bounces off if I lead with it. What actually moves them is walking through the specific meeting where being the smartest in the room cost me the room. The one where I answered the question correctly, watched a more junior engineer visibly stop talking for the rest of the quarter, and later learned we had shipped a decision I would have caught if that engineer had felt safe enough to push back. The rule they need to adopt is "my job is not to be right in the meeting, it is to be the reason the right thing gets said in the meeting." But they only adopt it after they have lived, secondhand, through the meeting where I learned it.

The same is true when I ask a team to do something uncomfortable, the kind of ask I write about in Stepping Into Your Power. Delegate a decision they have always personally owned. Kill a project that has their name on it. Say the honest sentence in a client review instead of the diplomatic one. The instruction alone gets nodded at and quietly ignored. The scene where I learned the cost of not doing it gets acted on.

Half the essays I have already written on this site are epiphany bridges in essay form. Fight For Your Limitations And You Get To Keep Them is the Ironman mile-eighteen moment. The Circumstance Will Lie To You is the I-70 blowout. Principle Over Peace is the exit-negotiation moment. In each one the pattern is identical. Old belief. Named scene. New belief. What to do on Tuesday. Brunson did not invent that shape; he named it. Once you can see it, you cannot unsee it in any communication that actually moved you.

How To Build Your Own

A short field guide, from running this at Blue Goat and inside my coaching and keynote work.

One, find the moment before you find the message. The mistake most founders make is starting from the pitch and reverse-engineering a story to fit it. Start from a specific scene where your own belief changed, and let the pitch fall out of it. If you cannot name a room, a person, and a sentence that was said, you do not have a bridge yet. You have a claim.

Two, tell the old belief out loud, in the buyer's or the team member's language, not yours. "Cybersecurity is compliance you bolt on before submission" is their sentence. If you translate it into your language first, they do not recognize themselves in it, and the scene has nothing to displace.

Three, keep the scene sensory and short. Room, people, one specific line that was said, one specific consequence. Not a case study. A scene. The listener's brain has to be in the room with you, not evaluating a slide.

Four, name the new belief in one sentence, and only then earn the right to say the number, the credential, or the offer. The 250+ submissions line only lands because it arrives after the belief has already moved. Said first, it is a brag. Said last, it is proof.

Five, use it in reverse for post-mortems. When something went sideways, do not open the debrief with the lesson. Open with the scene, in enough detail that the team feels the pivot the way you felt it. The lesson lands on its own after that, and the team owns it, instead of writing it down and forgetting it.

The Smallest True Sentence I Can Give You

You do not have a messaging problem. You have a scene problem. The reason your buyers are not moving and your team is not adopting the behavior you keep asking for is not that they do not understand your framework. It is that they have never been walked through the moment you understood it. Give them the moment, and the framework installs itself.

That is the whole trick, in cybersecurity, in leadership, and in the essays that get read to the end. Do not hand people the conclusion. Take them back to the exact place you had to stand before the conclusion was obvious, and let them stand there with you.

Start This Week

Do this in the next thirty minutes, before you close the tab.

One, pick one offer you are currently pitching, or one behavior you are currently asking a team to adopt. Write, in one sentence, the old belief the audience is walking in with, in their language.

Two, name the specific moment your own belief on that topic changed. Room, people, the one line that was said, the consequence. If you cannot find one, you do not yet believe the thing you are selling or teaching hard enough to move anyone else.

Three, write the new belief in one sentence, then, and only then, add the number, the offer, or the instruction. That is your bridge. Say it out loud twice. The next time you get the chance, lead with it and see what stops feeling like a pitch.