Engineering Language for Sales

Section 01

How Engineers Communicate

Engineers communicate in specifications, not descriptions. Where a client might say "we need a big pump," an engineer says "we need a piston pump rated at 80 m³/hr at 120 bar with 150mm DN discharge flange." Every word carries a precise meaning. Every number is a constraint. Imprecision is not vagueness — it is a technical error.

When you speak with an engineer, your credibility depends not just on knowing the right answer, but on framing it correctly. An engineer who hears you say "the machine is very powerful" immediately questions your technical authority. An engineer who hears you say "the main mixer motor is rated 75 kW at 1,475 RPM with IE3 efficiency class" knows they are talking to someone who understands the product.

The Precision Spectrum

              "Big" / "Strong" / "Good"
            

— no engineering meaning

              "High capacity" / "Powerful motor"
            

— vague, needs context

              "120 m³/hr at 350 bar, 75 kW"
            

— engineering language ✓

Three Principles of Engineering Communication

1. Always include units. "120" means nothing. "120 m³/hr" is a specification.

2. Distinguish rated vs actual. "Rated at 150 kW" and "drawing 150 kW" are different facts.

3. State conditions. "80 m³/hr" — at what pressure? At what slump? Under what operating conditions?

          Signal quality of communication
        

            VAGUE
          

"It's a very good machine"

            PRECISE
          

            75 kW · 1475 RPM · IE3
          

Real Dialogue — Engineer Evaluating a Batching Plant Offer

👷

Site Engineer — Al-Rashid Construction

We need a batching plant for the Beirut project. We have C35 concrete, a peak pour rate of 55 m³/hr, and the site power supply is limited to 250 kVA. What can you offer?

❌

Salesperson — Weak Response

We have a really good batching plant that can handle all that. It's very powerful and many clients are using it. I'll send you a brochure.

✗ No numbers. No acknowledgement of constraints. Zero engineering credibility. The engineer will not respond.

✓

Salesperson — Strong Response

For a 55 m³/hr peak with C35, I'd recommend our MB-750 with a 1.5 m³ twin-shaft mixer — theoretical output is 72 m³/hr, net approximately 58–62 m³/hr at an 85% efficiency factor. Total installed power is 195 kW, well within your 250 kVA supply. The running load under full production is approximately 145 kW. Can you confirm the aggregate moisture content and maximum aggregate size? That affects the mix cycle time and I want to make sure the throughput calculation holds.

✓ Numbers match the requirement. Efficiency factor disclosed honestly. Questions show understanding. Power confirmed within site constraint.

Section 02

Key Engineering Terms a Salesperson Must Master

These are the six terms that appear in almost every technical conversation about construction equipment. Master the definition, the unit, and — most importantly — how to use each one in a sentence.

Capacity / Flow Rate

m³/hr · L/min · t/hr · m³/batch

The volume or mass of material processed per unit of time. For batching plants: m³/hr. For pumps: L/min or m³/hr. For crushers: t/hr. Always ask: capacity at what pressure? At what efficiency?

✓ "This pump delivers 60 m³/hr at 80 bar."
✓ "The plant has a theoretical capacity of 90 m³/hr, net approximately 72 m³/hr."
✗ "It can produce a lot."

Pressure

bar · MPa · psi (1 bar ≈ 100 kPa ≈ 14.5 psi)

Force per unit area. In hydraulic systems: 200–350 bar working pressure. In concrete pumps: 50–200 bar at the pump outlet. In pneumatic systems: 6–10 bar. Always distinguish working pressure from maximum rated pressure.

✓ "Working pressure: 200 bar. Safety relief set at 250 bar."
✓ "The pump maintains 120 bar at 50 m³/hr."
✗ "High pressure system."

Power

kW (kilowatts) · HP (1 HP ≈ 0.746 kW)

The rate of energy consumption or output. Motor ratings are in kW. Total plant power is in kW. Generator sizing is in kVA (kVA = kW ÷ power factor, typically 0.8). Always separate installed power from running power.

✓ "Mixer motor: 75 kW. Total installed: 195 kW. Running load: ~145 kW."
✓ "Generator required: 145 ÷ 0.8 = 181 kVA minimum — specify 200 kVA."
✗ "It uses a lot of electricity."

Torque

N·m (Newton-metres) · kN·m

