總覽 / 示範對話

示範對話|Set 1:企業客戶需求訪談

對話 1|初次拜訪:破冰與需求探索

A = Nexchip 業務顧問|B = Orion Telecom 採購經理(友善但謹慎)

  1. A: "Thank you for making time today. Before I talk about what we do, I'd love to hear what prompted you to take this meeting." ↳ 開場不推銷,先把發言權交給對方——避開「pitch first」陷阱。
  2. B: "Well, our team has been reviewing our component suppliers this year, and your name came up. We thought it was worth a conversation."
  3. A: "I appreciate that. What prompted you to look into this now, rather than, say, six months ago?" ↳ 必用句型:探「為什麼是現在」,挖出真正的觸發事件。
  4. B: "Honestly, we've had a few sourcing hiccups recently. Nothing dramatic, but enough to make us look around."
  5. A: "That's helpful context. Could you walk me through your current setup — how you source these components today?" ↳ 必用句型:請對方帶你看現況,而不是逐項質問。
  6. B: "We work with two main suppliers — one in Korea, one domestic. The domestic one handles most of our RF modules."
  7. A: "And how is this handled today on your side — who's involved when an order goes out?"
  8. B: "Procurement raises it, network operations signs off on the specs, and finance approves anything above a certain threshold."
  9. A: "Just to make sure I understand correctly, you're saying this review is less about cost and more about supply reliability?" ↳ 必用句型:換句話說回放,當場驗證理解。
  10. B: "That's fair. Cost matters, but reliability is what got this onto my desk."
  11. A: "Understood. What challenges are you facing with the current arrangement, if you don't mind me asking?" ↳ 說 challenges,不說 "What's your problem?"——語氣差一個字,感受差很多。
  12. B: "Mainly lead-time consistency. The quotes are fine, but delivery dates slip."
  13. A: "That's useful to know. What would success look like for you six months from now, if this review goes well?"
  14. B: "A supplier bench we can actually trust — and fewer fire drills for my team."
  15. A: "That gives me a clear picture. If it's all right with you, I'd like to dig into those lead-time issues next — shall we keep going, or would a follow-up session suit you better?"
  16. B: "Let's keep going. I have some time."

Useful takeaways

  1. 前段訪談的任務是「聽」,產品留到對方講完現況與痛點之後再說。
  2. "What prompted you to… now?" 能挖出觸發事件(trigger event),那才是成交的引擎。
  3. 每聽完一段就用 "Just to make sure I understand correctly…" 回放,錯誤理解要當場修正。
  4. 問困難用 "What challenges are you facing?",避免 "problem" 帶來的質問感。
  5. 段落收尾用「成功長什麼樣?」(What would success look like?)把對話從抱怨導向目標。

對話 2|深挖痛點:量化現況的代價

A = Nexchip 售前顧問|B = Orion Telecom 網路營運總監(講話含糊,需引導才給數字)

  1. A: "You mentioned delivery delays have been a recurring issue. Could you help me understand how often that happens, and what it costs you when it does?" ↳ 一句話同時問「頻率」與「代價」,為量化鋪路。
  2. B: "It's hard to say. Sometimes it's fine for months, and then everything slips at once."
  3. A: "How often does that happen, roughly — once a quarter? Once a month?" ↳ 必用句型+技巧:給選項式區間,幫含糊的人開口估數字。
  4. B: "Probably… two or three times a quarter, if I'm honest."
  5. A: "Can you give me a recent example of when this went wrong?"
  6. B: "Last month a base-station module came in nine days late. We had field crews already scheduled, and we had to reshuffle everything."
  7. A: "What's the impact on your team when that occurs?" ↳ 必用句型:從「事件」追到「影響」,層層往商業代價推。
  8. B: "Overtime, mostly. And the rollout team misses their site targets — which then becomes my problem."
  9. A: "Have you been able to put a number on that — in hours or dollars?"
  10. B: "Not precisely. Maybe forty to sixty crew-hours per incident, plus penalty exposure on two of our municipal contracts."
  11. A: "So conservatively — two incidents a quarter at fifty hours each — that's around four hundred crew-hours a year, before we even count penalties. Does that sound right?" ↳ 現場換算並回放數字,讓客戶「聽見」自己損失的規模。
  12. B: "When you put it that way… yes. Probably more."
  13. A: "If nothing changes, what happens over the next twelve months?" ↳ 必用句型:把痛點投射到未來,建立「不能不動」的急迫感。
  14. B: "We have a 5G expansion starting in Q2. If the delays hit that, the exposure isn't crew-hours anymore — it's the launch date."
  15. A: "That's exactly the context I needed. Rather than jumping to solutions today, I'd like to take these numbers away and come back with something concrete. Who else in the organization feels this pain the most?" ↳ 忍住不說 "We can fix that!"——先問完、記完,才有資格提解方。
  16. B: "Talk to our rollout director. She'll give you an earful."

