Sales · The Pitch Leak
How Do You Get Every Employee Quoting From the Same Rules?
In This Article
The calls are coming in. That part's working. But somewhere between "hello" and "book me in," some of them just... stop. No complaint, no objection you can point to. They said they'd call back.
You've probably already looked at the leads themselves — the source, the timing, the follow-up. Here's a question that's easy to skip: when someone other than you picks up the phone, do they ask the same questions you'd ask, quote the way you'd quote, and offer the same next step you'd offer? Or does the customer's experience quietly depend on which employee happened to answer?
By the end of this, you'll have a way to find out — and a shared checklist to write down the answer once, instead of guessing at it every time the phone rings.
To be clear up front: this isn't an assumption that your team is doing it wrong. It's a test. Your team may already agree. If their answers differ, compare the questions they asked, what the quote includes, and who can change the price — that gives you a specific rule to settle.
Is it a different job, or a different answer?
Two quotes for the same kind of job can legitimately come out different — different scope, different materials, different access, a rush versus a week out. That's not the leak. That's just pricing doing its job.
The leak is when the conditions are identical and the answer still isn't. One employee always asks a round of qualifying questions before quoting anything; another quotes a ballpark off the first sentence. One says a job needs an in-person look; another is comfortable pricing the exact same scope over the phone. One holds the line on price; another hears "can you do it for less?" and moves it without checking with anyone.
Here's a simple way to see which one you have. Write out one hypothetical inquiry — a specific, believable job, with every detail held constant: the scope, the address type, the timing, the customer's exact opening question. Hand that identical scenario to every employee who quotes jobs, separately, and have each of them write down what they'd ask, what they'd quote or defer, what they'd promise, and what they'd tell the customer happens next.
Then put the answers side by side. Where they match, you've just confirmed a rule your team already follows without needing it written down. Where they don't — that's the specific thing to settle. Not a personality difference to shrug off, and not a sign anyone's bad at their job. Just an unwritten decision that's been living in each person's head instead of on one page.
What belongs on the shared checklist
Once you can see where the answers diverge, the fix is one page: a shared checklist that gives every quoting decision one agreed rule instead of one memory per employee. Here's what belongs on it, and what "different answers" usually looks like before it exists.
| Decision | What each person says now | Agreed rule | Who handles exceptions |
|---|---|---|---|
| Questions before quoting | Some ask a round of qualifying questions; some quote off the first sentence | The exact questions that change eligibility or price — separate a genuinely unqualified caller from someone who's just early in the conversation, not every hesitant caller labeled a "tire kicker" | Owner / lead estimator |
| What can be priced by phone | One quotes anything by ear; another insists on seeing every job in person | Which scopes are simple enough to price by phone, which get a conditional estimate, which require an on-site look | Owner / lead estimator |
| What the price includes | Inclusions get mentioned inconsistently; exclusions surface later as surprises | What's always included, what's always excluded, and the conditions that change it — stated the same way every time | Owner |
| How the price is explained | Some lead with the number; some explain the outcome first | Outcome, then the reason why, then the price — see The Price Stall for the full sequence | Owner |
| Who can change the price | "Can you do it for less?" gets a different answer depending on who's on the phone | A stated discount authority and a clear point where it escalates instead of getting decided on the spot | Named escalation contact |
| What happens next | Some book on the spot; some say "they'll call back" and leave it there | The specific next step after a yes — booked, scheduled, or logged — and who's responsible for making sure it happens | Whoever answered |
Imagine a job priced at a 25% gross margin. A 12% discount removes 48% of the original gross profit if job costs stay unchanged. Source: GrowthLeaks internal arithmetic (12 ÷ 25 = 48%); this is an illustration, not a study. It's why "who can change the price" gets a named rule instead of a judgment call — see the discount cost calculator to run your own margin against it.
Notice what this checklist isn't. It's not a script, and it's not a claim that writing it down guarantees more booked jobs. It's a record of decisions your business is already making, written down once instead of re-decided differently by whoever answers. If a job needs a real price change once work has already started — not at the quote stage — that's a related but separate leak; see The Scope Creep Leak for that one.
Can staff use it without sounding scripted?
A checklist and a script solve two different problems, and mixing them up is where this kind of thing usually goes wrong. A script fixes the wording. A checklist fixes the facts and the boundaries underneath the wording — and those are what actually need to be identical, not the sentence structure.
The qualifying questions, the price boundaries, who's allowed to discount and how far, and what happens the moment someone says yes: those should come out the same no matter which employee is talking. How they're phrased in the moment doesn't have to match word for word. That's the difference between a rule and a script.
To test whether it's actually working, run the same hypothetical inquiry again a few weeks after the checklist exists. Have the same employees answer it independently, the same way as before. This time you're not looking for a perfect match — you're looking for whether the gaps you found the first time have closed. If someone answers in a way that doesn't fit the agreed rule, that's useful information, not a failure: maybe the rule needs an exception, maybe it needs to be clearer, maybe it needs a named person to decide the edge case. Update the checklist and move on.
How can you tell whether it helps?
The repeat exercise tells you whether your team's answers agree with each other. It doesn't by itself tell you whether more jobs get booked — that takes watching real inquiries, not just the hypothetical one.
Start recording comparable inquiries as they come in: what was asked, what was quoted, what the outcome was, and anything genuinely different about the job (scope, timing, whether it came from a returning customer). Your close rate — booked jobs divided by eligible inquiries — only means something if you're using the same definition of "eligible" every time you calculate it.
Be careful what you credit the checklist for. A slow month, a change in lead source, or a run of jobs outside your usual scope can move that number just as much as anyone's answer on the phone. A dip or a rise the month after you write the checklist isn't proof of anything on its own — it's a data point to add to the ones that come after it.
Before the next call comes in
Imagine handing the phone to someone else and knowing exactly what they'll say — not because they memorized a script, but because the decisions underneath their answer are the same ones you'd make. Now compare that to stopping mid-afternoon, again, to settle a question that should have already had an answer.
You don't need new software or a training program to start. You need one hypothetical inquiry, answered independently by everyone who quotes jobs, compared side by side. Where they agree, write it down. Where they don't, that's the next rule to settle.
Frequently Asked Questions
Start by writing down the decisions your business already makes on every quote — even if right now those decisions only live in your head or your best employee's. What questions get asked before pricing, what can be quoted by phone versus assessed in person, what the price includes, who can discount and by how much, and what happens right after someone says yes. Once those five or six decisions are on paper, you have a sales process.
At minimum: the qualifying questions that change eligibility or price, what can be priced over the phone versus what needs an in-person look, exactly what's included and excluded in the base price, who has authority to discount and where that authority stops, and what the next step is the moment someone says yes.
Test it before you train it. Give every employee who quotes jobs the exact same hypothetical inquiry and have each of them answer independently in writing. Compare the answers side by side. Where they agree, you've confirmed a rule everyone already follows. Where they disagree, that's the specific thing to write down and settle.
It depends on the job, and that's exactly the kind of thing that belongs on a shared checklist rather than each employee's judgment call. Some jobs are simple enough to price by phone; others genuinely need an in-person look. The problem isn't which answer you pick — it's different employees picking different answers to the identical situation.
Separate what has to stay the same from what can stay natural. The facts — the questions asked, the price boundaries, who's allowed to discount, what happens next — should be identical no matter who answers. The wording around those facts doesn't need to be. A checklist gives employees the guardrails; it doesn't have to hand them a word-for-word script.