Rotational force. A mixer with high torque can handle thick, dry mixes that would stall a lower-torque machine. Crane hoist motors are specified by both power (kW) and torque (N·m). Torque and speed are inversely related at constant power.

✓ "The mixer drive produces 18,000 N·m at the output shaft — critical for zero-slump mixes."
✓ "The gearbox converts 1,450 RPM / 75 kW to 14 RPM / 48 kN·m at the drum."
✗ "Very strong mixer."

Load / Force

kN · tonnes (1 tonne ≈ 9.81 kN)

The weight or force applied to a structure or machine. Crane capacity is in tonnes. Foundation bearing is in kN/m² or t/m². Anchor bolt tensile capacity is in kN. Always add self-weight of rigging to the suspended load.

✓ "The crane's rated capacity at 25 m radius is 8.2 tonnes."
✓ "With 400 kg of rigging, the net payload is 7.8 tonnes."
✗ "It can lift heavy things."

Efficiency

% · ratio (0–1)

The ratio of useful output to total input energy or production. Motor efficiency: 92–97%. Gearbox efficiency: 94–97%. Batching plant efficiency: 75–85% of theoretical. Always apply efficiency when converting theoretical to real-world output — failure to do so creates undeliverable promises.

✓ "Theoretical 90 m³/hr × 82% efficiency = 73.8 m³/hr net output."
✓ "IE3 motor at 94.5% efficiency vs IE1 at 91% — saves ~2.6 kW per 100 kW installed."
✗ "It's very efficient."

      Quick Unit Conversions — Memorise These
    

          1 bar
        

          = 100 kPa
= 14.5 psi
≈ 10 m water head
        

          1 kW
        

          = 1.34 HP
kVA × 0.8 = kW
P = V × I × √3
        

          1 tonne
        

          = 1000 kg
= 9.81 kN
≈ 10 kN (practical)
        

          1 m³/hr
        

          = 16.7 L/min
= 0.000278 m³/s
÷ 3600 = m³/s
        

Section 03

How to Ask the Right Technical Questions

The quality of your questions determines the quality of your specification. A client who says "we need a concrete pump" has told you almost nothing. A well-structured question sequence extracts the information needed to specify correctly and avoid errors.

Five-Step Client Requirement Discovery

1

What

          What material?
What process?
What output?
        

2

How Much

          Volume/hr?
Total volume?
Peak demand?
        

3

Where

          Site dimensions?
Access width?
Height limit?
        

4

What Power

          Grid or genset?
Available kVA?
Voltage: 380/415V?
        

5

When & How Long

          Project duration?
Daily hours?
Start date?
        

Sentence Templates for Requirement Discovery

Opening — Establishing Requirements

"Before I recommend a configuration, can I confirm a few technical parameters?"

"What is the target output in m³/hr, and is that the average or the peak pour rate?"

"What concrete grade are you producing — is C30 the minimum, or do you have higher-grade requirements?"

These three questions alone eliminate 80% of specification errors. Note that you are not asking "what do you need?" — you are asking for specific numbers.

Clarifying Site Constraints

"What is the available electrical supply? Grid connection or generator — and what is the available kVA?"

"What is the maximum vehicle access width, and the road load limit for delivery trucks?"

"Are there environmental constraints — noise curfews, dust limits, or proximity to residential areas?"

Clarifying Unclear Requirements

"You mentioned you need a 'big' plant — can you help me understand the peak hourly demand? That's the key number for sizing."

"When you say the pump needs to 'reach the top floor' — what is the vertical height in metres, and the horizontal run from the pump position?"

"Just to confirm: is the 60 m³/hr the output you need at the pump discharge, or is that the target at the pour location? There's a pipeline loss factor between the two."

Section 04

How to Explain Equipment in Technical Terms

Translating equipment features into engineering value is the core of technical sales. Every specification has a meaning that matters to the client. Your job is to make that connection explicit — not to recite a datasheet, but to explain why each number matters for the client's specific project.

✗ Before — Weak Description

"This batching plant has a twin-shaft mixer and a good control system. It's made of high-quality steel and many clients are using it in Nigeria and Lebanon."

✗ No numbers. No engineering value. No connection to client's project.

✓ After — Technical Explanation

"The twin-shaft mixer produces 1.5 m³ per 60-second cycle — that's a net output of 72 m³/hr at 80% efficiency. The S355 steel mixing arms carry a 12mm Hardox liner, giving a wear life of 300,000 m³ on standard aggregate before replacement."