Useful takeaways

  1. 客戶說不出數字時,給區間選項(once a quarter? once a month?)比開放式問句有效。
  2. 追問順序:頻率 → 具體案例 → 團隊影響 → 換算成時數/金額 → 未來一年的後果。
  3. 把客戶給的零散數字當場乘開回放("that's ~400 crew-hours a year"),痛感立刻具體化。
  4. 聽到痛點不急著接解方——打斷吐露等於關掉資訊水龍頭。
  5. 用 "Who else feels this pain?" 順勢拿到下一位關鍵人,痛點訪談兼做組織地圖。

對話 3|預算與決策流程:問錢不失禮

A = Nexchip 客戶經理|B = Orion Telecom 財務暨採購副理(習慣反問報價來迴避)

  1. A: "To make sure we propose something realistic, may I ask how this initiative is being budgeted on your side?" ↳ 用「為了提案務實」當理由問錢,給對方台階。
  2. B: "Why don't you tell me your pricing first? Then I'll tell you if it fits."
  3. A: "That's fair — and I promise you'll get real numbers from us. But the price depends heavily on scope, so may I ask a few more questions first?" ↳ 陷阱破解:被反問報價時不急著報數字,守住訪談主導權。
  4. B: "All right, go ahead."
  5. A: "Is there a budget range you're working within for this fiscal year?" ↳ 必用句型:問 range,不問 "How much money do you have?"。
  6. B: "There's an allocation for supplier diversification. I can't share the exact figure."
  7. A: "Understood — no exact figures needed. Would it be fair to say it's a six-figure initiative rather than a seven-figure one?" ↳ 對方不肯給數字時,改用量級(six-figure/seven-figure)降低敏感度。
  8. B: "Six figures. For the pilot phase, at least."
  9. A: "That helps a lot. Is this budgeted for this fiscal year, or would it need a new approval?"
  10. B: "The pilot is covered this year. A full rollout would go into next year's cycle."
  11. A: "Who else would be involved in the final decision?" ↳ 必用句型:把決策鏈問清楚,提案才寄得到對的人手上。
  12. B: "Myself, the network operations director — and anything beyond the pilot goes up to our CFO."
  13. A: "And what does your internal approval process typically look like — roughly how long from proposal to signature?"
  14. B: "For a pilot, four to six weeks, if the paperwork is clean."
  15. A: "Last one on this topic, I promise: if the business case is strong, is there flexibility in that range?"
  16. B: "If the ROI story holds, there's always a conversation to be had."

Useful takeaways

  1. 問預算永遠問 range/allocation,不問對方「有多少錢」。
  2. 被反問「你們多少錢」時,先承諾會給實價,再用 "That depends on scope" 換回提問權。
  3. 對方守口如瓶時,退一步問量級(six-figure or seven-figure?)——多數人願意點頭或搖頭。
  4. 預算三件套要問齊:金額範圍、屬於哪個年度、走什麼簽核流程。
  5. 收尾補一句「如果商業效益夠強,範圍有彈性嗎?」,為超出預算的提案預留空間。

對話 4|技術需求訪談:規格與整合細節

A = Nexchip 客戶經理(非工程背景,主導訪談)|B = Orion Telecom 資深網路架構師(術語多、語速快)

  1. A: "I'd like to capture your technical requirements accurately, so please stop me if I oversimplify anything. Could we start with your current architecture?" ↳ 先自我定位:我不是工程師,但我負責把需求記對——反而建立專業感。
  2. B: "Sure. We run a distributed RAN with fronthaul over eCPRI, and our OSS stack polls inventory over NETCONF/YANG. Any component you supply has to expose telemetry into that pipeline."
  3. A: "Could you clarify what you mean by 'expose telemetry into that pipeline' — is that about feeding real-time monitoring data into your system?" ↳ 必用句型:聽不懂當場問,絕不裝懂點頭——記錯需求的代價遠大於發問。
  4. B: "Exactly. Temperature, error counts, firmware version — streamed, not batch."
  5. A: "Got it. Is streamed telemetry a must-have or a nice-to-have for the pilot phase?" ↳ 必用句型:每條規格都標優先級,提案才知道哪裡不能省。
  6. B: "Must-have. Batch reporting is what killed our last vendor evaluation."
  7. A: "Noted as a hard requirement, then. What systems would this need to integrate with, and via what interfaces?"
  8. B: "Our NMS, over NETCONF. And the security team will want your module hardened to our internal baseline."
  9. A: "On that point — are there any compliance or security standards we need to meet?"
  10. B: "NESAS compliance, and everything goes through our internal penetration test before field trial."
  11. A: "I want to be straight with you: rather than promise NESAS on the spot, let me confirm our current certification status with our engineering team and get back to you by Friday." ↳ 陷阱破解:做不到或不確定的規格,不說 "No problem",改給「查證+明確回覆日」。
  12. B: "Appreciated. Vendors who say yes to everything are the ones that worry me."
  13. A: "What's your expected timeline for testing and deployment?"
  14. B: "Lab validation in about eight weeks, field trial next quarter."
  15. A: "Let me summarize the requirements so far to make sure nothing is missed: streamed telemetry — temperature, error counts, firmware — into your NETCONF pipeline as a must-have; NESAS compliance plus your internal pen test; and lab validation within eight weeks. Did I capture that correctly?" ↳ 必用句型:口頭彙整全部需求,請對方確認。
  16. B: "That's the list. Put it in writing and I'll countersign it."

