b2b-questioning

B2B Questioning Skill for Enterprise Software

This skill codifies the questioning discipline that wins enterprise software deals, designs implementable solutions, and retains accounts. It is built for Sales Account Executives, Pre-Sales / Solution Consultants, and Customer Success Managers working on Oracle, SAP, NetSuite, MS Dynamics, Salesforce, Workday, Infor, Odoo, and comparable platforms, with a primary lens on Thailand and APAC enterprise buyers.

Questioning is the highest-leverage advisory skill in enterprise software. The product is invisible until configured, the buying committee is large and heterogeneous, and the value is realized over years — all three conditions make the quality of questions the direct driver of win rate, implementation margin, and net revenue retention. This skill should be used whenever the user is preparing for, executing, or reviewing a customer conversation at any stage of the deal or account lifecycle.

How to use this skill

When this skill triggers, follow this workflow:

Step 1 — Clarify the engagement context. Before producing any question set, confirm these five inputs with the user. If any are missing, ask for them:

• Role: AE (sales), SC (pre-sales / solution consultant), or CSM (customer success).
• Stage: prospecting, discovery, qualification, solution design, demo/proof, RFP, negotiation, close/handoff, onboarding, adoption, QBR, renewal, expansion, or escalation.
• Persona: the specific stakeholder(s) who will be in the room — Economic Buyer (usually CFO/CEO), Technical Buyer (CIO/IT Director), User Buyer (Finance Director, Ops Head, HR Director), or Champion.
• Business process or solution area: Record-to-Report, Procure-to-Pay, Order-to-Cash, Hire-to-Retire, Plan-to-Produce, Treasury, Compliance, Analytics, or cross-functional.
• Cultural context: Thai (default for this user), regional APAC, Western, or mixed. This determines register and indirection.

Step 2 — Select the primary framework. Use the framework-selection guide below. Usually SPIN is the core discovery spine, with MEDDPICC as private qualification, Sandler Pain Funnel for depth probing, Challenger for one provocative reframe, and JTBD or Design Thinking laddering for solution workshops. For the full framework detail, read references/frameworks.md.

Step 3 — Draft the question set. Produce between eight and twenty questions tailored to the inputs. Every question must carry the ten mandatory elements (see references/mandatory-elements.md). Sequence the questions in a funnel: broad to narrow, past to present to future, Situation to Problem to Implication to Need-Payoff.

Step 4 — Tag each question. For every question produced, tag it with framework origin (SPIN-Situation, SPIN-Problem, SPIN-Implication, SPIN-Need-Payoff, MEDDPICC-[letter], Sandler-layer-[N], Challenger, Socratic, 5-Whys, JTBD, Design-Thinking-HMW, or Design-Thinking-ladder), target persona, and purpose.

Step 5 — Add Thai-register softening (if applicable). For any question that would feel direct or confronting in Thai business culture, provide a softened phrasing. For the hardest questions, recommend whether they are better asked in the room or in private follow-up. Read references/thai-context.md for the four dimensions: kreng jai (reluctance to impose), face (นับหน้าถือตา), hierarchy (ผู้ใหญ่-ผู้น้อย), and bunkhun (relationship debt).

Step 6 — Produce the meeting plan. Wrap the question set in a meeting plan that includes: the opening move, the sequencing logic, the three-second silence reminders, the probing follow-ups, a MEDDPICC-refresh template for post-meeting use, and a risk-surface question the user should ask even if it feels uncomfortable.

Framework selection guide

Choose frameworks based on the stage and the goal:

• Prospecting / first meeting: one SPIN-Situation opener, one Challenger question grounded in public research, one Champion-surfacing question.
• Discovery (primary spine): SPIN funnel — Situation → Problem → Implication → Need-Payoff — traversed once per business process. Use Sandler Pain Funnel layers 1–6 on the highest-priority pain. Use Five Whys when a problem statement is vague and root cause is unclear.
• Qualification (private scorecard after the meeting): MEDDPICC. Every letter below confidence 5/10 becomes the agenda for the next conversation.
• Solution design workshop: JTBD interview opener ("walk me through the last time you hired a system to do this job"), Design Thinking How Might We reframes, why/what/how laddering, Strategic Selling stakeholder map.
• Demo / Proof: discovery-driven scene scripting, open with context-question + close with Need-Payoff.
• Negotiation: open questions + disciplined silence after price.
• QBR / Renewal: accountability against committed success metrics, Socratic forward-looking questions, Champion health check.
• Escalation / Churn risk: direct truth-seeking questions, skeptic-surfacing.

See references/frameworks.md for the full treatment of each framework with enterprise software examples.

Question taxonomy (twelve types)

Every question produced should be one of these types and the type should be named in the tag:

Open (what, how, why, tell me about) — generates information and surfaces vocabulary. Closed (is/are/do/did/can/will) — confirms and narrows. Probing — goes one level deeper into a prior answer. Clarifying — resolves ambiguity. Reflective — paraphrases the answer back. Hypothetical — explores scenarios. Implication — extends consequences of a stated problem. Leading — contains its own answer (avoid in discovery; acceptable only for trial close). Funnel — broad to narrow sequencing. Confirmatory — seals agreement. Provocative — challenges current thinking (Challenger move). Silence — three-second pause after an answer (not a question, but functions as one).

A fluent thirty-minute discovery uses all twelve.

The ten mandatory elements of a great question

Every produced question must carry these elements. When reviewing a user's draft questions, score against this list:

1. Purpose — one-sentence statement of what this question is designed to produce.
2. Tense — deliberate location in past, present, or future.
3. Scope — calibrated altitude (not too broad, not too narrow).
4. Specificity — specific enough that only this customer can answer, not generic enough to apply anywhere.
5. Neutrality — no leading phrasing embedded.
6. Cognitive load — answerable in sixty seconds or less without forcing public long-form thought.
7. Sequencing — fits the funnel logic of the conversation.
8. Follow-up — at least one probing question drafted for the expected answer.
9. Silence — explicit reminder to hold three seconds after asking.
10. Documentation — plan to capture the answer in CRM, workshop minutes, or account notes.

Read references/mandatory-elements.md for the deep treatment with diagnostic tests.

The twelve character traits of a master questioner

When the user asks about skill development, coaching, or self-assessment, reference these twelve traits: curiosity, patience-with-silence, empathy, business acumen, domain knowledge, emotional intelligence, humility, discipline and preparation, active listening, cultural sensitivity, courage, objectivity. Full descriptions and the self-assessment rubric are in references/anti-patterns-rubric.md.

Thai cultural calibration

When the cultural context is Thai (the default for this user), every question must be calibrated against four dimensions: kreng jai (reluctance to impose/embarrass), face (saving face, นับหน้าถือตา), hierarchy (seniority register), and bunkhun (relationship-debt earned over years). The calibration softens delivery without losing rigor — same content, different form. Hard questions are often reserved for private one-on-one follow-up rather than the formal meeting. Read references/thai-context.md for detailed examples and softened phrasings of the hardest questions in the bank.

Role-specific playbooks

The three role playbooks map the right questions to the right stage of the work:

• Account Executive: prospecting → discovery → qualification → demo → negotiation → close/handoff.
• Pre-Sales / Solution Consultant: solution discovery workshop → fit-gap → RFP response → demo scripting → design validation.
• Customer Success Manager: onboarding → adoption reviews → QBR → renewal → expansion → escalation.

Read references/role-playbooks.md for the full stage-by-stage questioning agendas.

Question bank

When the user asks for sample questions, a discovery list, a QBR agenda, MEDDPICC probes, or any canned question set, pull from references/question-bank.md (125 curated questions indexed by phase, persona, framework, and purpose). Do not just dump the bank; select 8–20 questions that fit the user's specific inputs, tag each one, and add the Thai softening where relevant.

Anti-patterns to avoid

Fifteen named anti-patterns account for most questioning failures. When reviewing a user's draft or a call transcript, check against this list: interrogation, brochure dump, leading loop, assumption shortcut, feature-probe, orphaned question, seniority mismatch, premature close, confirmation-bias collection, silence-breaker, assumption-laden phrasing, one-sided discovery, Thai-register miscalibration, unprepared Challenger, undocumented conversation. Full corrective discipline for each is in references/anti-patterns-rubric.md.

Output format

When producing a question set, structure the output as follows:

# Question Set: [Stage] — [Persona] — [Process]

## Context summary
[1–2 sentence restatement of the five inputs gathered in Step 1.]

## Opening move
[The first question and why it opens this way.]

## Question sequence
1. [Question] — *[Framework tag / Persona / Purpose]*
   - Follow-up probe: [one probing question]
   - Thai softening (if applicable): [softened phrasing]
2. ...

## The hard question
[One question the user should ask even if uncomfortable, with reasoning.]

## Post-meeting capture template
- MEDDPICC refresh: [fields to update]
- Next-meeting agenda: [what to ask next]
- Risk/flag to escalate: [if any]

When reviewing a user's existing questions or a call transcript, structure the output as a rubric score against the ten mandatory elements with specific rewrite suggestions for any question scoring below four on any element.

Reference files

• references/frameworks.md — SPIN, MEDDPICC, Sandler Pain Funnel, Challenger, Five Whys, Socratic, Strategic Selling, JTBD, Design Thinking laddering. Read whenever a framework selection decision is needed or the user asks about any specific framework.
• references/mandatory-elements.md — the ten mandatory elements with diagnostic tests and funnel-sequencing discipline. Read when producing or scoring questions.
• references/role-playbooks.md — stage-by-stage agendas for AE, SC, CSM. Read when the user's role and stage are identified.
• references/question-bank.md — 125 tagged sample questions. Read when the user asks for examples, a starter set, or inspiration.
• references/thai-context.md — kreng jai, face, hierarchy, bunkhun calibration. Read whenever the cultural context is Thai or APAC.
• references/anti-patterns-rubric.md — 15 anti-patterns and the self-assessment rubric. Read when reviewing user drafts or transcripts.
• references/design-thinking-complement.md — empathy mapping, POV statements, stakeholder personas (from the companion Design Thinking research). Read during solution design workshops and co-creation sessions.
• assets/playbook-full.md — the complete source playbook as a single document, for deep reading when the user wants the full research.

Invocation tips

• When the user's request is multi-stage (e.g., "prep me for a full discovery and negotiation cycle"), produce stage-sequenced outputs in one response, each with its own question set, rather than asking which stage to start with.
• When in doubt about whether Thai softening is needed, apply it — erring toward softened delivery rarely costs anything and often earns trust.
• When the user pastes a call transcript or rough notes, score the questions already asked against the ten mandatory elements, then propose the next three questions that the user should ask in the next conversation.
• When the user's context is government, e-bidding, or Thai public sector, cross-reference the advisor-govt-gfmis and govt-egp-gfmis skills if installed — questioning in regulated procurement has additional legal and process constraints.
• When the technology in scope is Oracle, SAP, NetSuite, or Salesforce, domain knowledge matters — depth of the question correlates directly with the user's technical fluency, so recommend pre-meeting homework if the user seems unsure of the technical baseline.