Working Draft · Manager Capability Training

Sales Process Foundation

The Syntax of the Sale

This is the operating standard behind the Cam Clark Automotive Group sales process. The purpose is not to create a script. The purpose is to define the expected order of operations so a manager can teach it, inspect where the customer interaction broke down, and coach the next action. The five cards are the detailed lessons; this page is the operating system they sit inside.

SequenceIntelRapportPresentationClose

The Operating System

Start with the order of operations

Every customer is different, but every interaction needs the same expected order of operations. When the order is consistent, the manager can teach it, inspect it, and coach exactly where it broke down. This is the sequence the salesperson moves through with the customer.

1Get control

Set the agenda and create logical certainty in the first 11 seconds, so the customer knows what to expect.

2Gather effective intel

Capture the reason for shopping, expectations, must-have options, and where else the customer has looked.

3Establish rapport & transition

Show the customer they were heard and understood, then guide them into vehicle selection.

4Pitch, present, create certainty

Connect what the vehicle is, what it does, and the impact on the customer; build certainty on the three 10s.

5Close & loop back

Offer a simple next step, diagnose the real objection, and loop back to the concern without losing control.

Then close again

Once the concern is answered, return to the close. The loop is part of the process, not a detour from it.

Why an order of operations The checklist does not replace judgment — it protects consistency. When every interaction follows the same sequence, a manager can inspect any deal and name the stage where it worked or broke down.

The Capability Arc

What the five cards teach

The five cards map directly to the sequence. Each one is a manager-capability lesson for one stage of the customer interaction — what good looks like, and how to inspect it.

Card 1 · Sequence

The Syntax of the Sale. Teaches the expected order of operations and gives managers a common way to inspect where the process worked or broke down.

Card 2 · Intel

Gather Effective Intel. Teaches using the guest sheet to capture the customer's reason, expectations, must-have needs, and shopping context.

Card 3 · Rapport

Establish Rapport and Transition. Teaches moving from discovery into vehicle selection while the customer feels heard, understood, and guided.

Card 4 · Presentation

Pitch, Present, and Create Certainty. Teaches connecting what the vehicle is, what it does, and the impact — and building certainty before payment.

Card 5 · Close

Close and Loop Back. Teaches the simple close, diagnosing the real objection, and looping back to the concern without losing control.

Stage Inspection

What the manager inspects at each stage

A manager does not inspect whether the salesperson was friendly. The manager inspects whether each stage of the order of operations actually happened. Pick a stage to see the questions.

Get control — the first 11 seconds

  • Did the salesperson set an agenda so the customer knew what to expect?
  • Was logical certainty created early, before any pressure?
  • Did the customer feel professionally guided rather than sold?
ORDERof operations

Operating Truth

You can't coach what has no order of operations.

When every interaction follows the same sequence, a broken deal becomes a coachable moment — the manager can name the stage it broke at. Without an order of operations, there is nothing to inspect and nothing to coach.

Operating Checklist

The sales process inspection checklist

Use this to inspect any deal or coach a one-on-one. It is the operating standard expressed as a checklist — the same sequence, every time.

  • Agenda set and logical certainty created in the first 11 seconds.
  • Reason for shopping is documented.
  • Expectations and must-have options are captured.
  • Shopping context — other stores and vehicles — is known.
  • Rapport shown: the customer felt heard and understood.
  • Clean transition from discovery into vehicle selection.
  • Value connected: what it is, what it does, and the impact.
  • Certainty built on the three 10s before payment.
  • A simple next step or close was attempted.
  • The real objection was diagnosed — not accepted as “think about it.”
  • Looped back to the concern without losing control, then closed again.

Diagnosis

Where the process breaks down

Most lost deals break at a predictable stage. Because there is an order of operations, the manager can name the break point and coach it.

No agenda

The salesperson never set expectations, so the customer stayed in control of the interaction.

Weak intel

No reason, expectations, or must-haves were captured, so the pitch is generic and cannot tie to the customer.

Skipped rapport

The salesperson jumped to the vehicle before the customer felt heard, so the transition felt abrupt.

Jumped to price

Payment was presented before value and impact were connected, so there is no certainty to support the number.

No certainty

Features were listed, but the three 10s were never built, so the customer is not confident enough to move.

Took “think about it”

A stall was accepted instead of diagnosing the real objection and looping back to it.

The teaching point When the deal breaks, the manager should be able to name the stage it broke at — because there was an order of operations to inspect.

Coaching Language

Manager Word Track

Practical language a manager can use to inspect a deal and coach the next one — short, direct, and operator-led.

“When I inspect a deal, I am not asking whether the salesperson was friendly. I am asking whether they followed the order of operations.

  • Did they get control and set the agenda in the first 11 seconds?
  • Did they gather real intel — reason, expectations, must-haves, shopping context?
  • Did they show the customer they were heard before transitioning?
  • Did they connect value and impact, not just features?
  • Did they build certainty on the three 10s?
  • Did they ask for a simple next step?
  • When the customer hesitated, did they diagnose the real objection and loop back?

If I can name the stage where it broke, I can coach it. If there was no order of operations, there is nothing to inspect.”

What should trigger coaching

  • No agenda was set in the opening.
  • Intel is missing, so the pitch is generic.
  • The salesperson transitioned before establishing rapport.
  • Payment was presented before value and impact.
  • Certainty was never built on the three 10s.
  • No close was attempted.
  • “Think about it” was accepted without diagnosis.
  • The manager cannot tell which stage broke down.

Begin with Card 1. The first card defines the overall sequence. The remaining cards explain how the salesperson moves through the customer interaction and how the manager inspects the work.

Start Card 1

Training Cards

Training cards behind this tool

These five cards are the manager-capability lessons behind the Sales Process Foundation. Each one teaches and inspects one stage of the customer interaction.

1Sequence

The Syntax of the Sale

Teach the expected order of operations for every customer interaction and give managers a common way to inspect where the process worked or broke down.

Open Card 1
2Intel

Gather Effective Intel

Use the guest sheet to understand the customer's reason, expectations, must-have needs, shopping context, and next step.

Open Card 2
3Rapport

Establish Rapport and Transition

Move from discovery into vehicle selection while showing the customer they were heard, understood, and professionally guided.

Open Card 3
4Presentation

Pitch, Present, and Create Certainty

Connect what the vehicle or option is, what it does, and the impact it has on the customer.

Open Card 4
5Close

Close and Loop Back

Make the next step simple, identify the real objection, and loop back to the concern without losing control of the process.

Open Card 5

Finished previewing? Return to Project Update 003 to upload related source material, provide feedback, or confirm no changes.

Return to Project Update 003