Many beginners become nervous around technical people.
They think the engineer is waiting to expose them. Sometimes that fear makes them talk too much. They use words they do not understand. They nod through details. They promise to send a quote before they know what is being quoted.
There is a better way.
Respect beats performance
Technical people usually do not need you to be the smartest person in the room. They need you to avoid wasting their time.
That means:
- Listen carefully.
- Write down exact terms.
- Ask what you do not understand.
- Repeat the requirement back.
- Separate confirmed facts from assumptions.
- Bring the right specialist into the conversation.
This is not weakness. It is professionalism.
Use clarification questions
If a buyer mentions a valve, ask for the datasheet, size, class, material, end connection, quantity, and standard requirement.
If they mention calibration, ask for the equipment list, ranges, due dates, location, certificate requirement, and whether ISO/IEC 17025 accreditation is needed for that scope.
If they mention HSE training, ask for the topic, participant count, site, certificate format, and client requirement.
If they mention API or ASME, ask which standard, which edition, and what proof is expected.
You are not pretending to know. You are making the request clearer.
The sentence that protects you
"I do not want to guess on that. Let me confirm with the technical team and come back with the correct answer."
That sentence can save your reputation. It also tells serious people that you understand the consequences of careless answers.
Why the book teaches this early
The Cookbook repeats one rule in many forms: do not pretend.
That is not just moral advice. It is a sales strategy. When buyers see that you verify instead of bluffing, they are more likely to trust you with the next question.
You can be a beginner and still be professional. The difference is discipline.