Sales Communication Instructions

Tactical communication rules for Naologic sales. Use when writing emails, preparing calls, running discovery, or evaluating buyer resistance. Resistance signals missing safety, clarity, control, or trust—not a reason to apply pressure.

---

1. Message Framework

Structure every outbound message in this order:

1. Reality — buyer's narrative + observable artifact + seller's model → buyer confirms
2. Problem Hypothesis — operational mismatch + evidence requirement + confirmation question + status (inferred | call_confirmed | artifact_verified)
3. Impact Hypothesis — quantified loss, risk, constraint, or labeled hypothesis
4. Mechanism — native capability, builder adaptation, or Logic Pilot action
5. Proof — customer data demo, live build, benchmark, or reference
6. Choice — explicit, low-pressure next step

Prohibited in any message

• Unsupported superlatives
• Presenting a hypothesis as a customer fact
• Generic feature dumps
• Manufactured urgency
• Hidden tradeoffs
• Predetermined conclusions

Capability Classification

Every capability claim must be labeled:

Type	Definition
Native	Available without customer-specific build
Configured	Produced with the builder
Integrated	Dependent on an external system
Roadmap	Unavailable now; must be explicitly labeled as such

Critical gap rule: If a capability required for purchase is not native, disclose it before making any recommendation, classify it, explain the interim state, and define the delivery dependency.

---

2. Product Narrative

Position Naologic as three layers:

• Industry Core — models known manufacturing physics
• Builder — captures tacit knowledge, expresses it as editable rules, deploys as working software, evolves without reimplementation
• Logic Pilot — explains and acts on live operational state

Positioning formula:

• Fit without rigidity
• Adaptation without consultant dependency
• AI without surrendering control

Builder is proof that customer uniqueness is modelable—not an objection to implementation.

---

3. Bias-Aware Design

Biases are human responses to uncertainty, complexity, and perceived threat. Do not manipulate them. Reduce the trigger through product and process, then provide inspectable evidence.

Customer confidence = clarity + control + continuity + evidence + reversibility

Never: shame the response, manipulate the trigger, conceal uncertainty, or pressure the decision.

Active Bias Rankings (ERP Replacement Context)

Rank	Bias	Trigger	Required Response
1	Status quo bias	Change threatens continuity	Quantify inaction; stage migration; define rollback and acceptance tests
2	Loss aversion	Operations, data, or career value may be lost	Protect critical workflows; prove continuity before cutover
3	Ambiguity aversion	Scope, outcome, or ownership is unknown	Make scope, timeline, controls, and owners inspectable
4	Confirmation bias	Prior ERP experience defines expectation	Invite disconfirmation; test claims live; expose limitations
5	Sunk-cost effect	Existing investment feels wasted	Preserve reusable data, knowledge, integrations, and processes
6	Anchoring	Buyer needs an initial reference point	Establish the customer baseline before price or ROI
7	Availability heuristic	Memorable failure dominates judgment	Explain its cause; show the specific control for that cause
8	Social proof	Buyer seeks evidence that peers are safe	Use comparable customers and disclose comparability
9	Authority bias	Expertise substitutes for verification	Pair expert claims with inspectable product evidence
10	Reactance	Pressure threatens autonomy	Preserve choice, approvals, configuration control, and the right to say no

Principle: Bias reveals a need for more safety, clarity, evidence, or control.

Buyer Response Playbook

Buyer Response	Likely Trigger	Bias-Aware Response
Defensiveness	Expects pitch, judgment, or hidden downside	Name the likely concern before presenting; invite correction
Reactance	Question appears designed to force agreement	Make refusal safe; treat "no" as information, not rejection
Easy agreement	Wants relief, escape, or social compliance	Distinguish acknowledgment from commitment; verify through specifics
Fairness claim	"Fair" used as emotional frame without criteria	Ask what standard, comparison, or process defines fairness
Deadline pressure	Date creates urgency before consequences known	Verify who owns the date, why it exists, and what happens after it
Anchoring	First number or scope dominates discussion	Return to customer's baseline, assumptions, mechanism, and evidence
Loss aversion	Change endangers continuity or sunk value	Show how value is preserved; make cost of inaction inspectable
Premature compromise	Midpoint feels safer than solving real constraint	Do not split the difference by reflex; find the need each term protects
Withheld information	Buyer does not yet feel safe disclosing	Slow down, listen for inconsistencies, explore without accusation

Tactical Empathy Rules

• Tactical empathy = observe, label as hypothesis, pause, invite correction
• Empathy ≠ agreement
• Recognition ≠ endorsement
• Influence ≠ coercion

Emotional safety protocol:

1. Name the concern
2. Demonstrate understanding
3. Confirm or correct
4. Then explore solution

Hidden constraints: unspoken facts, private stakes, informal influence, fear. If behavior seems irrational, search for a hidden constraint. Never label the person irrational.

---

4. Conversation Architecture

Objective: Accurate understanding before influence. Slow the interaction down, lower threat, and make it easy for the buyer to correct the seller.

Pre-call preparation

• Desired outcome
• Buyer-view hypotheses
• Likely negative perceptions
• Labels to deploy
• Calibrated questions
• Known constraints
• Walk-away conditions

In-call delivery

• Calm tone
• Deliberate pace
• Concise language
• Unhurried silence

Listening protocol

• Attend to words, tone, omissions, contradictions
• Do not rehearse rebuttal
• Follow new information

---

5. Tactical-Empathy Tools

Label

Neutral observation of perspective, emotion, or constraint; expressed as a tentative hypothesis; followed by silence.

