Skip to content
VIVIDSELLING
OS
Menu

Field notesFramework · Seven layers

The VIVID 7-Layer Selling Framework: From First Contact to Deliberate Practice

Learn the seven VIVID layers through a worked sales conversation, industry examples, and practical tools for choosing what to improve next.

Start reading
Key points
  • VIVID connects Internal State, First Contact, Diagnostic Engine, VIVID Architecture, Guided Persuasion, Objection Dissolution, and The Observer.
  • The five conversation phases and five presentation movements do different jobs inside Layer 4.
  • Use a specific moment from a real conversation to choose what to practise next.

A buyer says, “Send me the proposal.” You send it. Then nothing. The next call is quieter, the follow-up gets shorter, and eventually you start looking for a better closing line.

The closing line may deserve attention. But it is worth replaying the conversation before changing it. Did the buyer describe a result they wanted? Did you understand why their current approach was falling short? Did your presentation answer that problem, or did it explain everything your product does?

VIVID connects those choices into seven layers. It gives you a way to prepare, lead, and review a sales conversation—and a way to decide what to practise when “get better at sales” is too broad to be useful.

The seven layers, and the work each one does

The VIVID Selling Operating System
  1. Internal StateBring curiosity, conviction, and the willingness to walk away.
  2. First ContactMake the opening relevant enough to earn the next exchange.
  3. Diagnostic EngineUnderstand the buyer’s situation, reasoning, and decision.
  4. VIVID ArchitectureConnect the desired future, present gap, impact, and choice.
  5. Guided PersuasionHelp the buyer examine what matters through the appropriate instruments and mode.
  6. Objection DissolutionAddress the resistance where it lives.
  7. The ObserverNotice your choices, review them, and turn the lesson into practice.

These are layers of a selling system, not seven boxes to recite on every call. Internal State and The Observer operate throughout. The conversation has its own five-phase architecture inside Layer 4.

Layer 1: Internal State

Start with the position you are selling from. If this deal has to close, you may explain too much, discount too early, or keep talking after a buyer has given you something worth exploring. VIVID calls that pressure Commission Breath. Its opposite is the book’s Ferrari Dealership Energy: calm, unhurried, and able to accept that a particular buyer may not be a fit.

The Revealing Paradigm changes the seller’s job from arguing for a conclusion to helping the buyer examine their own situation. The Own Principle asks who carries the reasoning. Can the buyer explain why something needs to change, or are they agreeing with a case you have made for them?

Practise: before a call, name the decision you are helping the buyer make and one circumstance in which you would recommend stopping. This makes willingness to walk away concrete.

Layer 2: First Contact

An opening has a limited job: establish relevance and make the next exchange possible. VIVID teaches Observation, Peer, and Confusion opener architectures, followed by a bridge into a useful conversation. A long explanation of your company can answer a question the prospect has not asked.

An observation-led opener might begin with a specific, accurate change: “I saw you’re adding a second service team. How are you handling handoffs between the two?” A peer opener needs a real shared context. A Confusion opener puts the uncertainty on your understanding; it is not a reason to pretend you know the person.

Practise: write the opening, the reason it is relevant to this person, and one question you can ask if they engage. Read it aloud. Remove the company history that does not help the next exchange.

Layer 3: Diagnostic Engine

“We need better reporting” is a starting point. It does not yet explain what the buyer wants to see, why it matters, or what they believe a report will change. The Diagnostic Engine gives you seven Strategic Question Types: Easy, Tough, Direct, OR, Clarifying, Loose-Thread Pulls, and Confused-Skeptic.

The types do different work. “What do you mean by better?” is Clarifying. Returning to “we always find out too late” is a Loose-Thread Pull. A Confused-Skeptic question places the doubt on your understanding so the buyer can explain their logic. Ask one question, listen, and choose the next question from the answer.

The four buyer-psychology layers—Surface Criteria, Mechanism Belief, Felt Outcome, and Identity—help you distinguish a request from the reasoning and personal meaning behind it. They are separate from the seven numbered VIVID layers. Buyer types and multi-stakeholder dynamics add another practical question: how does this person decide, and who else participates?

Layer 4: VIVID Architecture

The five conversation phases are Vision, Identify, Validate, Impact, and Decision. Vision establishes the future the buyer wants. Identify explores the present gap. Validate works with the experience behind resistance. Impact makes the consequences concrete in the buyer’s context. Decision connects the work to a choice.

The presentation has a different structure: Framing, Proof, Peak, Inevitability, and Decision. These five movements help you build the presentation around the conversation you have already had. “Inevitability” is the book’s name for bringing the case together; it does not mean a buyer must purchase. Open assumptions and genuine constraints still belong in the decision.

Practise: take a proposal you recently sent. Under each recommendation, write the buyer statement it answers. If you cannot connect a section to the conversation, revisit the diagnosis or remove the unnecessary section.

Layer 5: Guided Persuasion

Guided Persuasion is more specific than presenting benefits. Its instruments include the Identity Gap, Permission Architecture, OR Questions, Closing Off Before Opening Up, and the Recap Instrument. They help the buyer examine a tension, compare directions, or hear the significance of what they have already said.

