44 documents
Sales & Playbooks⏱️4 min read

Pitch script — non-technical owners

Source: `../source/JSGlobtech_GEO_Agency_Playbook.pdf` §4 (Non-Technical Client Pitch Script), extracted 2026-07-30. Reproduced as written; commentary is clearly separated.

Pitch script — non-technical owners

Source: ../source/JSGlobtech_GEO_Agency_Playbook.pdf §4 (Non-Technical Client Pitch Script), extracted 2026-07-30. Reproduced as written; commentary is clearly separated.

Audience and rule

For non-technical business owners — clinic directors, agency owners, rental company principals. The standing instruction is to avoid technical jargon: no "schema", no "JSON-LD", no "Model Context Protocol", no "endpoint". The buyer cares about missed patients and missed bookings.

The script

1. Open with the behaviour shift

"When high-net-worth clients in Dubai want to find a service, over 40% are now skipping Google completely and asking ChatGPT or Perplexity questions like: 'Who is the top-rated clinic for rhinoplasty with clear pricing in Dubai?'"

⚠ The "over 40%" figure is unsourced — see ../strategy/kpis.md before saying it to a prospect.

2. Name the loss

"Right now, if they ask that, AI recommends your competitors because your website isn't built to talk to AI engines. At JSGlobtech, we do two simple things for you:"

The move is to make the problem concrete and already-happening rather than hypothetical. It lands hardest if you have actually run their query first — see ./demo-framework.md.

3. The two things (the entire offer, in plain language)

  1. AI Search Visibility — "We rebuild your digital presence so ChatGPT actively recommends your business over everyone else."
  2. Instant Lead Capture — "We install a digital receptionist inside the chat interface so when a user says 'Book me a consultation', their contact details land directly in your WhatsApp or CRM instantly."

These map to the two layers in ../strategy/positioning.md: the visibility layer (GEO) and the action layer (MCP). "Digital receptionist" is the load-bearing metaphor — it explains an MCP tool to someone who has never heard of one, in two words.

4. Close on economics

"If this brings you just one extra client a month, the entire system pays for itself. Everything beyond that is pure profit."

Checked against real numbers in ../strategy/kpis.md: sound for Tier 1 and Tier 2 across all four target verticals, but it does not hold for Tier 3 at the low end — a $4,000+/mo retainer is not covered by one $3,000 car rental. Don't use it verbatim on a Tier 3 car-rental pitch.

It is also a retainer breakeven, not setup + retainer. Fair as a steady-state argument; be ready to say so if the buyer does the arithmetic out loud.

Delivery notes

  • Do the search before the call. Run the prospect's own query on ChatGPT or Perplexity and note who gets cited instead of them. Step 2 stops being a claim and becomes a finding.
  • Keep "digital receptionist"; drop everything else. If the buyer asks how it works, the answer is "we give the AI a direct line into your CRM" — not a protocol explanation.
  • Don't promise booking or reservations. The playbook's §1 mentions booking consultations and processing reservations. Neither is implemented today (../integrations/mcp-server.md); the shipped capability is lead capture. Say "their details land with you instantly", which is true, rather than "the AI books the appointment", which is not yet.
  • WhatsApp caveat. The script says details "land directly in your WhatsApp or CRM". Today that is a single webhook that can be pointed at whatever the client uses; a WhatsApp channel is not pre-wired. Deliverable, but scope it rather than assuming it.
  • Have the demo ready. The natural next line after the close is "let me show you on our own site" (./demo-framework.md).
  • ./outreach-templates.md — the cold email that earns this conversation
  • ./demo-framework.md — the proof that follows it
  • ./pricing-tiers.md — ⚠ read the pricing warning before naming a number