Mirror

Repeat 1–3 critical words in a curious tone, then pause for elaboration.

Accusation Audit

Identify likely negative judgments, state them without defensiveness, invite correction.

Summary

Facts + perspective + emotion + constraints.

Understanding confirmed only when buyer says "that's right" or corrects the summary.

Caution: If buyer says "you're right," do not assume alignment. Ask for correction or missing detail.

Rule: Labels and mirrors are listening tools, not scripts to stack mechanically. Use one, remain silent, follow the buyer's response. A wrong label is useful when tentative—the correction reveals better information.

---

6. Questions and Control

No-oriented questions

Questions that make refusal safe. Example: "Would it be a bad idea to examine where the current system stops matching the work?"

Cold call access protocol:

1. Transparent identity
2. No-oriented time question: "Is now a bad time to talk?"
3. Stop and listen

• If buyer says no (it's not a bad time) → continue with relevance
• If buyer says yes (it is a bad time) → stop pitch, accept buyer-proposed callback or end call

Calibrated questions

Prefer what and how questions that give the buyer control and require explanatory answers.

Use why only when non-accusatory and necessary.

Prohibited question types:

• Forced yes
• Disguised pitch
• Answer embedded in question
• Rapid-fire interrogation
• Unexplained why

Question sequence: calibrated question → listen → label or mirror → pause

Question Bank

Purpose	Example
Open safely	"Would it be a bad idea to examine where the current system stops matching the work?"
Define objective	"What are we trying to accomplish operationally?"
Find main constraint	"What is the biggest challenge with changing this process?"
Reveal impact	"How does this affect production, cash, quality, or the rest of the team?"
Test inaction	"What happens if nothing changes?"
Surface stakeholders	"How do the people not in this meeting see the change?"
Reject infeasible demand	"How could we meet that requirement with the time and evidence currently available?"
Plan for failure	"If this breaks during implementation, what should happen next?"
Define proof	"What would you need to see to trust the result?"

Refusal protocol: The seller may refuse a term without rejecting the person. First recognize the buyer's need, then use a calm calibrated question to expose the constraint. Never use a calibrated question sarcastically or before demonstrating understanding.

---

7. Agreement and Commitment

A verbal "yes" is not proof of adoption.

Real agreement requires

• Shared summary
• Explicit terms
• Implementation path
• Affected stakeholders
• Named owner
• Date
• Failure response

Verify commitment by

• Confirming in multiple ways without pressure
• Asking how it will be done
• Resolving conflicting signals

Black Swan Search

• Notice unexpected detail
• Test assumption
• Identify hidden constraint or leverage
• Update recommendation

Rule: If new information changes fit, revise scope, change terms, or disqualify.

---

8. Selling with Love

Formula: love of impact + love of client + love of product + love of process + love of self

Dimension	Action
Love impact	Define measurable better state
Love client	Understand reality; recommend only if fit
Love product	Know mechanism; prove honestly; expose limits
Love process	Make each interaction useful; preserve choice
Love self	Prepare deeply; act without desperation

Productive energy = curiosity + competence + client problem
Hype = enthusiasm - evidence

---

9. Sales Methods

Discovery

Primary question: "Where does the current system stop matching physical reality?"

Process: listen → ask → observe artifact → model operational logic → confirm understanding

Discovery output:

• Physics — rules the software must respect
• Friction — spreadsheet, reentry, workaround, manual decision
• Leakage — material, time, capacity, quality, cash, risk
• Desired state — measurable operational change
• Required proof — evidence the buyer defines as sufficient
• Change context — incumbent, implementation stage, committed cost, exit cost, downtime tolerance, data constraints, economic buyer, risk owner, decision process

Artifacts to request: current screen, spreadsheet, quote, schedule, production order, report, source document. Do not rely on description when the buyer can safely show the work.

Demonstration

Structure: model → modify → decide → execute

• Model — reproduce customer workflow with native core
• Modify — implement one customer-specific requirement with builder
• Decide — answer one live operational question with Logic Pilot
• Execute — draft or run one approved action with auditability

Proof ladder:

1. Observe customer artifact
2. Reproduce data model
3. Build customer-specific prototype
4. Test acceptance criteria
5. Validate reference
6. Present transition plan

Use the customer's workflow, language, constraints, and success criteria. A generic tour is not proof.

Qualification

A deal is qualified only when all are true:

• Fit
• Material impact
• Sponsor
• Proof possible
• Decision process known
• Transition risk understood

If not qualified: clarify gap → reduce scope → recommend alternative → disqualify

Scope strategy:

• Primary wedge — highest impact + shortest proof + lowest transition risk
• Adjacent use case — capture, acknowledge, defer
• Entry scope options — full platform | high-value wedge | technical proof only

Value

Annual value =

• material savings
• throughput contribution
• labor reclaimed
• quality and expedite avoidance
• technology and consulting avoided
• minus transition cost

Rules:

• Published benchmarks are discovery input, not customer promises
• Price range requires: known scope, assumptions, exclusions, confidence level, validation step

Next Step

Valid next step contains: artifact, buyer owner, Naologic owner, due date, meeting date, acceptance criterion.

Invalid: vague follow-up, missing owner, missing date.

---

10. Prohibited Tactics

• Manufacture fear
• Weaponize loss aversion
• Use false deadlines
• Use extreme anchors without basis
• Frame compliance as fairness
• Seek counterfeit agreement
• Shame buyer responses
• Conceal uncertainty
• Pressure decisions
• Apply pressure when encountering resistance