Pre-Sales: Zero to Hero — Earned Technical Trust — the Asset AI Can't Commoditise
MOD 20+

Earned Technical Trust — the Asset AI Can't Commoditise

Michael Gutierrez, More Than a Demo: the demo is the most visible thing an SE does, which is exactly why the profession keeps mistaking it for the job.

Strategy vs. tacticsThis sheet is the argument for why AI changes what the role is worth. For the week‑to‑week toolkit — where it actually saves time, and where it doesn't — see Mod 08+.

Every function whose value depended on being the only person in the room who could answer a technical question is watching that scarcity erode, pre‑sales included. A buyer showing up to a first call having already asked an AI assistant the same questions they'd once have saved for a Sales Engineer is no longer a hypothetical — it's routine. Michael Gutierrez — Senior Director of Solutions Consulting at GoTo, and the author of More Than a Demo: The Sales Engineer's Guide to the Next Era of Technical Selling — argues that as AI commoditises product knowledge, the asset that decides deals stops being what you know and becomes earned technical trust: credibility built deliberately across an engagement, not performed in the ninety minutes of the demo itself.

The demo is the most visible thing we do.Michael Gutierrez, "Earned Technical Trust," sales‑engineering.org

Earned technical trust, in three phases

Gutierrez's own published framework — not the book itself, which this manual hasn't read, but his companion article for NAASE — breaks the discipline into three phases, each with its own behaviour to get right:

Earned Technical TrustGutierrez, sales‑engineering.org, 2026
Before — the discovery‑based foundation Trust starts forming before the call does: real research into the customer's pain and their competitive landscape, then an opening that reflects their own priorities back to them rather than walking straight into an agenda. A demo that opens with the customer's own words proves you were listening before you prove anything about the product. During — honesty under pressure This is where most of the trust is actually won or lost, and it comes down to three behaviours: naming a knowledge gap plainly instead of guessing — a provisional answer, an honest confidence level, and a specific commitment to a verified answer by a stated time; volunteering a real product limitation before the customer finds it themselves; and translating between stakeholder levels in the room rather than giving everyone the same answer at the same altitude. Gutierrez's own example is a competitive deal won by candidly conceding a rival's genuine strength — the concession surfaced what the customer actually cared about, which the polished pitch hadn't. After — a structured proof of concept Written, testable success criteria agreed before the trial starts. One question asked explicitly once they're met: "if the trial proves these things, is there anything else standing between us?" — surfacing the next objection while there's still time to work it, rather than at the readout. A defined window, two to three weeks, not left open‑ended. A named owner on the customer side, not a distribution list.

Notice how closely this maps onto ground this manual already covers — the situation‑slide discipline in Module 09, the S9 honesty‑over‑a‑filled‑template rule this manual borrows for its own tone, and the written success‑criteria discipline in Module 11 — restated for an era where a buyer can no longer be impressed by information alone, because they can get the information from a model before you've said a word.

Trust compounds

Gutierrez's closing point is the one worth carrying past this sheet: technical trust built well on one deal doesn't reset at signature. It carries into the renewal, the expansion, and the referral the customer makes to a peer without being asked — which is the same economics as wallet share in MSP 02, arrived at from a different direction. A pre‑sales person who treats every deal as a standalone trust‑building exercise is running the expensive version of a discipline that gets cheaper every time it compounds.

What the book covers beyond this

Per its own listing, More Than a Demo goes further than the trust framework above — into why the demo alone is no longer enough and what replaces it, how to build and lead a solutions‑consulting organisation, the competencies separating a good SE from an elite one, how AI is reshaping discovery, demos and technical validation specifically, career paths for an SE who wants to grow past individual contribution, and what a manager has to do differently to develop technically‑enabled sellers rather than demo operators.

Who it's actually written for

  • Solutions consultants and sales engineers planning their next move — which, per Module 21, is exactly the seat you're aiming at
  • SC and pre‑sales leaders rethinking team structure — the Practice Lead / Director fork from Module 02
  • Revenue leaders deciding how AI changes go‑to‑market — the audience for the market‑voice work above
  • Anyone whose job sits at the intersection of technical depth and the deal — which is this manual's definition of the role, restated
What's the book's and what isn'tThe three‑phase framework, the competitive‑concession example and the closing "trust compounds" line above are Gutierrez's own published argument, paraphrased and cited from his NAASE article — not this manual inventing a framework in his name. The "what the book covers beyond this" list is drawn from the book's own public description, not from having read the finished chapters. Read More Than a Demo directly for the full career‑path and org‑design material before using it as your own in an interview.
SourcesMichael Gutierrez, "Earned Technical Trust: What Great SEs Do Before, During, and After the Demo", sales‑engineering.org / NAASE (2026); and More Than a Demo: The Sales Engineer's Guide to the Next Era of Technical Selling (Amazon, Kindle & NAASE reading list). Flagged here because the shift it describes is already visible in the field this manual was written for, and because Module 20's market‑voice argument and Module 02's leadership fork both get sharper once AI is priced into them.