✓ Cycle time, output, efficiency, material grade, liner specification, wear life — all in one sentence.

✗ Before — Feature Without Value

"It has a variable frequency drive on the conveyor motor."

✗ States the feature. Does not explain why it matters to the client.

✓ After — Feature Linked to Value

"The conveyor uses a VFD-controlled 22 kW motor. That means you can ramp aggregate feed from 0 to full speed in 8 seconds without the 140A starting surge that would trip a DOL-connected motor on a 250 kVA supply — which is exactly what your site is limited to."

✓ Feature → engineering mechanism → specific benefit for this client's constraint.

✗ Before — Comparing Brands Vaguely

"Our machine is better quality than the Chinese option. You get what you pay for."

✗ Sounds defensive and unprofessional. No technical substance.

✓ After — Technical Comparison

"The alternative uses a 10mm standard cast liner. Our mixing arm carries a 12mm Hardox 400 liner — that's a 30% longer wear life and approximately 80,000 m³ more production before the first liner change. At your target output, that's an extra 14 months of operation before a planned shutdown."

✓ Specific dimensions, material grade, quantified advantage, translated to operational impact.

How to Translate Specifications into Client Value

Section 05

How to Read and Respond to Technical Requests

Reading an RFQ (Request for Quotation)

An RFQ is a formal document describing what a client wants to buy. When you receive an RFQ, your first job is to identify: what is specified, what is missing, and what looks technically inconsistent. Do not quote before checking all three.

Sample RFQ — Concrete Batching Plant — Lagos Infrastructure Project

Required output60 m³/hr

Concrete gradeC35 / C40

Max aggregate size32 mm ✓

Cement silo capacity100 tonnes ⚠ — check: 60 m³/hr at 350 kg cement/m³ = 21 t/hr — only 4.7 hours of autonomous operation

Electrical supply150 kVA ⚠ — CONFLICT: 60 m³/hr plant needs ~180 kW installed / 200+ kVA

Site footprint available30m × 20m ✓

Control systemPLC with recipe management, batch reporting

Mixer typeDrum mixer ⚠ — C40 with 32mm aggregate requires twin-shaft for consistency

Delivery required16 weeks from order

⚠ = requires clarification before quoting ✓ = confirmed adequate flag = technical conflict — must raise with client

📋

How to Respond to a Conflicting RFQ

Never quote an RFQ that contains conflicts without raising them. The correct response is a Technical Clarification Letter — not an email saying "we cannot quote this." Structure it as: "We have reviewed your RFQ and wish to raise the following technical points before submitting our quotation…" Then list each conflict with the specific numbers, explain the consequence, and propose the correction. This approach demonstrates technical competence and protects both parties from a failing contract.

Responding to an RFQ — Power Conflict Example

"Your RFQ specifies 150 kVA electrical supply. Our 60 m³/hr configuration has a total installed load of 195 kW, with a running load of approximately 145 kW. At a power factor of 0.85, this requires a minimum supply of 171 kVA. We recommend either upgrading the supply to 200 kVA or configuring the plant with soft starters on the larger motors to remain within 150 kVA — at a 10–15% reduction in production rate. Please advise which approach your project requires."

This response identifies the conflict, quantifies it precisely, and offers two solutions with their trade-offs. The client can make an informed decision.

Section 06

Common Communication Mistakes

⚠ Mixing Units

Quoting flow in m³/hr but pressure in psi. Saying "tonnes" when you mean "kN." Mixing kW and kVA without distinguishing them. Engineers notice immediately and lose trust in everything else you say.

✗ "The pump delivers 1000 litres and 200 bar pressure."
✓ "The pump delivers 60 m³/hr at 200 bar working pressure."

✗ "The crane lifts 10,000 kgs at that distance."
✓ "The crane's rated capacity at 20 m radius is 10 tonnes."

⚠ Overpromising Performance

Quoting theoretical capacity as deliverable output. Saying a pump "reaches 300 metres" without specifying that this is the maximum at zero flow. Promising a delivery date without confirming manufacturing lead time.

✗ "This plant produces 90 m³/hr."
✓ "Theoretical output: 90 m³/hr. Net at 82% efficiency: ~74 m³/hr."

✗ "The pump can reach your top floor."
✓ "At your floor height of 55m and pipeline run of 80m, the pump operates at ~60 bar — within the 80 bar working pressure rating."

