Modern Selling: How Techs Can Be a Salesforce Multiplier

In my first sales job, working alongside field technicians and engineers, I witnessed two extremes: One technician talked at 300 words per minute, trying to be a salesperson; another retreated so far into his introverted shell that he actively damaged client relationships.

Both were capable people – just completely untrained in how to communicate with customers. The results were predictably bad.

In the system integration world, the most client-facing people aren't salespeople at all – they are often technicians, project managers, and engineers constantly on the phone, walking customers through issues, managing project timelines, and commissioning systems. That said, most companies invest almost nothing in teaching them how to handle those moments effectively.

System integrators who invest in the communication skills of their entire client-facing workforce don't just reduce complaints – they build the kind of reputation that earns referrals and lasting relationships. The good news: Technical professionals are already built for great client communication. Here are six principles that matter most:

1. Set clear expectations. Technical team members should never be expected to sell, and that message needs to be explicit; however, they do need to know what is expected – something as simple as mentioning a cloud solution that could reduce service calls or noting that your company also handles fire alarm services.

2. Overcommunicate. What feels like a normal amount of communication to a technical person often falls short of what clients need to feel confident. If a customer is expecting an update by Thursday and there's nothing new to report, most technicians go silent because it feels illogical to call with no news. Teach your people to call anyway. Let the customer know you're on top of it. That call matters more than the update.

3. Listen before you explain. Technical professionals are wired to solve problems the moment they identify them, but the problem rarely surfaces at the start of a conversation, and clients rarely feel heard when an answer comes too quickly. Train your team to pause, ask open-ended questions, and ask "why?" often. Role-playing exercises work well here – technical people tend to tolerate them better than salespeople do.

4. Translate technology into outcomes. Technical professionals default to feature-based language because that's how they think, but clients don't share that vocabulary and shouldn't have to. Instead of explaining bandwidth thresholds, talk about whether their video will buffer during a presentation. Instead of discussing cable categories, talk about whether the infrastructure will support their plans two years from now. Bridging technology to everyday impact is the single most powerful communication skill a technician or PM can develop.

5. Own bad news early. Delays, unexpected costs, and scope changes are realities in system integration. How your team communicates those moments defines the client relationship more than almost anything else. Teach them a simple structure: "Here's what happened, and here's what we're doing about it." Clients can handle setbacks; what they can't handle is feeling like they were the last to know.

6. Match the client's communication style. Some clients want a two-sentence update. Others want documentation and a full walkthrough. Ask early: "How do you prefer to stay updated, and by what method?" It's a simple question that signals professionalism and prevents friction throughout the project.