Technical Presentation Tips for Sales Engineers

Anika had the room. Twenty-five minutes into her technical presentation on a new pump line, the plant engineer was leaning forward and procurement had asked about lead times, which is as close to a yes as procurement gets. The committee asked 14 questions. She answered nine and promised to follow up on five. By the time she reached her car, she could remember two. (Anika is a composite, not a real person.)

Her follow-up email went out the next morning with two answers. The plant engineer replied with one line: "What about the seal life at 90 °C?" He'd asked it in the room. He now believed she hadn't listened.

If you've presented to an engineering buying committee, you know the problem. A technical presentation isn't a lecture. It's a conversation where the questions are the point, and you're the only person in the room who can't write them down. This guide covers how to prepare a technical presentation for a committee or a plant floor, a 30-minute structure that works, and a question log that gets every question into the follow-up.

What a technical presentation has to do in a sale

A technical presentation sits between two formats you probably already run. A product demonstration proves the machine does the job. A manufacturing plant tour proves you can build it. The technical presentation proves it fits their plant: their flows, their utilities, their standards, their maintenance crew.

That's why the room is full of people who disagree about what matters. A typical committee includes:

• The plant or process engineer, who wants the numbers and will check them.
• The maintenance manager, who wants to know what breaks and how long it takes to fix.
• The operations lead, who wants to know what changes on the shift.
• Procurement, who wants lead time, terms and a reason the cheaper option is worse.
• Safety or quality, who wants certifications, guarding and documentation.

Each seat asks a different kind of question, and each question is a piece of the deal. IEEE Spectrum's advice to technical presenters is to adjust depth and terminology to each group, because "one size does not fit all in presentations". For a sales engineer that means one presentation with five audiences.

Prepare the technical presentation around the room's questions

Start with one sentence: At the end of this presentation, the committee agrees to ____. A trial at their plant. A spec-in on the next project. A budgetary quote with a named champion. Engineers Ireland's guide to presenting technical information says it from the audience's side: "it is your job to figure out WHY the audience cares about the information you're presenting". If a slide doesn't move the room toward that sentence, cut it.

Then do the homework the engineers have already done: their RFQ, their site standards, the spec sheet of whatever you're replacing. Our guide to selling to engineers has 15 spec questions to ask before you build a slide; the answers become your opening numbers.

Three preparation habits that pay off every time:

1. Lead with the conclusion. IEEE calls it BLUF, bottom line up front. Slide two says what you recommend and the three numbers behind it, so engineers spend the next 25 minutes testing the claim instead of waiting for it.
2. Predict the questions by seat. Write the three questions each person is most likely to ask, and decide now whether the answer is on a slide, in your head or still with your applications team.
3. Bring the data in their units. The SPE's hints for presenting technical papers recommend showing single values in both unit systems. Gallons per minute to a plant that thinks in cubic meters per hour is a question you created for yourself.

Want the questions written down while you're still answering them? Try ParrotNotes free and record your next technical presentation with the room's consent.

A 30-minute technical presentation structure

Thirty minutes is the slot most committees give, and the SPE's rule of about one slide every three minutes puts you at roughly 10 slides. This structure leaves a third of the time for questions, the part that sells.

Two rules for the slides. A slide is a chart, a drawing or three numbers, never a paragraph. And every number carries its source and conditions: "92% efficiency" invites a fight, while "92% at 1,450 rpm on water at 20 °C, our test bench, March 2026" invites a follow-up question.

Keep the questions slot sacred. If you're running long, cut the commercial section, not the questions. A committee that didn't get to ask will ask by email, slowly.

Presenting on the plant floor without slides

Half of a sales engineer's technical presentations happen beside the line, with ear protection, a forklift reversing somewhere and a maintenance tech who has ten minutes before a changeover.

Priya sells conveyor drives. Her plant-floor version is ten minutes long with no slides. (Priya is a composite.) She prints one page: the layout on their drawing, three numbers, the lead time. She stands where the new drive would mount, points, and asks before she tells: "What would you want to be different about swapping this?" The tech's answer, "the motor side faces the wall, so we pull the whole unit," becomes the first line of her follow-up and a change to the mounting she quotes.

