Work With a Technology Buyer Who Wants Email Only
Respect a buyer’s preferred channel while learning whether email is enough for the decision.
The buyer moment
A prospect refuses meetings and asks all questions by email.
Email can be a legitimate preference, especially when a buyer needs written answers for an internal review. Answer each question directly, label assumptions, and state which document supports the response. If a question needs a live technical review, explain the risk or ambiguity it would resolve and let the buyer choose the channel. For example, an architecture diagram may require the buyer to confirm a data flow. An optional 15 minute validation session can save rework while leaving the buyer in control of the channel. Keep the written thread organized so a new stakeholder can see exactly which question each answer addresses.
A useful way to open
“I am happy to answer in writing. Which decision are you trying to make from these answers?”
Move the decision forward
Email can be efficient, but complex questions may hide assumptions. Do not force a call; make written answers complete and identify when a live review would reduce risk.
Coach reps to use concise, structured responses and to label assumptions.
Practice before the next call
Practice replying to a technical email with five parts without slipping into vague marketing language.
Next step
Answer the written questions, then offer an optional 15 minute validation session for the riskiest item.
Practice these next
Frame a first conversation around an operating decision the CFO recognizes.
Give a useful answer without pretending all technology pricing is identical.
Carry forward the buyer’s language so the first AE call feels like progress.
Use comparison requests to uncover the decision criteria behind the checklist.
Earn a reply with a plausible operating question that relates to the buyer’s work.
Choose a next step that matches the uncertainty uncovered in the call.