Useful takeaways

  1. 非技術背景主持技術訪談,開場先說「請隨時糾正我的簡化」,把弱點變成流程優勢。
  2. "Could you clarify what you mean by…?" 是專業,不是丟臉;裝懂才會在提案階段爆炸。
  3. 每條規格都追問 must-have or nice-to-have,拿到的是有優先級的需求清單而非願望清單。
  4. 不確定能否做到的規格,回覆公式=「我與工程團隊確認+星期五前回覆」,永不空頭承諾。
  5. 訪談尾聲完整複誦需求清單並請對方確認,最好再落成文字讓客戶會簽(countersign)。

對話 5|訪談收尾:摘要確認與下一步

A = Nexchip 業務顧問|B = Orion Telecom 採購經理(趕下一個會,想用「先寄資料」打發)

  1. A: "We're coming up on time, so let me quickly recap what I've heard today and confirm our next steps." ↳ 主動收束會議,收尾權不能交給趕時間的對方。
  2. B: "Can you make it quick? I have another call in five minutes."
  3. A: "Two minutes, I promise. To recap, your top three priorities are: lead-time reliability ahead of the Q2 5G expansion, streamed telemetry into your existing NMS, and a pilot that fits within this year's budget." ↳ 必用句型:三點式摘要——短、可核對、對齊雙方認知。
  4. B: "That's about right."
  5. A: "Did I miss anything, or is there anything you'd like to add?" ↳ 必用句型:給對方最後補充權,漏掉的需求現在撈,不要到提案才發現。
  6. B: "Just that the rollout director should see whatever you send over."
  7. A: "Noted — I'll include her. As a next step, I'd suggest a proposal review session. Shall we schedule a follow-up for next Thursday to review the proposal together?"
  8. B: "Just email me the proposal, and I'll take a look when I can."
  9. A: "I'll absolutely send it in advance so you can skim it first. In my experience, though, a thirty-minute walkthrough saves weeks of back-and-forth by email — would Thursday at ten work, or is Friday morning better?" ↳ 陷阱破解:不接受「寄來就好」;先讓步(先寄),再給兩個具體時段二選一。
  10. B: "…Thursday at ten, then. Thirty minutes, not a minute more."
  11. A: "Done — thirty minutes. Before that meeting, is there anyone else you'd recommend we include?"
  12. B: "Invite the rollout director. I'll forward you her contact after this call."
  13. A: "Perfect. And so I aim the proposal correctly — what would you need to see in it to feel confident moving forward?" ↳ 直接問「提案要長怎樣你才會點頭」,命中率最高的一題。
  14. B: "Hard delivery commitments, and the telemetry spec in black and white."
  15. A: "You'll have both. I'll send today's recap and the calendar invite within the hour. Thank you for your time — this was a very productive session." ↳ 下一步=具體動作+負責人+時限(一小時內寄 recap 與會議邀請)。
  16. B: "Good meeting. Talk Thursday."

Useful takeaways

  1. 會議最後五分鐘由你主導:recap → 確認遺漏 → 敲定下一步,一步都不能省。
  2. 摘要壓成三個優先事項,對方三十秒就能核對,趕時間也擋不掉。
  3. "I'll send you some information." 不是下一步;「週四十點、三十分鐘、一起看提案」才是。
  4. 對方說「先寄來就好」時,先答應寄,再用二選一時段(Thursday or Friday?)把會議釘下來。
  5. 散會前問 "What would you need to see in the proposal?"——讓客戶親口告訴你怎樣才會買單。

補充說明:我原本要把這份內容存到 materials/dialogues/set1-企業客戶需求訪談-示範對話.md,但寫入權限被拒,所以只呈現在這裡;下次開放寫入權限我可以直接落檔。