⚠ Using Incorrect Terminology

Calling a twin-shaft mixer a "drum mixer." Saying "horsepower" when all specs are in kW. Saying "tons" when you mean "tonnes" — these are different units. Saying "load" when you mean "torque."

✗ "The motor is 100 horses." (correct: 75 kW)
✗ "Short tons vs metric tonnes — 1 short ton = 0.907 t"
✗ "High load on the shaft" (correct: high torque)
✗ "Cylinder diameter" for a hydraulic pump (correct: bore or piston diameter)

⚠ Not Understanding the Application

Recommending a squeeze pump for a high-pressure long-distance pour. Recommending a drum mixer for C40 concrete. Recommending a mobile crane for a continuous lifting programme. These errors emerge from quoting equipment without understanding what the client is trying to do.

✗ Selling a 90 m³/hr plant to a client whose peak pour is 35 m³/hr
✗ Specifying a 2-pole motor (3000 RPM) where a 4-pole (1500 RPM) + gearbox is required
✗ Omitting the outrigger spread requirement from the crane specification
✗ Not asking about cement type when specifying silo venting

Section 07

Converting Technical Language into Sales Value

The final translation step: once you have established technical credibility, you convert specifications into business outcomes — productivity, profitability, and risk reduction. This is where the sale is made.

Spec → Productivity

          EXAMPLE
        

"Our plant produces 74 m³/hr net. At your pour schedule of 8 hours/day, that's 592 m³/day — meaning your 15,000 m³ project completes in 26 working days instead of 33 with the lower-capacity option."

          7 days × (your daily overhead cost) = money saved
        

Quality → Durability

          EXAMPLE
        

"The Hardox 400 liner has a wear life of 350,000 m³ vs 220,000 m³ for the standard option. At your production rate, that's 14 months vs 9 months between shutdowns — one fewer planned shutdown per year."

          Fewer shutdowns = more uptime = more revenue
        

Design → Reliability

          EXAMPLE
        

"The dual redundant PLC I/O means if one output card fails, the standby card takes over in under 200ms — the mixer continues without interruption. The alternative uses a single PLC without redundancy."

          Unplanned downtime on a live pour = project delay
        

Value Conversion Sentence Templates

"That [specification] means [engineering mechanism], which translates to [operational impact] for your project."

"At your [daily/weekly production target], the [X% efficiency advantage] saves you [Y hours/days/m³] per [period]."

"The [component] is rated for [life/cycles/hours]. At your [operating rate], that's [calendar time] before the first planned maintenance — versus [competitor's figure]."

"The price difference between these two configurations is [amount]. The daily operating cost difference from the [efficiency/capacity/downtime] advantage is [amount/day]. Payback period: [days]."

Section 08

Handling Technical Objections

"The Chinese option is 40% cheaper. Why should I pay more for yours?"

This is not a price question — it is an invitation to justify value. Do not defend your price; quantify the difference in total cost of ownership over the life of the equipment.

"The acquisition cost is higher, but let's compare over 10 years of operation. Our mixer liner lasts 350,000 m³ vs 200,000 m³ — that's one fewer liner change per 5-year cycle. At $18,000 per liner set including downtime, that's $18,000 back. Our IE3 motors save approximately $4,200/year in electricity versus the IE1 motors in the competing offer. Over 10 years: $42,000 in energy savings. The total cost difference over the asset life is [your calculation]. That's the correct comparison."

Key: always convert the comparison to the same timeframe and same basis. One-time price vs 10-year total cost is not a fair comparison — and the client knows it if you point it out.

"Your plant is rated 90 m³/hr but we only need 60. Why can't we take the smaller model?"

A sizing question that requires you to demonstrate your understanding of the project rather than the catalogue. Never concede to downsizing without checking the peak demand carefully.

"You're right that your average production is 60 m³/hr. But I want to check your peak pour requirement: you mentioned a 1,200 m³ mat slab in your programme. If that needs to be completed in 18 hours to avoid a cold joint, your peak rate is 67 m³/hr — above what the smaller model delivers at 80% efficiency. The 90 m³/hr plant gives you 74 m³/hr net, with 10% headroom for any delay. If the pour takes 20 hours instead of 18 due to a traffic delay, you're protected. Do you want to carry that risk for the cost saving?"

"Your competitor says their pump can reach 400 metres. Yours is only rated 300 metres. Why?"

