Skip to content
VIVIDSELLING
OS
Menu

VIVID / Tech Sales / Free practice

The buyer asked for reporting. What do you show?

Follow the buyer’s answers to a focused demonstration. Leave with a proof plan you can adapt for your next demo.

Try the conversationSee the course and price →

Two or three decisions. No account needed. Leave with a conversation card you can edit and keep.

“We need better reporting. I don’t want to be the escalation desk anymore.”

Fictional teaching example. People, dialogue and product details are invented for practice.

Your role: You sell an operations workflow platform.

What you know going in
  • The fictional platform supports configured routing, shared rule visibility and an inspectable decision history.
  • The buyer supplies approval policy; software does not decide what authority staff should have.

Try a decision

What would you say next?

Practice stays in this browser when local saving is available. Use fictional details and download a copy to keep elsewhere.

Follow the complete worked conversation below, or enable JavaScript to make choices and receive feedback.

Inspect the method

A worked conversation

  1. Buyer

    We need better reporting. I don’t want to be the escalation desk anymore.
  2. Seller

    When a manager sees an exception in today’s report, what happens next?

    Direct: establish what happens after the report makes an exception visible.

  3. Buyer

    They can see the owner. They ask me what they’re allowed to approve.
  4. Seller

    Which decisions can they make today, and where does that become unclear?

    Mechanism Belief: find how the buyer thinks operational change must happen.

  5. Buyer

    One-day delays are theirs; longer delays are mine. Teams interpret the rule differently.
  6. Seller

    And when that works consistently, what changes for you?
  7. Buyer

    I can trust them to run the day. I’m still accountable, but I stop checking everything.
  8. Seller

    So you want a consistent rule the team can use, with a history you can inspect. Would one routine exception and one escalation let you assess that—or is there another case we need?

    Felt Outcome and Identity came from the buyer. Recap ties them to inspectable proof, with room to correct.

  9. Buyer

    Those two. Include the operations lead; she owns the policy.
  10. Seller

    We can show routing and the history. Your team supplies the approval policy. Let’s use her rule so the example reflects the decision you actually need to make.

    Framing and Proof: the operational and personal threads determine the demonstration. This excerpt does not demonstrate the entire five-movement arc.

A fresh situation

Try the idea somewhere new

A different buyer asks for automated security approvals: “Reviews sit for days, and I’m tired of chasing people.” The system can route requests and record decisions; approval policy belongs to the buyer.

What is your next move?

Feedback on this authored task only; no certified skill score or business outcome inference.

Make it yours

Practise the words before the call

Say your next question aloud once. Listen for whether it invites the buyer to correct you. Then compare it with the worked example.

Read silently or say it aloud. This page does not record you. Keep real client names and private details out of your practice notes.

TECH SALES / PRACTICE DESK

Keep the work. Use it on your next call.

Prepare a focused brief, then return to it after the conversation. Keep the buyer’s words separate from your interpretation.

Draft context

Fictional practice is stored separately from any real-work draft.

Draft is blank. It will be saved in this browser as you type.

01 / LEARN

Follow the buyer’s reasoning.

Read the full exchange, then notice which detail changed what a useful demonstration should prove.

Read the worked conversation

02 / PREPARE

Build a discovery-to-demo brief.

Start with a blank draft. Use only information you are comfortable keeping in this browser.

Download a brief you can import into the course workspace. Keep drafts anonymous and review the file before sharing it.

Capture the relevant phrase as accurately as you can. Leave names and private customer details out.

What would the buyer need to decide or verify? Separate what they said from your current hypothesis.

Choose one bounded example tied to the confirmed criterion. State what it can and cannot show.

What product behavior, policy, participant or assumption must be checked before presenting it as fact?

What question or follow-up would let the buyer correct your understanding?

More ways to keep a copy
Inspect the fictional example before loading it

This is invented for teaching. The fictional example is only loaded into the fictional-practice draft.

Buyer’s words
“They can approve a one-day delay. Anything longer comes to me.”
Decision criterion
A consistent one-day approval rule across teams: routine decisions stay with managers; longer delays reach the leader. Confirm that this is the boundary the buyer wants to inspect.
Proof to show
Configure one ordinary exception and one escalation. Show the rule, routing and history. State that the team must supply its own approval policy.
Still to verify
The buyer supplies approval policy; software does not decide what authority staff should have.
Next check
“If we walk one exception through that rule, what would you need to inspect before judging whether this works?”
After-conversation review
Did the buyer confirm the rule and decide what evidence mattered?

03 / REVIEW

Review what the conversation established.

Use the context selector above to choose fictional practice or your real-work draft. Record the evidence you heard and one change to try next.

  1. Which buyer words or decision criterion did you confirm?
  2. What proof did you show, and what did it actually establish?
  3. What remains to verify with the buyer, product team or policy owner?
  4. What next check would invite correction or clarify the open point?

What did you learn about the buyer’s criterion, the proof shown and what remains open?

Open the brief fields

This desk does not send notes to analytics or place them in the URL. Avoid names, contact details and confidential customer information.

Continue learning

One conversation is a starting point.

Build the method around the conversations you actually handle: structured lessons, annotated examples, practice labs and resources you can return to before a call.

Turn the brief into a complete demo.

Study The Five-Movement Demo Architecture, build your outline and use the Diagnostic Demo Run Card. The course workspace adds a fuller conversation, a fresh case, authored feedback and an account-saved field kit.

Already enrolled? Open the matching lesson →

Open my saved Tech workspace →

Download your brief, then choose “Bring in your discovery-to-demo brief” in the course workspace. You review the fields before importing.

Explore VIVID Selling for Tech Sales

$297 once · 365 days of access · Written lessons and practice available now. Course videos are in preparation.