Vendor-Agnostic Doesn't Mean Opinion-Free: Rethinking the Presales Security Architect Role

Sample post included to show the format and tone of this section. Replace it with your own writing whenever you’re ready — see the README for how new posts get added.

Most of my career has been spent in the room where a client’s requirements meet a vendor’s roadmap, and a design has to come out the other side that actually works. Twelve years of that teaches you a specific kind of discipline: stay vendor-agnostic, present options fairly, let the client decide. It’s the right instinct in a room full of competing OEMs. It’s also, if you’re not careful, a habit that quietly costs clients good outcomes.

The neutrality trap

“Vendor-agnostic” gets taught as a synonym for “opinion-free.” It shouldn’t be. A presales security architect who has sat through forty Zero Trust RFPs knows things a first-time buyer doesn’t: which SASE platforms actually enforce policy at the edge versus backhaul it, which IAM integrations look identical on a slide and behave completely differently under a real identity provider migration, which “unified” security fabrics still ship as three separate consoles two years after the acquisition closed.

Withholding that judgment in the name of neutrality isn’t professionalism — it’s outsourcing the hard part of the job back to the client. Neutrality should mean I’ll show you the honest tradeoffs across options, not I have no view on which of these will actually hold up in your environment.

Where the line actually belongs

The distinction that’s held up for me:

• Neutral on the deal. I’m not steering a client toward a platform because of margin, relationship, or what’s easiest for my own team to deliver. That kind of neutrality is table stakes and clients can smell its absence from across the table.
• Opinionated on the architecture. Once we’re past “which vendor,” the actual design — segmentation boundaries, where policy enforcement lives, how identity and network security actually integrate versus just co-exist — deserves a real recommendation, not a menu.

Clients aren’t paying (directly, in a services engagement, or indirectly, in the time they spend in your PoC) for a feature comparison spreadsheet. They can build one of those themselves from public data sheets. What they’re actually buying from a solutions architect is judgment under uncertainty — and judgment requires having, and stating, an opinion.

What this looks like in an actual RFP

On a recent large retail SD-WAN and security transformation, the client’s draft RFP asked for “vendor recommendations across three shortlisted SASE platforms” with no stated preference. The easy answer is a feature matrix with checkmarks. The useful answer was different: two of the three platforms met the stated requirements on paper, but only one handled the client’s actual traffic pattern — a high volume of east-west traffic between retail locations and a central distribution hub — without adding a second hop through cloud-delivered inspection that would have added latency the client hadn’t priced into their SLA conversations.

That’s not a neutral finding you can hedge into a checkbox. It has to be said plainly, with the reasoning shown, so the client can push back on the reasoning if they disagree — which is a very different interaction than pushing back on an unexplained preference.

The takeaway

If you’re early in a presales or solutions architecture career, the instinct to stay neutral is worth having — it protects you from bias and keeps trust with every OEM in the room. Just don’t let it become an excuse to withhold the one thing the client actually came to you for: a considered, defensible opinion about what will work in their environment specifically, stated clearly enough that they can evaluate your reasoning, not just your recommendation.

That’s the difference between a vendor liaison and an architect. It’s also, not coincidentally, the skill that scales into independent consulting — where there’s no vendor quota to hit and the client is paying you specifically for the opinion.