Doctrine · internal only
Source methods train the work; they are not the pitch. The buyer is the protagonist. Tactical empathy exists to understand, label, and lower threat — never to manipulate.
Storyworthy
One five-second moment. Dinner test. But/therefore, not and-then.
Tactical empathy
Labels, mirrors, summaries, no-oriented safety, and calibrated questions.
People do not change because they were argued into a conclusion. They change when they recognize a moment as their own.
01 · Message framework
The six steps are the order. The craft is whether it is a story.
Structure every outbound message in this order. A correctly ordered message that reads like a brochure has still failed.
01
Reality
Buyer's narrative + observable artifact + seller's model → buyer confirms.
Open on the scene of the current opposite. Location + artifact. Invite “that's right.”
02
Problem hypothesis
Operational mismatch + evidence requirement + confirmation question + status.
Name the elephant as a tentative hypothesis. Never as a customer fact.
03
Impact hypothesis
Quantified loss, risk, constraint, or clearly labeled hypothesis.
Stakes as a scene of consequence, not a slogan. Label confidence.
04
Mechanism
Native capability, Builder adaptation, integration, or Logic Pilot action.
Therefore, not and-then. Use one capability that makes the moment possible. Classify it.
05
Proof
Customer-data demo, live build, benchmark, or comparable reference.
One comparable person's five-second moment. The buyer remains the protagonist.
06
Choice
Explicit, low-pressure next step.
Make refusal safe. The story does not close itself.
Narrative craft
A story of change in the buyer's life — not a chronicle of the product.
Five-second moment
Every message is about one moment of change: the work starts matching the system, or the buyer sees precisely that it does not. Everything else exists to bring that moment into focus.
Protagonist rule
The buyer — or a named operator like them — is the protagonist. Naologic is the setting or instrument. A story that makes the seller look brilliant has failed.
Dinner test
If you would not say it that way to a peer at dinner — if it sounds like a brochure, keynote, thesis, or victory lap — rewrite it. Heart is required. Performance is not.
But / therefore
Connect with consequence, not sequence. Feature lists are and-then chronicles. A story moves because something did not match, therefore a decision became necessary.
Start at the mismatch
Once the five-second moment is clear, start at its opposite and as close to the change as possible. Do not recap company history or capabilities first.
Scene, not thesis
“Inefficient processes” is a thesis. “The planner re-enters the same order on three screens” is a scene. Attach claims to a screen, cell, floor, order, or meeting.
Prohibited in any message
- Unsupported superlatives
- Presenting a hypothesis as a customer fact
- Generic feature dumps and and-then chronicles
- Internal verification language or tool names in buyer-facing copy
- Manufactured urgency or false predictions dressed as stakes
- Hidden tradeoffs or predetermined conclusions
- Seller-as-hero stories, victory laps, or thesis-statement morals
- “I understand” or “I’m hearing that…” as a substitute for listening
Capability classification
If a capability required for purchase is not native, disclose it before recommending, classify it, explain the interim state, and define the delivery dependency.
- Native
- Available without a customer-specific build.
- Configured
- Produced with Builder for this customer.
- Integrated
- Dependent on an external system.
- Roadmap
- Unavailable now and explicitly labeled as such.
02 · Product narrative
Naologic is the setting. The buyer is the hero.
Use only the layer that makes this buyer's five-second moment possible. Do not narrate the platform as an and-then tour.
Industry Core
Models known manufacturing physics.
Builder
Captures tacit knowledge as editable rules and working software.
Logic Pilot
Explains and acts on live operational state.
- Fit without rigidity
- Adaptation without consultant dependency
- AI without surrendering control
Builder is proof that customer uniqueness is modelable — not an objection to implementation.
03 · Buyer safety
Bias reveals a need for more safety, clarity, evidence, or control.
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
- 01
Status quo bias
Trigger — Change threatens continuity
Quantify inaction; stage migration; define rollback and acceptance tests.
- 02
Loss aversion
Trigger — Operations, data, or career value may be lost
Protect critical workflows; prove continuity before cutover.
- 03
Ambiguity aversion
Trigger — Scope, outcome, or ownership is unknown
Make scope, timeline, controls, and owners inspectable.
- 04
Confirmation bias
Trigger — Prior ERP experience defines expectation
Invite disconfirmation; test claims live; expose limitations.
- 05
Sunk-cost effect
Trigger — Existing investment feels wasted
Preserve reusable data, knowledge, integrations, and processes.
- 06
Anchoring
Trigger — The buyer needs an initial reference point
Establish the customer baseline before price or ROI.
- 07
Availability heuristic
Trigger — A memorable failure dominates judgment
Explain its cause; show the specific control for that cause.
- 08
Social proof
Trigger — The buyer seeks evidence that peers are safe
Use comparable customers and disclose comparability.
- 09
Authority bias
Trigger — Expertise substitutes for verification
Pair expert claims with inspectable product evidence.
- 10
Reactance
Trigger — Pressure threatens autonomy
Preserve choice, approvals, control, and the right to say no.
Buyer response playbook
Defensiveness
Expects pitch, judgment, or hidden downside
Name the likely concern before presenting; invite correction.Reactance
A question appears designed to force agreement
Make refusal safe; treat “no” as information, not rejection.Easy agreement
Wants relief, escape, or social compliance
Treat it as a counterfeit yes until specifics and implementation prove commitment.Deadline pressure
A date creates urgency before consequences are known
Verify who owns the date, why it exists, and what happens after it.Anchoring
The first number or scope dominates discussion
Return to the customer's baseline, assumptions, mechanism, and evidence.Withheld information
The buyer does not yet feel safe disclosing
Slow down, listen for inconsistencies, and explore without accusation.Tactical empathy
Understand the feelings and mindset of another in the moment — and what sits behind them — then vocalize that recognition. Empathy is not agreement. Recognition is not endorsement. Influence is not coercion.
- Name the concern with a tentative label.
- Summarize facts, perspective, emotion, and constraints.
- Confirm or correct — wait for “that’s right” or a correction.
- Only then explore a solution.
04 · Conversation architecture
Accurate understanding before influence.
Slow the interaction down, lower threat, and make it easy for the buyer to correct the seller. Treat assumptions as hypotheses to be tested.
Prepare
- Desired outcome and buyer-view hypotheses
- Likely negative perceptions — the accusation-audit list
- Labels and calibrated questions to deploy
- Known constraints and walk-away conditions
- The one five-second moment this conversation is for
- What changes if new information changes fit
Deliver
- Deep, soft, slow delivery with downward inflection
- Positive or playful only when the room can bear it
- Direct or assertive sparingly, never to punish
- Concise language and unhurried silence
Listen
- Attend to words, tone, omissions, and contradictions
- When tone or body does not match words, label the incongruence
- Do not rehearse rebuttal; follow new information
- Summarize until they say “that’s right” or correct you
05 · Tactical-empathy tools
Use one. Remain silent. Follow the response.
Label
Offer a neutral, tentative observation of perspective, emotion, or constraint — “It seems like…”, “It sounds like…”, “It looks like…” — then remain silent.
Mirror
Repeat one to three critical words in a curious tone, then pause for elaboration. The intention is help me understand, not clever echo.
Accusation audit
Name the worst credible perceptions before the buyer does, without defensiveness, and invite correction. Then be quiet.
Summary
Bring together facts, perspective, emotion, and constraints. Understanding is confirmed by “that’s right” or a correction — never by your own confidence.
“That’s right” means they feel understood. It is better than “yes.”
Counterfeit yes
Said to end the conversation or escape social pressure.
Confirmation yes
Reflexive agreement with a statement; no commitment.
Commitment yes
Agreement plus a credible implementation path.
06 · Questions and control
Make refusal safe. Yes is nothing without how.
Prefer what and how. Use why only when it cannot sound accusatory. Sequence one calibrated question → listen → label or mirror → pause.
Cold call access
- Use a transparent identity.
- Ask, “Is now a bad time to talk?”
- Stop and listen. If it is a bad time, accept their callback or end the call.
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 the 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?”
Plan for failure
“If this breaks during implementation, what should happen next?”
Define proof
“What would you need to see to trust the result?”
Implementation
“How will we know we’re on track, and what happens if we are not?”
Restore control
“How would you like me to proceed?”
Refusal protocol
Recognize the buyer's need, then stop at the first line that holds.
- “How am I supposed to do that?”
- “That’s generous — I’m sorry, that doesn’t work for me.”
- “I’m afraid I can’t do that.”
- A clear, calm no.
07 · Agreement
A verbal yes is not proof of adoption.
Counterfeit and confirmation yeses are common. Commitment requires how. Never take a bad deal simply to have a deal.
Real agreement
- Shared summary that earned “that’s right”
- Explicit terms and implementation path
- Affected stakeholders and a named owner
- A date and a defined failure response
Rule of three
- Treat the first agreement as unproven
- Give a summary that earns “that’s right”
- Ask: “How will this actually get done?”
Notice unexpected details, test assumptions, find hidden constraints, and update the recommendation. If fit changes, revise scope, change terms, or disqualify.
08 · Selling with love
Curiosity plus competence plus the client's problem.
Productive energy = curiosity + competence + client problem. Hype = enthusiasm − evidence.
Love impact
Define a measurable better state — the five-second moment made operational.
Love client
Understand reality; keep them as protagonist; recommend only if fit.
Love product
Know the mechanism; prove honestly; expose limits.
Love process
Make each interaction useful and preserve choice.
Love self
Prepare deeply and act without desperation.
09 · Sales methods
Collect scenes. Bring one moment to clarity.
Discovery
“Where does the current system stop matching physical reality?”
Listen → ask → observe an artifact → model operational logic → confirm understanding. Do not extract pain points as abstractions. Collect scenes.
- Physics
- Rules the software must respect.
- Friction
- Spreadsheet, reentry, workaround, or manual decision.
- Leakage
- Material, time, capacity, quality, cash, or risk.
- Desired state
- The five-second moment, made measurable.
- Required proof
- Evidence the buyer defines as sufficient.
- Change context
- Incumbent, cost, tolerance, constraints, owners, and decision process.
Demonstration
Begin at the opposite — their current artifact. End at the moment their work matches the system. Everything that does not serve that moment is cut.
- 01 · Model
Reproduce the customer workflow with native core.
- 02 · Modify
Implement one customer-specific requirement with Builder.
- 03 · Decide
Answer one live operational question with Logic Pilot.
- 04 · Execute
Draft or run one approved action with auditability.
Proof ladder
- Observe a customer artifact
- Reproduce the data model
- Build a customer-specific prototype
- Test acceptance criteria
- Validate a comparable reference
- Present the transition plan
Qualification
A deal is qualified only with fit, material impact, a sponsor, possible proof, a known decision process, and understood transition risk.
Value
Value combines material savings, throughput, labor reclaimed, avoided quality and expedite costs, and avoided technology or consulting — minus transition cost.
Next step
Valid: artifact, buyer owner, Naologic owner, due date, meeting date, and acceptance criterion. Vague follow-up is not a next step.
10 · Never
If it requires pressure, it is not ready.
- Manufacture fear or weaponize loss aversion
- Use false deadlines or extreme anchors without basis
- Frame compliance as fairness or seek counterfeit agreement
- Shame buyer responses or conceal uncertainty
- Apply pressure when encountering resistance
- Split the difference merely to relieve tension
- Stack labels, mirrors, or calibrated questions as a script
- Tell seller-as-hero stories or and-then feature chronicles
- Invent a false future to create suspense
- Explain the moral after the moment is already clear
Recognition sounds like “that’s right” — not like “yes.”