A specification comparison that is almost certainly comparing different conditions. Maximum reach is meaningless without the accompanying flow rate.

"Maximum reach figures are always measured at near-zero flow — at the point where the pump is fighting the pipeline resistance but barely moving concrete. At 400m, their pump delivers approximately 8–12 m³/hr. Our 300m rating is at 30 m³/hr — which is what you actually need for a live pour. If you check their technical datasheet at 30 m³/hr, you'll find their effective reach drops to approximately 280 m. The 400m figure is a catalogue maximum, not a working specification. Shall I prepare a pipeline pressure calculation for your specific job?"

"We need delivery in 8 weeks. Can you do it?"

A timeline question that requires an honest technical answer, not a commercial promise. Overpromising a delivery date has destroyed more client relationships than any other single mistake in equipment sales.

"Our standard manufacturing lead time for this configuration is 14 weeks. However, let me check two things: our current factory schedule may allow us to pull forward if there is capacity, and we can confirm this within 48 hours. Second, is the 8-week requirement for the full installation and commissioning, or for equipment arrival at port? If it's port arrival, we have more flexibility because we can ship in partial loads. Let me come back to you with a specific schedule rather than a yes/no that I can't guarantee."

Lesson 11 — Engineering Terms Reference

Term / Unit	Meaning	Correct Usage in Conversation	Common Error
m³/hr	Cubic metres per hour — volume flow rate	"The plant delivers 72 m³/hr net at 82% efficiency"	Quoting theoretical without stating efficiency
bar / MPa	Pressure — 1 bar = 0.1 MPa = 100 kPa	"Working pressure: 200 bar; relief valve set at 250 bar"	Mixing bar and psi; not distinguishing working vs rated pressure
kW / kVA	kW = real power; kVA = apparent power (kW ÷ power factor)	"Running load 145 kW; at PF 0.85 = 171 kVA; specify 200 kVA generator"	Using kW and kVA interchangeably — they are not equal
N·m / kN·m	Torque — rotational force	"Mixer output shaft torque: 18,000 N·m for zero-slump mixes"	Saying "load" or "force" when torque is meant
tonnes / kN	Mass (tonnes) or force (kN); 1 tonne ≈ 9.81 kN ≈ 10 kN	"Crane rated at 8.2 tonnes at 25 m; with 400 kg rigging: 7.8 t net payload"	Short tons vs metric tonnes (1 short ton = 0.907 t)
RPM / Hz	Rotational speed / electrical frequency	"4-pole motor at 50 Hz: synchronous 1,500 RPM, rated 1,475 RPM under load"	Not specifying poles; confusing 50 Hz and 60 Hz equipment
% efficiency	Useful output ÷ total input (0–100%)	"IE3 motor: 94.5% efficiency; 100 kW input → 94.5 kW shaft output"	Not applying efficiency to convert theoretical to real output
IP rating	Ingress protection (first digit: dust, second: water)	"IP55: dust-tight and protected against water jets — appropriate for batching plant"	Specifying IP44 for outdoor motors on African or MENA sites
PCD / DN	Pitch circle diameter (bolts) / nominal diameter (pipes)	"Flange: DN150, PN16 rating, bolt PCD 285 mm, 8 × M20 bolts"	Specifying pipe by outside diameter without the DN designation

Always include units. A number without a unit is not a specification — it is a guess. "120" means nothing; "120 m³/hr at 200 bar" is a technical statement.
Distinguish theoretical from actual. Theoretical capacity × efficiency factor = real deliverable output. Never present theoretical figures as guaranteed production rates.
Ask for numbers, not descriptions. "Big pour" tells you nothing. "600 m³ in 8 hours" gives you everything you need to size the equipment.
Flag RFQ conflicts before quoting. A power supply specification that is too small for the required output is a technical conflict — quote it correctly and the client respects you; quote it silently and you own the problem after delivery.
Convert specs to value. The specification is the evidence; the value is the argument. "IE3 motors" is evidence; "saves $4,200/year in electricity for 10 years" is the argument that closes.
Never overcommit on delivery, capacity, or performance. Every overpromise destroys exactly the credibility that technical precision builds. A precisely stated limitation is more persuasive than a vague promise.
The strongest technical objection response is a calculation. When a client says "your competitor's pump reaches further," show the calculation. Numbers win arguments that words cannot.