Technical Sales Fundamentals
Introduction
A production manager asks what a system will cost. The technician who knows the answer gives it, and loses. The one who asks what the room is, what went wrong last year and who is in the audience wins work worth four times as much, and is not a better salesperson — they simply did the phases in order.
Technical sales is the part of this trade that technicians are most suspicious of and best suited to. Suspicious because selling looks like persuasion, and best suited because the thing being sold is a technical answer, and a buyer can tell within ninety seconds whether the person opposite them actually knows it.
The subject also has a real literature, which is a surprise. There are seven named phases of a sale, and most failed calls are a presentation delivered during what should still have been discovery. There are thirteen types of question with distinct objectives. There are five documented ways to handle an objection and six ways to close, and the reason technicians use none of them is not ignorance but reluctance.
And there is a reframe worth the price of the book on its own: an objection is usually interest. A buyer who argues is engaged. The ones who say "very interesting, send me something" are the ones who have already gone.
This book teaches the named techniques, in AV terms, alongside the parts the general literature cannot cover: what a demonstration does in this trade, what an AV quote must actually contain, and where margin is quietly lost between the quote and the invoice.
How to Use This Book
Read it in order the first time. It follows the sale: what this is, the seven phases, the cycle they sit in, discovery, the questions that drive discovery, the demonstration, the proposal and quote, objections, and closing.
Then use three chapters as working documents. The questions chapter is something to take into a meeting. The quoting chapter is a checklist to run a quote against before it goes out. And the closing chapter is worth rereading before any call you are dreading, which for most technical people is all of them.
Keep a notebook
One record per opportunity, from today: what they asked for, what you found out that they did not volunteer, what you proposed, what they objected to, and what actually happened. Five lines. After a dozen you will see your own pattern, and it is nearly always one of two things — presenting before discovering, or never asking for the order. Neither is visible from inside a single call.
A note on the words
"Sales" in this book means winning a specific piece of work, which is different from account management, where the objective is preferred supplier status rather than a closed sale. "Discovery" is the phase the literature calls need and problem identification. A "close" is a request for a decision, not a trick. And "objection" is used in the literature's sense — any concern or question raised by the buyer — which is broader and more useful than the everyday meaning of a refusal.
A note on safety
Selling is where unsafe shows are agreed, months before anybody picks up a case.
A quote is a set of promises about time, crew and access. Quote one person fewer to win on price and somebody lifts alone. Quote a load-in an hour shorter than the room allows and the crew makes it up by skipping the part that felt optional, which is usually the part that was holding something up. Agree a turnaround the client wants rather than the one the work needs and people drive home unfit to drive.
None of that is visible at the point of sale, which is exactly the problem: the person who agrees it is not the person who pays for it. So the rule in this book is that crew numbers, load-in time and turnaround are not commercial variables. Price, scope and specification can move. Those three are checked with somebody who will actually be on the job, before the number goes out.
And never sell a capability you do not have on the assumption it can be worked out later. In AV that assumption is settled at height, under time pressure, by people who were not in the meeting.
What Technical Sales Is
The thing being sold is a technical answer, which makes the person who actually knows it the right person to sell it.
The best AV salespeople do not sell gear. They solve clients' problems with AV.
Consultative selling
The textbook's starting position is that selling should be an extension of the marketing concept — that it is in the seller's long-term interest to identify and satisfy what the customer actually needs, rather than to shift whatever is in stock. That is the whole of consultative selling, and everything else in this book is machinery for doing it.
In practice it means the first objective of any sales conversation is to discover the customer's problems and needs, not to describe your capability. The chapter is explicit that salespeople should avoid the temptation of making a presentation without first finding out the needs of the customer, and that it is all too easy to open in the same rigid way every time.
For AV that temptation is specific and strong. Somebody asks what you can do and the instinct is to tell them — the kit, the capability, the previous jobs. It feels helpful and it is a presentation delivered in phase two of a seven-phase process, which is why so many promising conversations end with "send me a quote" and then silence.
Why technical knowledge sells
A buyer of AV is usually buying insurance against embarrassment, and they are assessing one thing above all: does this person actually know? That judgement is made fast, from how you answer a question you were not expecting.
Which gives a technician three advantages a professional salesperson does not have. You can answer the hard question in the room rather than going away to ask. You can say what will not work and why, which is the single most credible thing anybody says in a sales meeting. And you can run a demonstration, which the literature treats as a phase of its own because showing beats describing.
The corresponding weakness is just as specific. Technical people over-explain, answer the question that was asked instead of the one underneath it, and reliably fail at the last phase — they will do everything except ask for the decision. Those three faults are what the rest of this book is about.
Sales against account management
These are different jobs with different objectives, and mixing them up is why some suppliers chase every enquiry and keep no clients.
In transactional selling the overall objective is the sale and the goal is the closed deal. In key account management the objective is preferred supplier status and the goal is managing the relationship. Both are legitimate; they just lead to different behaviour in the same meeting.
The practical rule is to know which conversation you are in. A one-off enquiry from somebody you will not see again is a sale: run the phases, close it, move on. A first job for a client who could become an account is an audition, and behaving as though the objective is this order will cost you the nine that would have followed.
How to do it
- Find out what the event or project actually is before you are asked anything.
- Find out who is in the room and what each of them is judged on.
- Decide whether this is a sale or the start of an account, and behave accordingly.
- Write down the three questions you most need answered, and take them in.
- Decide in advance what you will not do, so the limit is a position rather than an improvisation.
- Agree internally what you can commit to on crew, time and access before you are in front of anybody.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A good conversation that ends in silence | A presentation delivered before discovery was done | Hold the capability talk until you can name their problem |
| Winning work that loses money | Price conceded because the objective was the closed sale | Decide which objective you are pursuing before the meeting, not during it |
| Out-talked by a non-technical competitor | Over-explaining instead of answering the question underneath | Answer in consequences; the technical depth is held in reserve for the hard question |
| A promise made in a meeting the crew cannot deliver | Commercial pressure applied to crew, time and access | Settle those three internally before the number goes out |
Practice it
Using your last three enquiries.
- You can state their problem before you describe your capability.
- You know who is in the room and what each is judged on.
- You know whether this is a sale or an audition for an account.
- You answered in consequences, not specifications.
- You said plainly what will not work.
- Crew, time and access were agreed internally before quoting.
The Seven Phases
Seven named phases, which need not happen in order and need not all happen in one call. Knowing which one you are in is most of the skill.
The phases, named
The literature distinguishes seven phases of the selling process, and in the textbook they are literally the chapter's own sections in sequence.
- The opening. Establishing who you are and why the conversation is worth their time.
- Need and problem identification. Discovering what the customer is actually trying to solve. This book calls it discovery.
- The presentation and demonstration. Showing how what you have meets what you found.
- Dealing with objections. Working through the concerns and questions the buyer raises.
- Negotiation. Where the seller has discretion over terms, agreeing them.
- Closing the sale. Asking for the decision.
- Follow-up. Making sure the thing actually worked, after the money.
The chapter is careful that these need not occur in the order shown: objections arrive during a presentation or a negotiation, a trial close can be attempted at any point if interest is high, and negotiation may not happen at all.
Phases happen over time, and across people
A finding quoted in the chapter matters more in AV than almost anywhere: the evolved selling process assumes a salesperson will perform the various steps in some form, but that the steps do not occur in each sales call — they occur over time, accomplished by multiple people within the selling firm, and not necessarily in the order given.
That describes AV exactly. Discovery happens on a site visit with a technician. The demonstration happens in a warehouse with somebody else. The quote comes from a third person. Objections arrive by email a week later. The close might be a production manager ringing to say go.
The practical consequence is that somebody has to hold the thread, because the phases are distributed. If nobody owns the opportunity across those handovers, the usual failure is that everybody assumes discovery was done by somebody else, and the quote answers a question nobody asked.
Knowing which phase you are in
The single most useful habit this chapter produces is asking yourself, mid-conversation, which phase this is. It sounds academic and it is immediately practical, because the commonest failure in technical selling is doing phase three in phase two.
Three quick tests. If you cannot yet state their problem in their words, you are in discovery, whatever else is happening. If they are raising concerns, you are in objections, and that is progress rather than resistance. And if they have stopped asking questions and started looking at the time, you are past closing and into having missed it.
Use the phases as a position check rather than a script. A script in a technical sale is obvious within a minute and costs you the credibility that was your main advantage.
How to do it
- Open by saying why you are worth their time, briefly, then stop talking.
- Discover until you can state their problem back in their own words.
- Present only what answers what you found, and demonstrate if you can.
- Treat every objection as a question and answer it without defending.
- Negotiate only what you actually have discretion over.
- Ask for the decision.
- Follow up after delivery, whether or not anything else is available.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A presentation that lands flat | Delivered in phase three before phase two was finished | Test: can you state their problem in their words? If not, keep discovering |
| A quote answering a question nobody asked | The phases were distributed across people and nobody held the thread | Name an owner for the opportunity across handovers |
| Objections treated as the end of the conversation | Read as refusal rather than as a phase | An objection is a phase you were always going to reach |
| A conversation that never reaches a decision | The closing phase was skipped entirely | The phase exists; somebody has to ask, and it is usually you |
Practice it
For your most recent significant opportunity.
- You can name which phase a conversation is in.
- Discovery finished before the presentation started.
- Objections were treated as a phase, not a verdict.
- Somebody owns the opportunity across handovers.
- Somebody asked for the decision.
- Follow-up happened after delivery.
The Opening
Phase one, and the one technical people skip because it feels like small talk. Initial impressions cloud everything that follows.
Why the first two minutes decide a lot
The textbook opens its treatment of the selling process with a plain statement: initial impressions can cloud later perceptions, so it is worth considering how a favourable initial response is achieved. That is not a point about charm. It is a point about how judgements get made and then defended.
Buyers expect salespeople to be businesslike in appearance and behaviour, and the chapter is blunt that untidy hair and a sloppy manner of dress create a lack of confidence. For a technical seller that lands awkwardly, because the trade tolerates and even prizes a scruffy competence. It is worth separating the two settings: on a load-in, nobody cares. In a client's meeting room before any work exists, you are the evidence.
The second expectation is about time. The chapter notes that a salesperson who does not respect that the buyer is busy, with many demands on their time, causes irritation. Technical people breach this one constantly and with good intentions — by explaining more than was asked, because the subject is genuinely interesting.
The mechanics, which are not trivial
The chapter's specifics are almost comically concrete, and they are worth keeping because each removes a small awkwardness that is otherwise paid for in attention.
- Open with a smile, a handshake and an introduction. Say who you are and which company you represent, where you are not already well known.
- Observe the courtesies. Wait for the buyer to indicate you can sit, or ask.
- Carry the briefcase in the left hand. So the right is free for the handshake, and there is no fumbled transfer as they extend theirs.
- Make the opening remarks business-related. They set the tone for the rest of the interview, and business is the purpose of the visit.
The briefcase line sounds like period detail and is actually the general principle in miniature: remove every small friction, because each one costs a fraction of the attention you need for the part that matters. The modern equivalents are a phone already silenced, a laptop that does not need four minutes to wake, and knowing in advance whether the room has the connector you brought.
Opening a technical conversation
Beyond the courtesies, the opening has a job: to establish why this conversation is worth their time, briefly, and then to stop. The characteristic technical failure is opening with capability — what we do, what we own, where we have worked — which is a presentation delivered in phase one.
A workable shape is three sentences. Who you are and why you are relevant to them specifically. What you understand about their situation, which signals you did some work before arriving. And a question that hands the conversation over.
Then let the silence do its work. An opening that ends in a question and a pause gets you into discovery within a minute. An opening that ends with a capability statement invites them to respond with a specification, and you will spend the rest of the meeting quoting rather than understanding.
How to do it
- Dress to the setting: the meeting room is not the load-in.
- Arrive with everything ready -- phone silenced, laptop awake, adaptors with you.
- Carry anything in your left hand so the right is free.
- Introduce yourself and your company if you are not known.
- Wait to be invited to sit, or ask.
- Say in one sentence why you are relevant to them specifically.
- Say what you already understand about their situation.
- Ask a question, then stop talking.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A meeting that never got past specifications | The opening was a capability statement | End the opening with a question, not with what you do |
| A buyer visibly impatient within five minutes | Their time was not respected | Say why you are relevant, briefly, and hand the conversation over |
| Credibility lost before anything technical was discussed | Appearance and preparation read as carelessness | The meeting room is a different setting from site; prepare for it |
| Four minutes lost to a laptop or an adaptor | Friction that could have been removed beforehand | Everything ready before you walk in; each small friction costs attention |
Practice it
Before your next first meeting.
- You were dressed and prepared for that setting.
- Nothing needed fixing once you were in the room.
- You introduced yourself and your company.
- You said why you are relevant to them specifically.
- You showed you had understood something before arriving.
- You ended with a question and then stopped.
The Sales Cycle
An opportunity has a life, and most are lost not by being refused but by being forgotten in the middle of it.
A deal moves through stages. Knowing where you are tells you what to do next.
From lead to close
A lead is somebody who might buy. An opportunity is a specific piece of work with a budget, a date and a decision-maker. The distinction matters because leads are counted and opportunities are worked, and a pipeline full of leads nobody has qualified is a comfortable way to be busy and win nothing.
Qualification is three questions, asked early and without embarrassment. Is there a real budget, or is this somebody finding out what things cost? Is there a decision-maker identified, or are you talking to somebody gathering options? And is there a date, or is this next year in principle?
An enquiry failing all three is not worthless, but it is marketing rather than an opportunity, and it should not be consuming the hours that a real one needs. Technical people are particularly bad at this, because an interesting technical problem is enjoyable to work on whether or not anybody is going to pay for it.
Managing opportunities
Keep a list with four columns and nothing else: what it is, what it is worth, what the next action is, and when. The fourth column is the one that does the work, because an opportunity with no dated next action is not being managed.
The characteristic AV failure is going quiet during the client's own decision period. You quote, they go into their internal process, and three weeks of silence feels like rejection so nobody follows up. Meanwhile the competitor who phoned twice is front of mind. Silence from a client is almost never a decision; it is their week being busier than yours.
Decide a follow-up rhythm in advance and hold it: a check that the quote arrived, a check before their decision date, and a graceful close-out if the answer is no. That third one is not futile — the reason you lost is the most useful information available, and it is only available in the week after.
Losing well
You will lose most of what you quote for, and the proportion is not a sign of failure. Winning everything means you are too cheap, a point the companion book Freelance Business Fundamentals makes about rates.
When you lose, ask why, once, without arguing. Price, timing, incumbency and specification are the usual four, and they are very different problems: price is a positioning decision, timing is a pipeline problem, incumbency means you were quoting as a stalking horse, and specification means you misread the discovery.
Record the reason. Over a year the pattern tells you something no single loss does — and if the answer is consistently incumbency, the fix is not better quoting but getting in front of the next one earlier, which is the subject of the companion book Account Management rather than of this one.
How to do it
- Qualify on budget, decision-maker and date before investing real hours.
- Record it with its value, its next action and the date of that action.
- Agree the follow-up rhythm with yourself before the silence starts.
- Check the quote arrived and is complete.
- Contact them before their decision date, not after it.
- If you lose, ask why once, do not argue, and write it down.
- Review the loss reasons once a quarter for the pattern.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A busy pipeline that produces nothing | Leads being worked as though they were opportunities | Qualify on budget, decision-maker and date |
| An opportunity that went silent and was never revived | Silence read as rejection | A dated next action on every opportunity, and contact before their decision date |
| Hours spent on an enjoyable technical problem with no buyer | The work was interesting rather than qualified | Interest is not qualification; check the three questions |
| Losing repeatedly to the same incumbent | You are being quoted against to validate a decision already made | The fix is earlier access, which is account work rather than better quoting |
Practice it
With everything you have quoted in the last six months.
- Every entry is qualified on budget, decision-maker and date.
- Every entry has a next action with a date.
- A follow-up rhythm was decided before the silence.
- You contact them before their decision date.
- Every loss has a recorded reason.
- Loss reasons are reviewed for the pattern.
Discovery: Understanding the Need
The seller's first objective is to discover the customer's problems. Everything that goes wrong later usually went wrong here.
The most important sales skill is not talking. It is asking and listening.
Running a discovery
Discovery is the phase the literature calls need and problem identification, and the chapter is unambiguous that it comes first: before a seller can sell anything, they need to understand the customer's circumstances. Its examples are deliberately mundane — what size of car, economy or performance, what price range — because the point is that you cannot recommend before you know.
The AV version of those questions is specific. What is the event actually for. Who is the audience and how many. What is the room. What happened last year. Who else is involved. What is the budget range. When are the decisions made. And what would make this a disaster in their eyes, which is the question that reveals the most and is asked least.
Discovery is not a questionnaire. The chapter warns against opening in the same rigid way every time, and a technician working down a list is as rigid as a salesperson reciting the bargain of the week. Ask, listen, and let the answers choose the next question.
Listening and the real problem
Clients describe solutions, not problems. "We need two big screens" is a solution. The problem underneath might be that half the room could not see last year, which may be better solved by moving the stage — and the supplier who works that out is the one who gets asked back.
The move is to ask what the solution is for, without making anybody feel second-guessed. "What went wrong last time?" does most of the work, because almost every specification is scar tissue from a previous failure that nobody will mention unprompted.
Then say the problem back in their words before you propose anything. If they correct you, you have just avoided quoting for the wrong job. If they confirm it, you have earned the right to present — and the presentation practically writes itself, because it only has to answer what you have both now agreed the problem is.
Discovering what you must not do
Discovery also establishes the constraints that will later decide whether the job is deliverable, and these are the ones technical sellers skip because they are awkward rather than because they are hard.
- Access. When can you get in, when must you be out, and what does the venue actually allow.
- Power. What exists, and who is paying if it does not.
- The room. Dimensions, rigging points, load limits, sightlines, and whether anybody has measured rather than remembered.
- Who else is in the building. Other vendors whose schedule is now yours.
- What they will provide. Almost always less than assumed, and always worth stating back.
Every one of those becomes a line in the quote. A discovery that covered the creative brief and none of these produces a quote that is wrong in exactly the ways that cost money, and the person who finds out is a crew chief at six in the morning.
How to do it
- Ask what the event is for before asking anything technical.
- Ask what went wrong last time, and write the answer verbatim.
- Let the answers choose the next question rather than a list.
- Ask what would make this a disaster in their eyes.
- Cover the constraints: access, power, the room, other vendors, what they provide.
- Say the problem back in their words and let them correct it.
- Write it up and send it, so the understanding is on record.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Quoting exactly what was asked for and losing | They described a solution and the problem was underneath it | Ask what it is for and what went wrong last time |
| A quote that is wrong in expensive ways | Discovery covered the creative brief and not the constraints | Access, power, room, other vendors, what they provide -- every time |
| A discovery that felt like an interrogation | A list worked through rigidly | Let the answers choose the next question |
| Surprises on site that the client considers your fault | What they would provide was assumed rather than stated back | State it back in writing and get a reply |
Practice it
In your next discovery conversation.
- You can state their problem in their own words.
- You know what went wrong last time.
- You know what they would consider a disaster.
- Access, power, the room and other vendors are covered.
- What they will provide is stated back in writing.
- They have confirmed or corrected your understanding.
Questions as the Instrument
The literature names thirteen types of question with distinct objectives. "Ask good questions" is not a technique; this is.
Open and closed, and what each is for
Jobber and Lancaster's chapter 8 draws the basic distinction precisely. An open question is one that requires more than a one-word or one-phrase answer — why do you believe that, what were the main reasons, in what ways did it fail to meet expectations. A closed question invites a one-word answer, and is for purely factual information.
It also names the cost of overusing the closed ones: excessive use hinders rapport and leads to an abrupt kind of conversation that lacks flow. Which is exactly how a technician's discovery sounds when it is really a spec sheet being filled in — how many inputs, what size room, how many people, when is load-in. All reasonable, all closed, and the buyer feels processed.
The practical ratio is to open a topic with an open question and close it with the factual ones. "What went wrong with the audio last year?" first; "and how many lapel mics did you have then?" second. Reverse them and you get the number without ever learning why it mattered.
Thirteen types, and the ones that matter here
Jobber and Lancaster set out thirteen types of question in their Table 8.2, each with its own objective and an example. This book does not reproduce the full table, which repays reading in the original; what matters here is that questioning is treated as a set of distinct instruments rather than as curiosity, and that each is chosen for a job.
Four do most of the work in an AV discovery.
- The opening question. Broad, inviting, and designed to get them talking about their situation rather than your product.
- The problem question. Surfacing the difficulty that justifies spending money at all. Without one of these there is no reason to buy.
- The consequence question. What it costs them if it happens again. This is what turns a problem into a budget.
- The confirming question. Saying it back so the understanding is checked rather than assumed.
The sequence matters more than the taxonomy. Problem before consequence, consequence before solution, and confirmation before anything is proposed. A technician who learns only that order will outperform most people selling against them.
Silence, and the question after the answer
The most useful instrument in the set is not a question at all. Most people fill a pause within two seconds, and most clients need four to say the second, truer half of what they were telling you. The first answer is the official one; the one after the pause is what they actually think.
The second most useful is asking again, differently. "What else?" after an answer that seemed complete routinely produces the real item, because the first answer was the one they had ready.
And write the answers down in front of them, in their words. It slows the conversation, which is good, it signals that the answers matter, and it gives you the exact phrases to use in the proposal — where a client reading their own words back feels understood in a way no amount of specification achieves.
How to do it
- Open each topic with a question that cannot be answered in a word.
- Follow with the closed, factual ones once the topic is open.
- Ask the problem question before any solution is discussed.
- Ask what it costs them if it happens again, which is the consequence question.
- Leave four seconds of silence after an answer that seems complete.
- Ask "what else?" at least once.
- Confirm your understanding back in their words before proposing.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A discovery that sounded like a form being filled in | Closed questions throughout | Open the topic, then close it; the chapter names the cost of overusing closed questions |
| A real problem identified and no budget attached to it | The consequence question was never asked | Ask what it costs them if it happens again |
| The useful information arriving after the meeting | Pauses filled too quickly | Four seconds, and then "what else?" |
| A proposal that does not sound like their problem | Their words were not captured | Write the answers verbatim and use their phrases |
Practice it
In your next two client conversations.
- Each topic opened with an open question.
- Factual questions came after the topic was open.
- A problem question was asked before any solution.
- A consequence question attached cost to the problem.
- You left silence and something arrived in it.
- Their own words are written down and reused.
The Demonstration
The literature gives the demonstration a phase of its own. In AV it is the single biggest advantage a technical seller has.
Why showing beats describing
The third phase is the presentation AND the demonstration, and the pairing is deliberate. A description asks the buyer to imagine; a demonstration removes the imagining. For a product whose whole value is sensory — how it sounds, how it looks, whether the back row can read it — that difference is everything.
It is also the phase where a technician's advantage is largest. A salesperson can describe a system. Somebody who can set one up, make it work in front of a sceptical client and answer the awkward question while doing it is demonstrating competence as much as kit, and competence is what is actually being bought.
The rule from the previous chapter still binds: demonstrate what answers the problem you found, not what you are proud of. A demonstration of something impressive and irrelevant is a presentation given in the wrong phase, with more effort.
Running one that works
- Rehearse it. A demonstration that fails live does more damage than no demonstration, because you have just shown them your work failing.
- Show the thing they doubted. If discovery surfaced a worry about intelligibility at the back, that is what the demonstration is for. Everything else is filler.
- Let them operate it. A client who has touched the thing has a different relationship with it, and in AV the fear is usually "will we be able to use this".
- Include a failure. Showing what happens when a radio mic drops, and how fast it recovers, buys more trust than an hour of everything working.
- Keep it short. The demonstration ends while they still want more, not when you have run out of features.
Then stop and ask what they thought. A demonstration followed immediately by more talking wastes the only moment in the process where the buyer has direct evidence and an opinion about it.
When you cannot demonstrate
Much AV cannot be shown in advance: the room does not exist yet, the system is too large, the event is the first of its kind. The substitutes are weaker but real, and choosing deliberately beats defaulting to a slide.
A site visit is the strongest, because it is a demonstration of understanding rather than of equipment — walking their room and saying what will happen in it. Reference selling is the next, and the literature names it as a concept in its own right: a previous client who will speak to them removes risk in a way no specification does. Photographs and recordings of a comparable job come third, and are far better than renderings.
What does not work is specification. A list of model numbers demonstrates nothing to somebody who cannot evaluate it, and to somebody who can it demonstrates only that you can copy a data sheet.
How to do it
- Decide the one doubt from discovery that this will answer.
- Rehearse it end to end, in conditions as close as you can get.
- Keep the setup visible; the competence is part of the product.
- Let them operate it themselves.
- Show a failure and the recovery.
- Stop while they still want more.
- Ask what they thought, and then be quiet.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| An impressive demonstration that did not help | It showed what you are proud of, not what they doubted | Demonstrate against the doubt discovery surfaced |
| A demonstration that failed live | Not rehearsed in realistic conditions | Rehearse, or do not demonstrate; a live failure is worse than no demonstration |
| A client still unsure they could use it | They watched rather than touched | Put it in their hands |
| Falling back on a specification list | Nothing could be demonstrated and no substitute was chosen | Site visit, then a reference, then photographs of a comparable job |
Practice it
For your next opportunity.
- It answered a doubt that discovery actually surfaced.
- It was rehearsed in realistic conditions.
- They operated it themselves.
- A failure and its recovery were shown.
- It ended while interest was still high.
- You asked what they thought and then stopped talking.
Proposing & Quoting
A quote is a set of promises about money, scope, time and people. Most margin is lost in the three that are not money.
Propose what serves the client and that you can deliver, and price it clearly.
Proposing a solution
A proposal answers the problem you agreed in discovery, in their words, before it describes anything you will supply. That ordering is the whole craft: a client reading their own problem back feels understood, and a client who feels understood reads the rest differently.
Then say what you propose and why, in consequences rather than specifications. Not a model number but what it means — the back row will read the slides, the presenter will not have to think about the microphone, the room resets in twenty minutes between sessions.
Keep the technical detail, but put it after the part that decides. A proposal whose first page is a schedule of equipment is a document written for the writer. The buyer reads page one and decides whether to read page two.
Quoting and handling objections
An AV quote has to contain more than a price, and the items most often missing are the ones that later cost money.
- What is included, itemised. Not a lump sum for "AV".
- What is explicitly not included. The single most valuable line in the document.
- Crew numbers and hours, and what happens beyond them.
- Access requirements: when you need the room, and for how long.
- What the client must provide, with dates.
- Validity period — a quote without one is a price you offered forever.
- Payment terms, which the companion book Freelance Business Fundamentals treats at length.
On price objections specifically, the literature's framing helps: an objection is a concern or question, often an expression of interest, and a signpost to what is really on the buyer's mind. "That is more than we expected" is almost never a refusal. It is a request to be shown why, or an admission that the budget was set before the scope was understood — and those need completely different answers.
Where margin actually goes
Margin in AV is rarely lost at the moment of quoting. It is lost afterwards, in small increments nobody records.
- Scope absorbed. One more microphone, a second camera position, a longer rehearsal. Each trivial, four of them a different job at the same price.
- Hours not counted. The site visit, the three rounds of revisions, the hour on the phone redesigning it.
- The overrun. No agreed position on hours past the day, so the uplift is zero.
- Kit absorbed. Items added on site because it was easier than the conversation.
The fix is not toughness, it is recording. Note every change as it happens, with its consequence in time or money, even when you intend to absorb it. Absorbed and recorded is a visible gift that earns goodwill. Absorbed and unrecorded is an invisible loss that earns nothing, and it is how a busy year produces no profit.
How to do it
- Open with their problem, in their words, before anything you supply.
- State what you propose and why, in consequences not specifications.
- Put the technical detail after the part that decides.
- Itemise what is included.
- State explicitly what is not included.
- State crew, hours, access, what they must provide, validity and payment terms.
- From then on, record every change with its consequence, even the ones you absorb.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A proposal that did not land despite being correct | It opened with equipment rather than with their problem | Their problem, in their words, on page one |
| "That is more than we expected" ending the conversation | Read as refusal rather than as a question | It is a signpost; find out whether they need showing why or the budget predated the scope |
| A profitable quote that delivered no profit | Scope and hours absorbed without being recorded | Record every change with its consequence, even when absorbing it |
| An argument about something you never offered | What was NOT included was never written | The exclusions line is the most valuable one in the quote |
| A six-month-old quote accepted at the old price | No validity period | Put one on every quote |
Practice it
With your last quote and the job that followed it.
- It opens with their problem in their words.
- Benefits are stated as consequences, not specifications.
- Inclusions are itemised.
- Exclusions are explicit.
- Crew, hours and access are stated.
- What the client must provide has dates.
- It has a validity period and payment terms.
Objections
An objection is a concern or a question, and most of them are interest. The buyer who argues is still in the room.
What an objection actually is
The chapter defines objections as any concerns or questions raised by the buyer, and then makes the point that changes how a technical person hears them: objections should not always be viewed with dismay, because many are simply expressions of interest. The buyer is asking for further information because they are interested and not yet convinced.
It goes further: objections highlight the issues that are important to the buyer. The chapter cites Ford's line to its own sales trainees — that customers' objections are signposts to what is really on their minds.
Read that way, an objection is the most useful thing that happens in a sales conversation. It tells you what they actually care about, which discovery may have missed, and it proves they are still engaged. The dangerous meeting is the one where everybody is agreeable and nothing is raised.
The five techniques
- Listen and do not interrupt. The chapter is pointed about what interrupting signals: that the objection is obviously wrong, that it is trivial, or that it is not worth your time to let them finish. None of those is recoverable.
- Agree and counter. Acknowledge the point before answering it. The concession costs nothing and makes the answer hearable.
- Forestall the objection. Raise the known problem yourself, before they do. In AV this is powerful: saying "the obvious worry here is the sightline from the far corner, so here is what we do about it" removes the objection and demonstrates that you thought about it first.
- The trial close. Testing whether the objection was the last one, by asking whether solving it settles the matter.
- Hidden objections. The stated concern is sometimes not the real one, and a buyer who keeps finding new problems usually has one they have not said.
Running under all five is the chapter's point about face: the answers must be given in a way that lets the buyer accept them without loss of face. Winning an argument with a client is the most reliable way to lose the work, and technical people are unusually good at winning arguments.
The objections AV actually gets
- "That is more than we budgeted." Usually means the budget predates the scope. Ask what the budget was based on.
- "We have always used someone else." Incumbency. Forestall it, do not fight it: ask what works well about the current arrangement, and what they would change.
- "Can you do it with fewer people?" The one to refuse. Crew numbers are a safety term, as the front of this book says, not a commercial variable.
- "Can't we just..." Almost always a reasonable question about something that is harder than it looks. Explain the constraint in consequences, not in jargon.
- "Send us something and we'll be in touch." The polite close, and the one to treat as an objection rather than an outcome. Ask what would need to be true for them to decide.
Keep a list of the objections you actually receive. Within a season the same five or six repeat, which means they can be forestalled in the proposal itself — which is the cheapest objection handling there is.
How to do it
- Let them finish, entirely, without interrupting.
- Acknowledge the point before answering it.
- Answer in consequences, leaving them room to accept it.
- Ask whether that settles it, which is the trial close.
- If new objections keep arriving, ask what the real reservation is.
- Afterwards, add it to the list, and forestall it next time in the proposal.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| An objection answered and the buyer colder | They were interrupted, or made wrong | Let them finish, and answer in a way they can accept without losing face |
| A string of objections with no end | There is a hidden one | Ask what the real reservation is |
| The same objection on every job | It is never forestalled | Raise it yourself in the proposal, with the answer attached |
| An argument won and the work lost | Technical correctness used as a weapon | The objective is the decision, not the point |
| "Send us something" treated as progress | A polite close read as interest | Treat it as an objection and ask what would need to be true |
Practice it
From memory, then on paper.
- You hear an objection as interest rather than refusal.
- You let them finish.
- You acknowledge before answering.
- Your answers leave them room to agree.
- You test whether it was the last one.
- Repeat objections are forestalled in the proposal.
Negotiation
Negotiation only enters where you have discretion over terms. When it does, there is research on what effective negotiators actually do.
When negotiation enters at all
The chapter is precise about this: negotiation enters the sales process in situations where the salesperson or sales team has a degree of discretion over the terms of the sale. Where there is no discretion there is no negotiation, and pretending otherwise just erodes your own price.
What can be negotiated is broader than people assume. The chapter lists price, credit terms, delivery times, trade-in values and other aspects of the commercial transaction. In AV that translates into a long list that is not the day rate: payment terms, the deposit, how many days are billed, what is included, delivery and collection, who provides what, and when you get the room.
The deal that results, it says, depends on the balance of power and on the negotiating skills of the parties. The first of those is established before you walk in — by how many alternatives they have and how much they need you — which is why preparation is where most negotiations are decided.
That preparation is specific: estimate the buyer's needs, the competition the supplier faces, and what you know about the buyer's business and the pressures on them. A technical seller who has done discovery properly has already collected most of it.
Two rules and a set of behaviours
The chapter gives two guidelines and then a research-backed set of behaviours.
- Start high but be realistic. Three reasons: the buyer might agree to it, it provides room to negotiate, and buyers come to expect concessions in return for purchasing. "Realistic" is doing real work in that sentence — an opening position that is not credible costs you the credibility you came in with.
- Trade concession for concession. Sometimes a concession is simply needed to secure the sale, and if you left room, that is fine. Where you have power, the move is to get something back rather than to give.
Then the behaviours. The chapter reports research by the Huthwaite Research Group comparing skilled negotiators with average ones, which identified behaviours associated with success.
- Ask lots of questions. They gather information, and knowledge is power. They also identify how the buyer feels, give you control of the topic, buy thinking time while the other person answers, and serve as an alternative to outright disagreement.
- Use labelling behaviour. Announce what you are about to do: "Can I ask you a question?", "I should like to make two further points", "May I summarise?"
- But do not label disagreement. Announcing in advance that you are going to contradict somebody is a reliable way of ensuring your argument gets no fair hearing. "I totally disagree" makes the other party defensive before they have heard the reason.
- Maintain clarity by testing understanding and summarising. The same move as the check-back in Client & Stakeholder Communication, doing the same job under more pressure.
Notice that three of the four are questioning and summarising — the instruments from the discovery chapter, used again. A technical person who has learned to ask and confirm is already most of the way to negotiating competently.
What buyers do to you
The chapter also sets out techniques buyers use, noting that sellers should know they exist because their effect can otherwise be devastating. Three are named.
- The shotgun. "Unless you agree immediately to a price reduction of twenty per cent, we'll look elsewhere." The correct response depends on the balance of power you assessed in preparation. If they genuinely have several options offering the same benefits, you may have to concede. If your offer has clear advantages, you can resist.
- "Sell cheap, the future looks bright." The promise that a low price now pays off in future volume. Sometimes genuine, and sometimes a gambit to extract the maximum concession. Where your position is reasonably strong, ask for specific details and firm commitments.
- Noah's Ark. Tapping a file: "You'll have to do much better. I have quotations from your competitors that are far lower." Named for how long it has been in use. Responses scale with confidence: ask to see them, or take the initiative by assuming they want the price justified, or — flushed with past success — advise them to accept one.
All three appear in AV almost word for word, and the third most often. The useful thing is simply recognising them as techniques rather than as information, because the instinctive response to all three is to discount, and that is what they are designed to produce.
One limit from the front of this book still binds. Crew numbers, access time and turnaround are not negotiating currency, whatever is being tapped on the table. Price, scope and specification can move. Those three are settled with the people who will do the work.
How to do it
- Establish whether you actually have discretion. If not, this is not a negotiation.
- List everything negotiable besides price: terms, deposit, days, inclusions, delivery, access.
- Assess the balance of power: how many real alternatives do they have?
- Review what discovery told you about their needs and their pressures.
- Open high enough to leave room, and credible enough to be taken seriously.
- Trade every concession for something rather than giving it.
- Ask questions, label what you are about to do, never label disagreement, and summarise often.
- Recognise the shotgun, the future-volume promise and Noah's Ark for what they are.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Price conceded where nothing else was ever discussed | Only one variable was on the table | Terms, deposit, days, inclusions, delivery and access are all negotiable |
| An opening position that was not taken seriously | High but not realistic | Leave room, but stay credible; the credibility is what you came in with |
| Concessions given away one at a time | Nothing was traded for them | Every concession buys something, even if only a commitment |
| An argument that got no fair hearing | The disagreement was labelled before the reason was given | Label your behaviour, never your disagreement |
| An immediate discount offered to a competitor's quotation | Noah's Ark worked | Recognise it as a technique; ask to see them, or offer to justify your price |
| A crew reduced to win a negotiation | Treating a safety term as commercial currency | Price, scope and specification move. Crew, access and turnaround do not |
Practice it
For a live or recent negotiation.
- You confirmed you had discretion before negotiating.
- More than price was on the table.
- You assessed how many real alternatives they had.
- Your opening left room and stayed credible.
- Every concession bought something.
- You labelled your behaviour and never your disagreement.
- You summarised and tested understanding.
- Crew, access and turnaround never became currency.
Closing
Six named closes exist. The obstacle for technical people is never which one to use.
Why this phase gets skipped
The chapter is blunt that the earlier skills are not sufficient on their own: a final ingredient is needed, which is the ability to close. Some sellers believe a good presentation should lead the buyer to ask for the product, and the chapter says this sometimes happens but that more usually the seller has to take the initiative.
The reason is doubt. However well you identified needs, matched benefits and handled objections, some doubt remains, and it shows up as a wish to delay — would it not be better to think it over, would it not be sensible to see what the other supplier offers. The chapter's answer is unsentimental: if the buyer puts the decision off, it is as likely they will buy from the competition. While you are there, you have the advantage.
For technical people the reluctance has a particular flavour. Asking feels like pressure, and pressure feels like the opposite of the honest, consultative thing you have been doing for an hour. It is worth naming that directly: asking for a decision is not pressure. Leaving somebody with an unmade decision and an unfinished conversation is simply less useful.
The six closes
- Ask for the order. Simply and directly. It is the one people believe is too blunt and the one that most often works.
- Summarise and ask. Recap what has been agreed, then ask. The chapter's example runs through the agreed points and then puts the question.
- The objection close. Use the final objection as the hinge: if we solve that, are we agreed?
- The alternative close. Offer two acceptable options rather than a yes or no, so the decision is which rather than whether.
- The concession close. Hold something small back to give at the decision point.
- Action agreement. Where a decision is not available today, agree the next concrete step with a date. In AV this is the realistic one most of the time.
Action agreement deserves emphasis for this trade, because most AV decisions are not made in the room — they go to a committee, a budget holder, a procurement cycle. "What is the next step and when?" is a close, and leaving without one is what turns an opportunity into the silence described in the pipeline chapter.
Buying signals, and the follow-up
Buying signals are the chapter's term for the indications that a buyer is ready, and the practical use is knowing when to stop presenting. Questions about delivery, price details, terms, or what happens next are all signs that the selling part is over and the deciding part has begun. Continuing to sell past that point introduces doubt where there was none.
The chapter also notes that purchase intention is not a smooth rise but a series of peaks and troughs — a benefit that matches a need sends it up, an objection brings it down. A trial close can be attempted at any point when interest is high, which is the practical reason to watch for the peak rather than working to the end of your material.
And then follow-up, the seventh phase and the most skipped, because it produces no immediate order. The chapter's argument is that for most companies repeat business is the hallmark of success, and that the follow-up call shows the seller cares about the customer rather than only about the sale. It also provides reassurance against post-purchase doubt, which is real and is why a client goes quiet after agreeing.
How to do it
- Watch for buying signals and stop presenting when they appear.
- Attempt a trial close at a peak rather than at the end of your material.
- Summarise what has been agreed.
- Ask for the decision, plainly.
- Where no decision is available, agree the next concrete step with a date.
- Confirm in writing the same day.
- Follow up after delivery, whether or not anything else is on offer.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A conversation that went well and ended with nothing | Nobody asked | Ask for the order; it is the plainest of the six and the most effective |
| Selling past the moment they were ready | Buying signals missed | Questions about delivery, price detail or next steps mean stop presenting |
| A decision deferred and never revisited | No action agreement with a date | Where the decision is not available, close on the next step instead |
| A won job and a client who went quiet | Post-purchase doubt, unaddressed | Follow up; the chapter treats reassurance as one of its main purposes |
Practice it
On your last five opportunities.
- You stopped presenting when buying signals appeared.
- What was agreed was summarised.
- Somebody asked for the decision.
- A next step with a date exists if no decision was available.
- It was confirmed in writing the same day.
- Follow-up happened after delivery.
Closing & Building Relationships
The sale is one transaction. What it becomes depends on what happens after the money.
The close is the beginning, not the end. Real success is the client who comes back.
Closing and following through
Winning the work is the beginning of the obligation, and in this trade delivery and selling are rarely the same person, which is where sold work turns into disappointed clients.
Hand over properly. Everything learned in discovery — what the event is for, what went wrong last year, what they consider a disaster, what was promised and in what words — belongs with the people delivering it. A handover of the quote alone is a handover of the specification without the understanding, and the crew then meets a client whose expectations were set by a conversation they never heard.
Then follow through visibly. The chapter's point about follow-up is that it shows the seller cares about the customer rather than only about making sales, and that it reassures against the doubt that follows any significant decision. In AV the cheapest version is the one named in the companion book Account Management: a short post-show report, sent within days.
Relationships and the long game
Every sale is either a transaction or the first stage of a relationship, and the difference is decided by what you do in the fortnight after delivery rather than by anything in the pitch. In the relational model this is Pre-KAM becoming Early-KAM: the first real work done conspicuously well, with trust built on consistent performance and open communication.
Which reframes what a first job is worth. A small first order priced for access, delivered immaculately and followed up properly, is worth more than a larger one won on price and delivered adequately — because the first produces the second, third and ninth, and the second produces a client who will leave for a cheaper quote.
The limit is worth stating too: not every client should become an account. Some are correctly transactional, and the selection criteria in Account Management are how you tell. Courting a client who takes three quotes every time is effort that belongs somewhere it compounds.
Glossary
| Close | Reaching agreement; the client books the work |
| Consultative selling | Listening and solving a problem rather than pushing product |
| CRM | Customer relationship management system for tracking opportunities |
| Discovery | The conversation to understand the client's real need |
| Lead | A potential client with a possible need |
| Objection | A client concern or question during the sale |
| Pipeline | The flow of opportunities at various stages |
| Proposal | The solution offered to meet the client's need |
| Quote | The proposed solution with price and terms |
Practical sign-off
Sales skill is built in client conversations. You run a discovery, propose a fitting solution, build a clear quote, handle an objection, and track the opportunity in a CRM. A mentor signs off when you can move an opportunity consultatively from discovery to close.
- Ran a discovery uncovering goal, constraints, and decision
- Proposed a solution tailored to the need and deliverable
- Built a clear quote and handled an objection honestly
- Tracked the opportunity through the cycle in a CRM
What selling does to a technician
Two things worth knowing before you take this on.
The first is that you will carry the gap between what was sold and what is delivered, and you will feel it in both directions: from a crew who think you promised too much, and from a client who thinks you promised more. The protection is the one in the safety note — crew, time and access settled internally before the number goes out — plus writing down what was actually agreed, every time. Most of that pain is a documentation problem wearing an emotional costume.
The second is that it is learnable, which is the real message of the literature. Seven phases, thirteen questions, five objection techniques, six closes. None of it is charisma, all of it is practice, and the technical knowledge you already have is the part that cannot be taught quickly to somebody coming the other way.
How to do it
- Hand over the understanding, not just the quote: what it is for, what went wrong before, what was promised and in what words.
- Stay visible during delivery without taking over.
- Send a short post-show report within days.
- Ask what they would change, and write the answer down.
- Decide deliberately whether this client should become an account.
- If it should, hand it to whoever owns accounts, properly.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A client disappointed by a job delivered as specified | The quote was handed over and the understanding was not | Hand over discovery, in their words, to the delivery team |
| A first job that produced no second | No follow-up after delivery | A post-show report within days, and a question about next time |
| Caught between crew and client over what was promised | What was agreed was never written down | Confirm in writing at the time; most of this pain is documentation |
| Effort invested in a client who will always take three quotes | Treating every sale as the start of an account | Use the selection criteria; some clients are correctly transactional |
Practice it
On the last job you sold.
- Discovery was handed over, not just the quote.
- You stayed visible during delivery.
- A post-show report went out within days.
- You asked what they would change.
- A deliberate decision was made about whether this is an account.
- If it is, somebody owns it by name.
Where to Go Next
This book covered winning a specific piece of work. Account Management covers what happens once a client is worth keeping, including the six stages, the bow-tie problem and why accounts actually end. Client & Stakeholder Communication covers the conversations themselves. And Freelance Business Fundamentals covers the commercial frame underneath all of it -- rates, terms and getting paid.
The chapters this book leans on are 8 and 9 of Jobber and Lancaster's Selling and Sales Management, and chapter 8 repays reading in full -- particularly Table 8.2, which sets out all thirteen question types with their objectives and examples, and the negotiation section this book only touches.
The first ninety days
Four things, none of which takes a day. In your next discovery, ask what would make this a disaster for them and write the answer verbatim. Leave four seconds of silence once, deliberately, and notice what arrives. Write the five objections you receive most often and the sentence that forestalls each. And on your next opportunity, ask for the decision out loud -- or, if none is available, agree the next step with a date.
Then start the notebook: five lines per opportunity -- what they asked for, what you found that they did not volunteer, what you proposed, what they objected to, what happened. After a dozen the pattern is visible, and it is nearly always presenting too early or never asking.
Where this leads
Technical people who can sell are rare and are paid accordingly, because the combination is hard to assemble from either direction: teaching a salesperson to be credible about the technology takes years, and teaching a technician seven phases and six closes takes a season. The route from here runs through pre-sales and consulting, and it is the same route by which most people in this industry end up deciding what gets built rather than building it.
What the gear actually looks like
Every device named in this book, in one place. Recognition is the whole point of Chapter 4 — use this page to attach a picture to each name before you meet it on a dock at six in the morning.
Find the destination.
Work along the path between them.