Context changes how that work happens. The book names five modes: Emotional, Demonstration, Consultative, Product/Vision, and Proxy. A coaching prospect experiencing a bounded demonstration is in a different conversation from a software buyer evaluating technical fit or a contact preparing to speak to an absent decision-maker.

Practise: choose one instrument for a real point of uncertainty. Write the buyer’s words, the question you would ask, and what different answers would change. If every answer leads to the same pitch, the exercise needs more work.

Layer 6: Objection Dissolution

The same phrase can point to different concerns. “It’s expensive” may be a budget limit, uncertainty about the mechanism, a timing trade-off, or a decision standard the buyer wants to protect. Answering each with the same rebuttal makes the response easy to memorise and easy to misapply.

VIVID’s Five-Step Dissolution Flow is Absorb, Diagnose, Validate, Dissolve, Confirm. The four categories are Money, Trust, Timing, and Identity. The book maps these to Surface Criteria, Mechanism Belief, Felt Outcome, and Identity respectively. Use the map to choose a question and response, then check the buyer’s answer.

COR—Criteria-Outcome Realignment—belongs to Identity resistance. It explores a possible conflict between a stated outcome and a decision criterion. The Non-Negotiable Checkpoint and permission to explore matter: a genuine boundary is not an obstacle to talk someone out of. An absent partner calls for the Absent-Party Protocol, not a fifth objection category or a way around the partner.

Layer 7: The Observer

The Observer is how you keep using the system while a real conversation is happening. Dual Awareness means participating while also noticing your state, the buyer’s state, and your structural position in VIVID. When you lose the thread, the recovery sequence is pause, recap, redirect.

After the call, the Five-Question Audio Debrief turns a general impression into a moment you can practise. What happened? What did you do well? What could you have done differently? If the call did not move, what was the objection and your response? What applies to the next conversation?

The recursive loop—Observe, Analyze, Prioritize, Practice, Observe again—is the maintenance habit inside The Observer. It is not a replacement name for Layer 7.

One conversation, several layers at work

Fictional teaching example: a technology buyer asks for a dashboard. The seller has prepared a broad product demonstration.

Buyer: “We need one place to see what is still open.”

Seller: “When something stays open, what do you have to do to find out why?”

Buyer: “Ask around. The case is visible, but nobody knows who has the next action.”

Seller: “You said nobody knows who has the next action. What happens when the customer calls again?”

Buyer: “We start over. I’m responsible for the service standard, and it looks like we haven’t listened.”

Seller: “What would a dependable handoff look like from your side?”

Buyer: “One person accepts the next action, and everyone can see that. Another dashboard on its own won’t fix it.”

The seller resisted the Pitch Reflex, used a Loose-Thread Pull, explored the Felt Outcome and a responsibility the buyer expressed, and helped the buyer reach a conclusion. Now the presentation has a job: demonstrate the relevant handoff, including any gap in assignment or acceptance. It no longer needs to tour every dashboard.

If the buyer then says, “We tried a new system last year and people still didn’t use it,” the next move is not more dashboard proof. There is a Mechanism Belief to explore: what caused the previous approach to fail, and what would have to be different? That answer shapes both the recommendation and any unresolved implementation work.

The example shows why the layers connect. It also gives you observable practice targets: the question asked, the buyer’s answer, the presentation chosen, and the unresolved concern.

How the same method changes across industries

  • A coach: a prospect requests a productivity plan. Explore the week they want, the interruptions they describe, and what they have tried before offering a bounded demonstration of the work.
  • A real estate agent: a homeowner asks about commission. Understand the sale they want, their timing, and how they intend to compare representation before explaining your services and fee.
  • An in-home seller: the homeowner wants to speak with a spouse. Clarify the shared decision and prepare a useful conversation with both people instead of treating the absent person as a hurdle.
  • A sales manager: “Ask better questions” becomes a specific coaching task: return to one meaningful phrase, ask a Loose-Thread Pull, and review how the answer changed the next move.

The framework stays recognisable. The example, evidence, decision process, and practice task change with the work.

Choose a practice focus you can actually use

Review one conversation that progressed and one that stalled. Find a moment you can point to: the opening became a monologue, a meaningful phrase went unexplored, the presentation answered a different problem, or the next step remained vague. Choose the layer that helps you work on that moment.

Then write three lines: what the buyer said, what you did, and what you would try next time. Rehearse the alternative aloud. On a later call, notice whether the relevant opportunity appeared and what happened when you used it. A lost deal alone cannot tell you which layer needs work.

Tools for taking the framework into a call

Start with your next conversation

The short quiz offers a self-reported starting point. The full 35-question quiz covers all seven layers. Neither can listen to a call for you; compare the result with your own examples.

If you want the lessons, industry scenarios, labs, assessments, and tools together, choose your industry course. You can read the curriculum and a worked example before enrolling. The book is still in progress; the available courses are a separate way to study and practise the method now.

Put it into practice

Choose a conversation to practise.

Explore the framework and put this idea to work on your next call.