Eon SoCal Playbook

Plays & copy

Michael's rules, his two emails, call open, objections, and what stays off-limits.

Plays

Play 1 — Snapshot Audit

default

Backup bill is three lines nobody owns: snapshot storage, restore fees, extra-region copy. 2–3 week posture and cost assessment. Waste number, coverage map, restore-time. His to keep. Michael closes the platform.

Play 2 — Native backup TCO

conditional — not assigned to any of the 49

ONLY if they are on AWS Backup / Azure Backup / GCP Backup AND no Veeam / Rubrik. One week on their GB-by-service inventory vs Eon list, including $0 restores. Do not quote mix TCO as account dollars. Do not invent GB inventory. Do not assign Play 2 on any of the 49 unless stack is known — it is not, so no row gets door 2.

Play 3 — Audit-ready recovery

regulated list

Regulated list only (already marked door 3): UCLA Health, Molina, Pacific Life, PIMCO, PennyMac, Ionis, Neurocrine, Tandem, PDS, FFF, Aya, Tebra, SimplePractice. When the auditor asks who can restore what, and in what time, that answer is usually a slide.

Naming Cloud Latitude

Only if asked. They run the assessment and the cutover. Michael sells the platform. They make the number local and they staff the migration. Do not lead with it, do not put it in send copy unprompted.

Scripts

Fill [Name] and [Company] before sending. Copy buttons pull the raw text.

Email — cloud / platform / FinOps

Subject: [Company] — recoverability, not another backup SKU

Hi [Name] —

Michael Newar, Eon. I cover Southern California.

When someone asks who can restore what at [Company], and in what time, that answer is usually a slide. I want twenty minutes on recoverability: snapshot waste, restore-fee reality, and whether a second-region copy is actually doing the job.

You keep the readout whether we work together. If the number is real, I close the platform.

If this is the wrong desk, point me.

Michael Newar
Eon — Southern California

Email — CISO / GRC

Subject: [Company] — who can restore what, and in what time

Hi [Name] —

Michael Newar, Eon. Recoverability evidence, not another backup SKU.

When the auditor asks who can restore what at [Company], and in what time, most teams have a diagram. I want a short conversation on turning coverage into something you can sign: what is protected, what is restorable, and how long that takes.

Twenty minutes if useful. I will stand down if it is not.

Michael Newar
Eon — Southern California

60-second call open

[Name], Michael Newar at Eon. I will be brief. When someone asks who can restore what at [Company], and in what time, that answer is usually a slide. I run recoverability first — coverage, restore-time, snapshot waste. You keep the number. I close the platform if it is real. Is that a conversation you own, or should I be with someone else?

Objections

Objection 1 — We already have backup / native is fine

That is why we read it out. Native often bills restore, re-copies full, and charges a second in-region copy. You do not have to buy anything to see whether that is true on your estate. If the number is not real, we stop. Do not quote a mix TCO as this account's dollars.

Objection 2 — We already have a backup product

Then do not run native TCO. Recoverability still applies: who can restore what, and in what time. If they are on Veeam or Rubrik, stay on Play 1 or Play 3. Do not invent a displacement number or a SKU.

Objection 3 — Who is Cloud Latitude / why a services firm?

Answer ONLY if asked. They run the assessment and the cutover. I sell the platform. They make the number local and they staff the migration.

FFF — internal note

FFF (ACC-178) is a Veeam-displacement door, not a live HYCU customer. Recoverability is open. Do not name a competing bidder on any script for this account.

Off-limits