Plant-floor rules that work:

• Shorten everything by half and keep the numbers.
• Put the one-page handout in their hands, not on a screen.
• Ask the operator and the maintenance tech before you tell them.
• Debrief within ten minutes, in the parking lot if you have to, because the detail goes fast.

Capture every question asked during the technical presentation

Here's the part most technical presentation advice skips: the questions are the output. They're the objection list, the open spec list and the skeleton of your follow-up email. And you can't write them down, because you're the one talking.

The question log

Sort every question the room asks into one of five types. The type tells you what the person is really asking.

A spec question you can't answer is normal. A spec question you forget is a lost deal. That's what the "park it" script is for.

The "park it" script

When you don't have the answer, say so in a way that records the question and buys you a date:

• "Good question. I don't want to guess at seal life at 90 °C. I'll park it and come back to you by Thursday."
• "Can I check who owns that number on your side, so I send it to the right person?"
• "Let me make sure I've got it: inlet at 90 °C, continuous, with the glycol mix. Is that your worst case?"

Three sentences, and the question has an owner, a condition and a deadline. Our sales engineer guide has the read-back script for the reverse situation, when the customer is giving you requirements.

Record the room, then rebuild the log

The simplest way to keep every question is to record the presentation. Ask first, every time: "Do you mind if I record this so I get your questions right?" Recording rules vary by state and country, so read our guide to one-party consent states and follow the site's phone and NDA rules. If anyone says no, a colleague writes.

With consent, ParrotNotes turns the recording into the log for you. Start it on your phone, lock the screen and put the phone on the table; there's no bot, because the conversation is in the room. Afterwards you get the transcript, a summary and action items, and you can ask the recording "What did the maintenance manager ask about seal life?" to get the exact wording back. Anika's five parked questions would have been five lines in the summary before she reached the parking lot.

The Free plan includes 100 minutes of recording a month, a summary on every recording and 5 AI-powered recordings for the action items and questions. Pro ($19.99/month, or $14.99/month billed annually) adds 3,000 minutes a month, speaker identification so the log shows who asked what, and 99+ languages with translation for plant teams that work in Spanish while your engineers read English. Download ParrotNotes free and let the recording keep the log.

Technical presentation mistakes that lose engineers

1. Answering a failure question with "it doesn't." Every machine fails. The maintenance manager wants to know how, how you'll know and how long the swap takes.
2. Showing data without conditions. A number with no test conditions is an adjective with a decimal point.
3. Running over into the questions. "We're out of time, email me" is the most expensive way to save five minutes.
4. Forgetting what was asked. The question missing from the follow-up is the one the engineer remembers.

After the presentation: answer in the order they asked

Rafael sells industrial chillers. After a 30-minute presentation to a food plant's committee, his recording gave him 11 questions: four spec, two failure, two integration, two proof and one commercial. (Rafael is a composite.) He'd answered seven in the room and parked four. His follow-up email, sent that afternoon, used the log as its structure:

• Answered in the room (for the record): the seven questions, each with its number and conditions.
• Parked, with dates: "Compressor life at 35 °C ambient with your glycol mix: our applications team confirms by Thursday." "PLC protocol: Modbus TCP, I/O list attached."
• Proof requested: the reference plant the maintenance manager asked for, with a contact name and a proposed call date.
• Next step: the trial the commercial question pointed to, with a window.

The plant engineer replied in 20 minutes, not with a new question but with a date. Rafael never had to say "as I mentioned," because the email proved he'd listened.

Give the presentation, keep the questions

A technical presentation for a buying committee is a conversation with five audiences, and the questions they ask are worth more than the slides you show. Prepare around the outcome sentence, lead with the bottom line, show numbers with their conditions, and keep a third of the slot for questions. Then capture every question, park the ones you can't answer with an owner and a date, and write the follow-up in the order the room asked.

Your next technical presentation is the place to start. Download ParrotNotes free, ask the room's permission and let the recording keep the question log while you keep the room.