The AE Mindset for Complex Technology Sales

• A signed deal is an outcome to inspect; discovery quality, buyer understanding and agreed follow-up are behaviors an AE can improve.
• In a complex deal, a strong demo follows the buyer’s stated problem and gives a champion a clear account to carry into other rooms.
• Use the book’s Five-Question Audio Debrief to find one observable moment to practice, while tracking conversion and customer feedback too.
• Layer 1 Internal State helps the AE notice urgency and recover their attention; it does not control procurement or the buyer’s decision.

A technology account executive can have a careful discovery call on Tuesday and hear on Friday that the evaluation has paused. A second deal may advance after a mediocre demo because the buyer already had a mandate. If the AE treats each outcome as a verdict on their worth, the next call inherits the last deal’s emotional residue. Layer 1 of VIVID, Internal State, asks a more useful question: what is happening to my attention right now, and what can I do in this conversation?

That does not mean ignoring revenue, forecast accuracy or customer outcomes. Those measures reveal whether the work is effective. It means also examining the actions that produced the experience: the pre-call audit, the quality of diagnosis, which problem the demo addressed, whether a champion can explain the case, and whether the next step was mutually agreed.

Separate the score from the craft

Suppose an AE has three late-stage opportunities. One procurement review slips. One buyer chooses another vendor. One signs. The result column matters, but it cannot tell the AE what to practice. A craft review asks: Did I hear the actual decision criteria? Did I learn who else must agree? Did the demo prove a relevant workflow, or simply tour features? Did I record an open concern in the buyer’s words? “Send more follow-ups” is too vague to learn from.

A practical weekly scorecard can contain two lanes. Outcome signals include progression, conversion, retention or other measures the organization uses. Process evidence includes the proportion of demos tied to a stated buyer task, whether next steps had an owner and date, and whether champions received usable decision material. A high activity count with poor buyer experience is a warning, not a win. A good call that did not close is still worth studying.

Regain your state before the call

Before a meeting, name the pressure without handing it the steering wheel: “I want this deal because the quarter is tight.” Then do the book’s sixty-second reset: breathe in for five counts through the nose and out for seven through the mouth. Check the pre-call facts, the buyer’s stated purpose and the one uncertainty you need to explore. The goal is presence, not a claim that breathing changes the buyer’s budget.

During the call, use Dual Awareness from Layer 7, The Observer: notice your own state, the buyer’s response, and where you are in the conversation. If you catch yourself rushing to screen share, pause and recap: “I may be moving ahead of the problem. You said the handoff between security review and rollout is where time is lost. Is that still the part to examine?” That correction is observable and teachable.

From discovery to a useful demo

In this fictional example, an AE sells workflow software to a team evaluating its approvals process. The conversation is illustrative; it predicts no deal result.

AE: “When an approval stalls, where do you first see it?”
Buyer: “Usually in the finance queue, but the real delay is finding who changed the request.”
AE: “So the issue is less approval speed itself and more tracing changes. What does a missed change cause downstream?”
Buyer: “My team rebuilds the audit trail by hand.”
AE: “For the demo, would it be more useful to test change history or the approval dashboard first?”
Buyer: “Change history. Our security lead will ask about it too.”

The AE has used a Clarifying question and an OR question from the Diagnostic Engine. The answer changes the demo order. It also exposes a second stakeholder. The AE should verify product behavior before promising that the software solves the audit problem. If the capability only partly fits, say so and document the unresolved point.

After the demo, ask the buyer to restate what they would need to show the security lead. A champion can carry a concise summary: their current workflow, what was demonstrated, evidence still needed, and the trade-off to decide. A polished feature deck is not a substitute for that decision material.

Use the Five-Question Audio Debrief

After a consequential conversation, answer the book’s five questions aloud or in written notes according to company policy. Do not record a customer without the permissions your organization requires.

1. What was the outcome?
2. What did I do well, specifically, and at what moment?
3. What could I have done differently, and at what moment?
4. If it did not move forward, what was the objection, what did I say, what could I have said instead, and why?
5. What did I learn that applies to the next conversation?

Keep the answers concrete. “I stayed curious” is less useful than “At minute 12, I asked what ‘audit ready’ meant and learned the security lead needed change history.” If the next call has the same pattern, practice that question. If several deals stall at procurement, investigate the buying process and stakeholder map rather than assuming the problem is your attitude.

A repeatable AE routine

At the start of the week, review pipeline reality with your team and choose one conversation skill to improve. Before each call, do a short pre-call audit and state the buyer’s purpose in one sentence. During discovery, let the buyer’s answer determine what the demo should prove. Afterward, use the debrief and send only the follow-up that was agreed. At the next review, compare both process evidence and actual outcomes.

The Seller Type Quiz can prompt reflection on habits; its archetypes are a website instrument, not buyer types from the book and not a diagnosis of why a deal was lost. For deeper review, the seven VIVID layers give a better map: Internal State, First Contact, Diagnostic Engine, VIVID Architecture, Guided Persuasion, Objection Dissolution and The Observer.

Common Questions

Should an AE celebrate activity or results?

Recognize deliberate work and inspect results. A booked meeting count alone says little; a discovery that clarifies criteria and a demo that tests a stated workflow provide stronger learning evidence.

What if a good conversation still stalls?

Use the debrief, then check external causes such as budget, procurement and stakeholder agreement. A stalled opportunity is information, not proof that the AE’s mindset caused it.

How is this different from an SDR activity target?

The AE reviews the quality of diagnosis, demonstration and multi-stakeholder decision support in addition to activity volume and business outcomes.

Put it into practice

Choose a conversation to practise.

Explore the lessons and practice for your selling environment, or try a conversation first.

Practise a reporting request that reveals an approval-rule problem and changes the demonstration.

VIVID Selling for Tech Sales →Try: The buyer asked for reporting. What do you show? →