AI Gave Your Buyers the Spec Sheet. Now What?

Last month one of my solutions engineers walked into a discovery call with a Fortune 500 CISO's team and they'd already built a comparison matrix — YubiKey 5 Series vs. Titan vs. token-based OTP vs. software authenticators. Not a rough sketch. A detailed, accurate breakdown covering FIDO2/WebAuthn support, NFC and USB-C form factors, FIPS 140-2 validation status, and per-unit pricing at scale. They'd used AI to do in a weekend what used to take weeks of vendor calls and SE deep-dives.

He called me after. His first thought: well, that part of my job just evaporated.

His second thought — and mine when he told me — was: good.

I lead a team of solutions engineers at Yubico, covering enterprise accounts across the U.S. And the shift I'm seeing isn't hypothetical anymore. AI is actively changing what it means to be technical in a sales cycle — and the SEs who recognize that are pulling ahead fast.

The Old Playbook Is Dead

For years, the SE's superpower was depth. You knew the YubiKey portfolio cold — which firmware supported which protocols, the differences between PIV and OpenPGP key management, when to recommend TOTP via Yubico Authenticator versus native FIDO2 passwordless. You could run a live WebAuthn registration in the room and watch the lightbulb go on. That aha moment used to close deals. I watched my team lean on it hard.

That model assumed an information asymmetry that no longer exists. Buyers show up to first meetings having already consumed our developer docs, read the FIDO2 spec, watched the YouTube walkthroughs on passkey implementation, and fed it all into an AI to generate a deployment comparison. Some of them have already enrolled test YubiKeys against their Azure AD or Okta tenant in a sandbox.

The demo isn't the aha moment anymore. It's a confirmation step. I started pushing my team on this over a year ago — stop leading with the tap-and-go demo, start leading with the deployment conversation. It took a few uncomfortable calls for it to land.

What Actually Matters Now

If the SE isn't the smartest person in the room about the product — and increasingly, they won't be — then what's the value?

Three things: synthesis, judgment, and trust.

Synthesis means connecting what the buyer already knows to what they haven't considered. It's not "let me show you how FIDO2 attestation works." It's "based on what you've told me about your hybrid Azure AD and on-prem PKI environment, your FedRAMP authorization timeline, and your 40,000-seat helpdesk ticket volume — here's what a realistic YubiKey deployment looks like, here's where credential lifecycle management gets complicated at your scale, and here's where most organizations your size hit friction during key provisioning." That's not something an AI summary gives you. That comes from doing hundreds of these rollouts across federal agencies, healthcare systems, and financial institutions.

Judgment is knowing what to recommend and what to steer away from. I've watched SEs lose credibility by pushing YubiHSM into an environment that didn't need on-prem key ceremony. And I've watched SEs win six-figure deals by saying "honestly, you don't need FIPS 140-3 validated keys for your entire workforce — here's why standard YubiKey 5 Series covers your compliance posture for PCI-DSS, and you reserve the FIPS keys for your privileged access tier." Buyers can smell a pitch. They're looking for someone who'll tell them the truth about their own environment.

Trust is the compound effect of the first two. When a technical buyer trusts the SE, the SE becomes their internal champion's secret weapon — the person who helps them write the business case, navigate procurement, and defend the architecture decision to their board. That hasn't changed. What's changed is how you earn it.

How Discovery Changes

The biggest practical shift is in discovery. Old-school discovery was about uncovering what the buyer didn't know about phishing-resistant MFA. New discovery is about understanding what the buyer already believes — and where those beliefs are wrong, incomplete, or based on outdated information.

A buyer comes in thinking YubiKeys are just U2F dongles for developers. They haven't modeled what credential lifecycle management looks like at 50,000 seats — spare key logistics, YubiEnterprise Delivery integration, self-service provisioning flows, key revocation when someone leaves, or how air-gapped environments change the entire enrollment architecture. They've read the spec. They haven't lived the rollout.

I've been coaching my team to treat discovery like a technical peer review. Assume the buyer has done their homework on protocols and form factors. Your job is to pressure-test their assumptions about deployment reality — identity provider integration depth, helpdesk operational load, compliance framework mapping across HIPAA and FedRAMP boundaries, and the gap between a 50-user pilot and enterprise-wide credential management via YubiEnterprise Subscription.

This requires SEs who can think on their feet, ask better questions, and have a genuine point of view about authentication architecture — not just product features.

What SEs Need to Develop

If I were hiring an SE today, here's what I'd weight more heavily than I did two years ago:

Consultative instinct. Can you walk into a room where the buyer already knows the YubiKey product line and still add value? Can you shift from presenter to advisor when they've already read the FIDO2 attestation docs?

Business acumen. The best SEs I work with can talk about risk quantification, compliance timelines, total cost of ownership across YubiEnterprise Subscription versus one-time purchase, and helpdesk deflection ROI as fluently as they talk about ECDSA curves and PIV slot assignments. AI handles the feature matrix. You handle the business case.

Storytelling with evidence. "We had a healthcare customer who tried to deploy FIDO2 across their clinical workstations without accounting for shared device workflows, and here's what happened" is worth more than any slide. Build a library of these — across federal, financial services, critical infrastructure. Real deployment scars are your differentiator.

AI fluency. Use the tools. Spin up test enrollment environments faster. Generate POC documentation and integration guides. Automate the repetitive stuff so you can spend more time on the high-judgment work — the architecture whiteboard sessions, the compliance mapping conversations, the "here's what the last three agencies your size got wrong" discussions that actually move deals.

The Punchline

The SEs who were already operating as trusted advisors on authentication architecture? AI just made them more powerful. They're using it to prep faster, build better deployment artifacts, and spend more time on the conversations that matter — the ones where a CISO needs to understand how phishing-resistant MFA actually lands across 80,000 employees in a hybrid environment.

The SEs who are still coasting on product knowledge and polished YubiKey tap-and-go demos? They're going to struggle. Not because AI replaced them — but because it gave their buyers the same knowledge, and now there's nothing left to differentiate.

The role isn't shrinking. It's elevating. But only for the people willing to elevate with it.