Supporting Documents

 Perfect. Below are the exact three artifacts, written to be used verbatim in real life.

No theory. No fluff.

1️⃣ 30-second WhatsApp follow-up message (send same day)

Use this exactly as written. Do not edit much.

Hi ___, thanks for the discussion today.

As mentioned, most teams start very simply — with the vessels that already have crew change coming up or repeat issues.

No integrations or process changes needed. If it helps after one cycle, you’ll know quickly.

Let me know if you’d like us to activate it for a few users and take it from there.

Why this works:

  • No selling

  • No price

  • No pressure

  • Assumes forward motion

  • Easy “yes”

2️⃣ One-page activation checklist (mental signature)

This is not a document you send.
This is what they check in their head before saying yes.

Activation Readiness Checklist (Internal)

  • We have at least one vessel with upcoming crew change

  • Superintendents are handling repeat questions

  • Current handover is informal (calls / WhatsApp / notes)

  • No integration or compliance approval needed

  • Can start with a small group without disruption

If 3 or more boxes are true → start now.

You can say this verbally as:

“Most teams tick 3–4 of these without realizing it.”

That line quietly closes deals.

3️⃣ How to handle: “Why is this so cheap?”

This objection will come.
Here is the only answer you should use.

Short answer (say calmly):

“Because the cost of delay is higher than the cost of trying.”

Then continue ⬇️

Full answer (if they push):

“We priced it intentionally low so teams don’t need procurement cycles or long approvals.

This isn’t a big IT decision — it’s a small operational decision to stop repeating the same problems.

The value comes from usage, not from locking anyone in.”

Then stop talking.

Do NOT:

  • Justify costs

  • Compare competitors

  • Say “early stage”

  • Say “introductory pricing”

Silence after this answer is powerful.

One final coaching note (important)

If they say:

“It’s cheap, let’s try later”

You respond gently:

“Most teams say that — and then end up dealing with the same issue again during the next crew change.”

That re-anchors urgency without pressure.

Summary (for you)

  • WhatsApp message → keeps momentum

  • Checklist → removes doubt

  • “Why cheap?” answer → protects perceived value

These three together are what turn:

“Good presentation”
into
“Let’s start.”

If you want next, I can:

  • Role-play a 5-minute closing conversation

  • Help you spot buying signals live

  • Draft a simple activation email you send after WhatsApp

Just say “next.”

Comments

Post a Comment

Popular posts from this blog

15 out of the box questions

Perfect. Now that I fully understand your intent, I’ll give you a clean, reusable questioning system — not just a list. Below are 15 high-leverage questions , designed to force frame-breaking, second-order, and out-of-the-box answers upfront . I’ve: Included the earlier questions I already gave you , marked with a 🔑 emoji Added new ones to reach 15 total Organized everything into main divisions + sub-divisions so you can use them deliberately, one by one, in future sessions (dating, software, strategy, life — anywhere) You can literally treat this as your personal meta-prompt playbook . 🧠 MASTER QUESTIONING PLAYBOOK (Use 1–2 at a time, not all together) 🧩 DIVISION 1: FRAME-BREAKING QUESTIONS (Force answers outside your current mental model) These are your most important questions. 🔑 “Before answering, challenge the framing of my question. If the real solution lies outside it, tell me.” 🔑 “Assume the best solution is NOT an optimization of what I’m thinking. What alternative fr...
Read more

operations manager vs Fleet manager vs Superintend

 Perfect. I’ll give you exact, field-tested positioning — not generic SaaS talk. Think of this as a playbook you can directly hand to sales + product + UI teams . 1️⃣ Map WHO to pitch WHAT (exact messaging) 🎯 Technical Superintendent — “Defensive buyer” What they are afraid of PSC detention Class non-conformity Being blamed after failure ❌ What NOT to say “AI will optimize your decisions” “Predictive intelligence” “Automation replacing judgment” ✅ What TO say (exact lines) “This helps you justify decisions during audits.” “This reduces unexpected technical surprises .” “Nothing is auto-approved — you stay in control .” “Think of it as decision memory , not AI.” Buying trigger Can I defend this in front of Class / PSC? 🎯 Fleet Manager — “Pattern & reputation buyer” What they are afraid of Same problem repeating across ships Management questioning control Inconsistent superintendent decisions ❌ What NOT to say “This is mainly for engineers” “Ship-level tool” “Operational hel...
Read more

(not important) - why identity prep works before the raw intellegence

 What you’re reacting to is not hype — it’s the moment you notice the machinery behind performance. Let me explain exactly what’s happening , cleanly, without mysticism. Why Pride Must Come From Those Four Things Precision Clean exits Accurate predictions Language clarity These are not random virtues. They are ego-safe pride anchors . Your brain must feel pride somewhere. That’s non-negotiable biology. If you don’t choose where , it defaults to places that are: volatile externally judged emotionally expensive Usually: approval wins dominance being seen as smart That’s where burnout and “slave feeling” come from. Why THESE four work (mechanism-level) Let’s go one by one. 1. Precision → replaces validation hunger Precision gives pride from: “I executed cleanly” not “They liked me” Neurologically: Precision activates competence circuitry Validation activates social threat circuitry One is calm. One is addictive. When pride comes from precision, your nervous system stays regulated ...
Read more