The Own Principle: Let Buyers Reach Their Own Conclusions

The Own Principle is about who carries the reasoning behind a decision. A seller can announce what a buyer needs and ask for agreement, or help the buyer examine the situation, connect it to what matters, and decide what follows. In the second conversation, the buyer is not repeating the seller’s conclusion; the buyer can explain the conclusion in their own words.

“If you say it, it’s sales talk; if they say it, it’s gospel” is a VIVID teaching shorthand. Its practical meaning is not that any answer is reliable because a buyer said it. It means the seller’s claim and the buyer’s considered conclusion have different roles. A seller’s explanation asks the buyer to trust the seller. A buyer’s own reasoning gives both people something concrete to examine, test, and correct.

Start with what the buyer actually knows

VIVID names four buyer-psychology layers: Surface Criteria, Mechanism Belief, Felt Outcome, and Identity. They help organize what a buyer has shared; they are not a numbered diagnostic ladder.

• Surface Criteria: what the buyer says they want, need, or will use to compare options.
• Mechanism Belief: the buyer’s cause-and-effect theory about how a solution or action could produce an outcome. A seller’s reading of that theory begins as a hypothesis.
• Felt Outcome: the experience or consequence the buyer says they want to change or preserve.
• Identity: how the buyer describes the standards, responsibilities, or kind of person they want to be. The buyer supplies this meaning; the seller does not assign it.

These distinctions matter because a request is often only the visible edge of a decision. “We need a dashboard” is a criterion. The buyer may believe the dashboard will expose a recurring handoff failure. The felt outcome may be confidence that customer commitments are being handled. Their identity may enter the conversation if they say, for example, “I’m accountable for making sure nobody gets left without an answer.” The seller should explore those connections when the buyer has made them meaningful, rather than decorating a pitch with guessed emotion.

The seven Strategic Question Types—Easy, Tough, Direct, OR, Clarifying, Loose-Thread Pulls, and Confused-Skeptic—give a seller different ways to explore the buyer’s account. They are choices, not a required sequence. A clarifying question can define “visibility”; a loose-thread pull can examine “left without an answer”; a direct question can test which unresolved issue matters most. The question should follow the conversation and make it easier for the buyer to think.

Let a hypothesis develop into the buyer’s conclusion

Fictional example: A software buyer asks for a dashboard that shows open service cases.

Buyer: “We need one place to see which cases are still open.”

Seller: “What happens today when a case stays open longer than expected?”

Buyer: “The case is visible. What we can’t see is whether anyone has taken responsibility for the next action. A customer calls again, and we start asking around.”

Seller: “So the issue is not simply finding the case. It’s knowing whether the next action has an owner. What does that create for your team?”

Buyer: “People interrupt each other to find out who is handling it. Sometimes we duplicate the work. I’m responsible for the service standard, and I don’t want customers to have to chase us.”

Seller: “You’re connecting the missing ownership to interruptions and repeat work, and you want the customer to get a dependable response. Have I got that right?”

Buyer: “Yes. I’d want to change how we assign the next action and make it clear when it has been accepted. A dashboard alone won’t do that.”

The buyer has now made several links that were absent from the initial request: the operational pattern, the effect on the team, the customer experience they want, and the change they believe is needed. The seller did not need to tell the buyer that interruptions are expensive or that the buyer cares about service. The buyer supplied those meanings and then drew a conclusion: assignment and acceptance of the next action matter more than a dashboard by itself.

The seller’s hypothesis still needs to be checked. “It sounds like the handoff is the decision point. Is that where you would focus first?” invites refinement; it does not press for a yes. If the buyer says the central issue is workload or authority instead, the diagnosis changes. The buyer’s correction is part of the method, not a detour from it.

Make the presentation follow the reasoning

Once the buyer identifies what needs to change, the presentation can answer that question. In this fictional case, the seller would first confirm the product’s actual workflow for assigning a next action, showing acceptance, and surfacing an unowned action. The relevant proof is the path that bears on the buyer’s conclusion—not every available dashboard view. The seller can ask the buyer to compare that workflow with the current handoff and point out where it fits or breaks.

If the product supports assignment but does not show acceptance, that distinction belongs in the presentation. It may mean the proposed workflow addresses only part of the buyer’s stated need. If a capability depends on configuration or another system, establish that before using it as proof. An accurate gap can be more useful than a polished demonstration that answers the wrong question.

As the presentation unfolds, return to the buyer’s own reasoning: “You said repeat work begins when the next action has no clear owner. Here is how this workflow records the owner. What would your team still need to see before you could evaluate it?” The buyer can then judge evidence against the change they described. The seller is not trying to produce a dramatic moment; the seller is helping the buyer examine whether the proposed mechanism matches the buyer’s mechanism belief.

Keep the decision with the buyer

Before recommending a next step, summarize the chain in plain language: what the buyer wants to change, what pattern they described, what outcome matters, and what they believe needs to happen. Ask what is missing. Then make the choice explicit: test a workflow, involve another stakeholder, investigate a dependency, compare another option, wait, or stop. A buyer may conclude the issue is not important enough to act on. That is still their conclusion.

The Own Principle is a discipline of listening and reasoning. It asks the seller to distinguish the buyer’s words from the seller’s interpretation, explore what the buyer has made relevant, and show evidence that answers the decision the buyer is actually considering. The quality of the conversation rests in that clarity; the decision itself remains the buyer’s.

Explore the VIVID course catalog to find the industry application that fits your work.

Put it into practice

Choose a conversation to practise.

Find a course for your selling environment and choose a useful skill to practise.

Browse VIVID courses →