The Sales Japan Series cover art

The Sales Japan Series

The Sales Japan Series

By: Dale Carnegie Japan
Listen for free

About this listen

 The vast majority of salespeople are just pitching the features of their solutions and doing it the hard way. They are throwing mud up against the wall and hoping it will stick. Hope by the way is not much of a strategy. They do it this way because they are untrained. Even if their company won't invest in training for them, this podcast provides hundreds of episodes with information, insights and techniques all based on solid real world experience selling in Japan. Trying to work it out by yourself is possible but why take the slow and difficult route to sales success? Tap into the structure, methodologies, tips and techniques needed to be successful in sales in Japan. In addition to the podcast the best selling book Japan Sales Mastery and its Japanese translation Za Eigyo are also available as well.Copyright 2022 Economics Management Management & Leadership
Episodes
  • Listening Skills

    Listening Skills
    Feb 17 2026
    Listening is the most underrated sales skill because it's the one that actually tells you what the buyer is thinking, not what you wish they were thinking. Most salespeople believe they listen well, but in real conversations—especially under pressure—we drift into habits that feel like listening while we're actually rehearsing our next line. In Japan, in the US, in Europe—whether you're selling to an SME, a startup, or a multinational—buyers can feel when you're not fully present. Are you really listening to the buyer—or just waiting to talk? Most salespeople aren't listening; they're mentally queuing up their next point, and the buyer can hear the delay. This shows up in every market: a SaaS rep in San Francisco, a relationship banker in London, or an account manager in Tokyo can look attentive while their mind is sprinting ahead. The trigger is usually one "important" phrase—budget, competitor, timing—then your attention snaps away from the buyer and into your internal monologue. You're still hearing, but you're not taking in. That gap matters because buyers don't only communicate in words. In executive-level meetings at firms like Toyota or Rakuten, meaning often sits inside tone, pace, hesitations, and what goes unsaid. Post-pandemic, with more hybrid calls on Zoom or Teams, these cues are easier to miss—unless you deliberately train for them. Do now: Treat every buyer conversation like a live intelligence feed: if you're writing your reply in your head, you've stopped listening. What are the five levels of listening in sales? There are five levels—Ignore, Pretend, Selective, Attentive, and Empathetic—and most sales calls hover around levels 2 or 3. Ignore doesn't mean staring at your phone; it can mean being hijacked by your own thoughts the moment the buyer says something provocative. Pretend looks like nodding, eye contact, "mm-hmm"—but your brain is busy building the pitch. Selective listening is the killer in modern B2B: you filter for "yes/no" buying signals, but you miss the conditions attached to them (timeline, stakeholders, risk concerns). Attentive listening is full-focus: no interruptions, no filtering, paraphrasing to confirm. Empathetic listening goes further—eyes and ears—reading what's behind the words and "meeting the buyer in the conversation going on in their mind." That's as relevant in procurement-heavy Japan as it is in fast-moving US sales teams. Do now: Identify which level you default to under pressure—and train upward, not sideways. What does "ignoring the client" look like if you're still in the room? You can "ignore" a buyer while looking directly at them—by following your own thoughts instead of their words. This is common when the client says something that sparks urgency: "We're also talking to your competitor," "Budget is tight," "We need this by Q2." The moment you latch onto that, the rest of what they say fades into the mist because you're fixated on the counterpoint you must deliver. In enterprise sales, this is where deals quietly die: you respond to the wrong problem, at the wrong depth, to the wrong stakeholder. In Japan, where meaning can be indirect and consensus-based, this is riskier—what's not said can be the real message. In Australia, where communication is often more direct, you can still miss the nuance in tone—especially in remote calls where you're juggling slides, notes, and chat. Do now: When you feel triggered, pause and mentally label it: "That's my ego talking—back to the buyer." Why do salespeople "pretend" to listen—and how can you spot it? Pretend listening happens when your body language says "I'm with you" but your mind is already pitching, defending, or debating. You nod. You lean in. You look professional. But internally you're preparing the product dump, building the objection-handling case, or rehearsing the "killer story." It's the classic "lights are on, but you're not home" dynamic—common across industries like consulting, insurance, tech, and professional services. The modern version is worse: you're also glancing at CRM notes, Slack messages, or the next meeting timer. Buyers notice because your responses don't quite match what they said. You answer a question they didn't ask, or you jump too early. In negotiation-heavy environments (Japan, Germany, regulated sectors), this reads as disrespect. In faster markets (US startups), it reads as shallow. Do now: After the buyer speaks, summarise in one sentence before you respond with anything else. Is "selective listening" efficient—or does it sabotage sales outcomes? Selective listening is efficient for hearing buying signals, but it often sabotages effectiveness by skipping the context that makes the "yes" or "no" meaningful. Salespeople are trained to hunt for signals: interest, hesitation, resistance. But if you only listen for yes/no, you miss the conditions attached—like internal politics, compliance concerns...
    Show More Show Less
    12 mins
  • Our Solution Provision

    Our Solution Provision
    Feb 11 2026
    The Five-Phase Sales Solution Cadence: Facts, Benefits, Applications, Evidence, Trial Close When you've done proper discovery—asked loads of questions about where the buyer is now and where they want to be—you earn the right to propose a solution. But here's the kicker: sometimes the right move is to walk away. If you force a partial or wrong-fit solution, you might "grab the dough" short-term, but you'll torch trust and reputation—the two assets that don't come back easily. Below is a search-friendly, buyer-proof cadence you can run in any market—**Japan vs **United States, SME vs enterprise, B2B services vs SaaS—especially post-pandemic when procurement teams want clarity, proof, and outcomes, not fluffy feature parades. How do you know if your solution genuinely fits the buyer (and when should you walk away)? You know it fits when you can map your solution to their stated outcomes—and prove it—without twisting the facts. If the buyer needs an outcome you can't deliver, the ethical (and commercially smart) play is: "We can't help you with that." In 2024–2026, buyers are savvier and more risk-aware. They'll check reviews, ask peers, and sanity-test claims through AI search tools and internal stakeholder scrutiny. In high-trust cultures (including Japan) and high-compliance industries (finance, health, critical infrastructure), a wrong-fit sale becomes a reputational boomerang. The deal closes once; the story travels forever. Do now: Write a one-page "fit test": buyer outcomes → your capability → evidence. If any outcome can't be supported, qualify out fast. What does "facts" mean in a modern B2B sales conversation? Facts are the provable mechanics—features, specs, process steps, constraints—and the proof that they work. Facts aren't the goal; they're the credibility scaffolding. Salespeople often drown here: endless micro-detail, endless Q&A, endless spreadsheets. Yes, analytical buyers (engineering-led firms, CFO-led committees) will pull you into the weeds—but remember: they aren't buying the process. They're buying the outcome from the process. Bring facts that de-risk the decision: implementation timelines, security posture (SOC 2/ISO), uptime/SLA history, integration limits, and measurable performance benchmarks. Then move on before you get stuck. Do now: Prepare a "facts pack" with 5–7 proof points (not 57 features). Use it to earn trust, then pivot to outcomes. How do you turn features into benefits buyers will actually pay for? Benefits are the "so what"—the measurable results the buyer gets because the feature exists. If you can't link a feature to an outcome, it's just trivia. A weight, colour, dimension, workflow, dashboard, or AI model is not valuable by itself. It becomes valuable when it improves a KPI: reduced cycle time, fewer defects, higher conversion, lower churn, faster onboarding, better safety, tighter compliance. This is where classic sales thinking still holds up—think **SPIN Selling and the buyer's implied needs: pain, impact, and value. In a tight 2025 budget environment, "nice-to-have" benefits die quickly; "must-have" outcomes survive. Do now: For every top feature, write one sentence: "This enables ___, which improves ___ by ___ within ___ days." If you can't fill the blanks, drop the feature from your pitch. What is the "application of benefits" and how do you make it real inside their business? Application is where benefits turn into daily operational reality—what changes in workflow, decisions, and results.This is the "rubber meets the road" layer. Don't just say "we improve productivity." Show where it lands: which meetings get shorter, which approvals disappear, which roles stop firefighting, which customers get served faster, which errors are prevented, and what leaders see weekly on dashboards. Compare contexts: a startup may care about speed and cash runway; a multinational may care about governance, change management, and multi-region rollouts. A consumer business might chase conversion and NPS; a B2B industrial firm might chase downtime reduction and safety incidents. Do now: Build a simple "Before → After" map for their week: processes eliminated, expanded, improved—and who owns each change. What counts as credible evidence (and what "proof" actually convinces buyers)? Credible evidence is specific, comparable, and close to the buyer's reality—same industry, similar scale, similar constraints. "Trust me" is not evidence. Bring proof that survives scrutiny: reference customers, quantified case studies, independent reviews, pilot results, and implementation artefacts (plans, timelines, adoption metrics). The closer the comparison company is to the buyer, the more persuasive it becomes. This is also where storytelling matters: not hype—narrative. Who was involved? What went wrong? What changed? What were the numbers before and after? Analysts like **Gartner or **Forrester can help with ...
    Show More Show Less
    12 mins
  • The Sales Questioning Model

    The Sales Questioning Model
    Feb 3 2026
    Most sales meetings go sideways because the seller is winging it, not guiding the buyer through a clear decision journey. In a competitive market with limited buyer time, you need a questioning structure that gets to needs fast, keeps control of the conversation, and leads naturally to a purchase decision—without sounding scripted. Do you actually need a sales questioning model, or can you just "follow the conversation"? You need a questioning model because buyers will pull the conversation in random directions and you still need to reach a purchase outcome. A lot of salespeople have little structure because they're untrained, they're used to winging it, or they hate being "shackled" by a system and want to be a free bird in the meeting. The problem is: you don't have unlimited time, and competitors are offering similar solutions, so you must get to a clear understanding of needs quickly and match a solution precisely. A model gives you a logical cadence and a "track of your choosing" so you can steer back to what matters when the conversation wanders. Do now: Go into your next meeting with a written question flow, not just a list of topics. What are "As-Is" questions and why do they matter in discovery? As-Is questions establish the buyer's baseline—what they're doing now and how well it's working. You're mapping the current reality: what has the client been doing so far, what's working, what isn't working well enough, and what the situation inside the organisation looks like today. Sometimes buyers jump straight to where they want to be; that's fine, but you still need the "before" picture to measure the gap between current and desired states. Without the baseline, you can't diagnose properly, you can't quantify distance, and you're guessing at priorities. Do now: Ask three baseline questions before you pitch anything: current process, current result, current constraint. What are "Should Be" questions and how do you uncover real goals? Should Be questions reveal what outcomes the buyer is aiming for—strategic, financial, or operational. Clients have goals whether they publish them or keep them private, and you need to know them to judge whether you can help. These goals might be in an annual report, an internal plan, or just in the head of the decision-maker. Your job is to get them into the open so you can measure fit and value. This is also where you start building a clear "destination" so the buyer can see the difference between today and the target state. Do now: Ask: "What does success look like this quarter?" then "What metrics prove it?" What are implication questions, and why should you always include time? Implication questions create urgency by showing the downside of staying as-is—especially the cost of taking too long. The point is to plant doubt: can they hit the goal by themselves, fast enough, and cost-effectively enough? Time is the accelerator—because even if they could get there eventually, they usually don't have "100 years." Strong implication prompts include: "If things stay the way they are, will you still reach the target fast enough?" and "What happens if you don't meet the goal in the required timeframe?" You're not bullying them; you're helping them face the reality that no action has opportunity costs. Do now: Add one time-based implication question to every discovery call. What are "Change" questions and how do they uncover your real sales opportunity? Change questions ask the key truth: if they know where they are and where they need to be, why aren't they there already? This is where your value often appears, because their answer exposes capability gaps, speed gaps, political roadblocks, or resource limits—exactly the reasons they may need you. The companion implication here is serious: if they can't make the necessary changes, will it damage the business? Markets don't wait around, and delaying change isn't neutral—it has a price. Your role is to surface that cost clearly, then position your solution as the fastest, safest path to progress. Do now: Ask: "What's stopped you fixing this until now?" and then "What will it cost to delay another 90 days?" Payout questions identify what's personally at stake for the buyer if the project succeeds—or fails. The company expects outcomes, and the buyer is under pressure to deliver results. When you know what the buyer personally gains (reputation, promotion, risk reduction, credibility), you can frame your solution around what matters to them, not just the organisation. There's also an implication question here, but it requires diplomacy: "In the worst-case scenario, what would be the personal impact for you if this can't be fixed fast enough?" Done well, it makes you an ally in their success—not another vendor chasing a contract. Do now: Ask one personal-stakes question on every deal where multiple vendors ...
    Show More Show Less
    13 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.