Document Type: Framework
Status: Structural
Version: v1.0
Authority: HeadOffice
Applies To: AIBS Brain, Ecommerce Brain, HeadOffice, future MWMS service offers
Parent: HeadOffice
Last Reviewed: 2026-04-12

Purpose

This framework defines how MWMS structures sales conversations so that calls diagnose real business problems before proposing solutions.

It exists to prevent:

• premature pitching
• generic sales conversations
• weak problem understanding
• poor client qualification decisions
• misaligned expectations
• low close rates
• weak proposal relevance

The diagnostic approach ensures that service offers are based on real business needs rather than assumptions.

Diagnosis-first selling improves:

client trust
solution relevance
pricing confidence
commercial alignment
close probability

Sales conversations become structured discovery processes rather than persuasion attempts.

Scope

This framework applies to:

• consulting sales calls
• optimization service discovery calls
• AI implementation opportunity calls
• ecommerce growth consultation calls
• diagnostic consultations
• high-value advisory conversations

This framework governs:

conversation structure
information gathering logic
problem clarity development
opportunity identification
next-step definition

It does not govern:

pricing logic
proposal structure formatting
contract structure
client onboarding processes

Those are governed by:

MWMS Value Based Pricing Framework
MWMS Proposal Structure Framework
MWMS Client Expectation Setting Protocol

Definition or Rules

Core Principle

Sell the diagnosis, not the pitch.

Clients trust providers who demonstrate understanding of the problem.

A structured diagnostic conversation:

clarifies business constraints
uncovers opportunity size
identifies performance gaps
reveals decision drivers
identifies urgency level

The course material emphasizes that strong sales conversations focus on diagnosing underlying performance issues before presenting solutions.

Diagnostic Sales Call Structure

A diagnostic sales call progresses through five phases:

Context
Problem
Impact
Constraints
Next Step

Each phase improves clarity.

Clarity improves commercial alignment.

Phase 1 — Context Discovery

Understand the business environment.

Typical context questions:

business model
revenue model
traffic sources
customer acquisition channels
product structure
current priorities
growth stage
internal team structure

Goal:

understand operating environment.

Context shapes solution relevance.

The source material stresses understanding the client’s environment before recommending specific services.

Phase 2 — Problem Discovery

Identify the primary challenge the client wants to solve.

Examples:

conversion rate stagnation
poor lead quality
low repeat purchase rate
weak landing page performance
inefficient acquisition costs
unclear funnel drop-offs

Problem clarity improves relevance of solution design.

Clients often initially describe symptoms rather than root causes.

Diagnostic conversation must clarify the underlying constraint.

The course emphasizes clarifying real performance bottlenecks before suggesting improvements.

Phase 3 — Impact Clarification

Understand why the problem matters.

Examples:

lost revenue potential
inefficient marketing spend
low lifetime value
weak growth trajectory
operational inefficiency
stakeholder pressure

Impact clarifies urgency.

High impact problems justify higher pricing and faster decisions.

Understanding impact allows prioritization of opportunities.

The source material emphasizes identifying economic consequences of the problem.

Phase 4 — Constraint Identification

Identify limitations that affect solution design.

Examples:

data limitations
implementation capacity
internal resources
stakeholder alignment
technical constraints
timeline constraints
budget constraints

Constraints shape feasible solution structure.

Ignoring constraints leads to unrealistic proposals.

The course highlights importance of understanding organizational readiness and operational limitations.

Phase 5 — Next Step Definition

Define appropriate next step.

Possible next steps:

diagnostic audit
research engagement
structured roadmap
pilot engagement
full retainer
internal discussion
follow-up clarification session

Next step should feel logical given conversation insights.

Avoid forcing premature commitment.

The course material suggests that clarity-driven next steps improve trust and close probability.

Active Listening Requirement

The diagnostic call prioritizes listening over speaking.

Indicators of effective listening:

clarifying questions
paraphrasing client statements
confirming understanding
exploring underlying assumptions
identifying unstated concerns

Clients value feeling understood.

Trust improves when the client feels accurately interpreted.

The source material highlights paraphrasing client problems to demonstrate understanding.

Avoid Premature Pitching

Premature pitching signals lack of understanding.

Avoid:

presenting predefined solution immediately
describing services before problem clarity
pushing specific package before qualification
assuming problem without validation

Solutions should emerge from diagnosis.

The course strongly discourages jumping directly into pitching services before problem clarity exists.

Problem Ownership Alignment

Client must acknowledge the problem.

If the client does not recognize the problem:

urgency is low
commitment is weak
implementation likelihood is reduced

Strong alignment occurs when:

client describes problem clearly
client recognizes business impact
client expresses motivation to solve problem

Problem ownership increases close probability.

The course material emphasizes shared understanding of the problem as a prerequisite for engagement.

Diagnostic Signals of Strong Opportunity

Strong signals include:

clear business problem
measurable impact
internal motivation to improve
operational readiness
budget alignment
collaborative attitude

Weak signals include:

vague goals
exploratory curiosity only
unclear responsibility ownership
unclear urgency
unrealistic expectations

Diagnostic signals inform qualification decision.

Governance Role

This framework ensures:

sales conversations remain structured
proposals remain relevant
qualification decisions remain informed
pricing decisions remain justified
client expectations remain aligned

HeadOffice maintains authority over sales logic structure.

AIBS Brain applies framework during consulting opportunity evaluation.

Relationship to Other MWMS Standards

This framework interacts with:

MWMS Service Offer Qualification Framework
MWMS Productized Service Design Framework
MWMS Value Based Pricing Framework
MWMS Proposal Structure Framework
MWMS Client Expectation Setting Protocol

Diagnostic clarity informs qualification strength.

Qualification strength informs pricing confidence.

Pricing confidence informs proposal strength.

Together these frameworks form the MWMS service commercialization layer.

Drift Protection

The system must prevent:

pitch-first selling
generic discovery calls
offering solutions before understanding problem
assuming client needs
forcing standardized packages prematurely
skipping qualification logic
weak problem articulation
shallow conversations

Weak diagnosis produces weak engagements.

Architectural Intent

MWMS Diagnostic Sales Call Framework ensures that service engagements begin with clarity.

Diagnosis-first sales logic:

improves client trust
improves solution relevance
improves pricing alignment
improves close probability
reduces expectation misalignment

Clarity improves execution quality.

Structured diagnosis improves long-term client outcomes.

Change Log

Version: v1.0
Date: 2026-04-12
Author: HeadOffice
Change: Initial creation.

Change Impact Declaration

Pages Created:

MWMS Diagnostic Sales Call Framework

Pages Updated:

none

Pages Deprecated:

none

Registries Requiring Update:

MWMS Architecture Registry
MWMS Document Registry

Canon Version Update Required:

Change Log Entry Required: