# Proposal Automation Copy

Use these messages in MySam CRM proposal workflows. Keep the tone direct and specific. Replace bracketed fields before sending.

---

## Proposal Sent

### Email

Subject: MySam proposal for `[Business Name]`

Hey `[First Name]`,

I sent over the MySam Business OS proposal for `[Business Name]`.

The key section is the leakage math: based on `[monthly_leads]` monthly opportunities, a `[missed_rate]` missed/delayed rate, and a conservative `[won_value]` value per won lead, the current monthly leak is roughly `[monthly_leakage]`.

The 1-Agent starting price is set at 30% of that estimated leak: `[starter_price]/mo`.

If the math feels off, send me your real numbers and I will adjust it. The system should be priced against the leak it closes.

-- `[Sender]`

### SMS

Hey `[First Name]`, sent the MySam proposal. The main thing to check is the leakage math: `[monthly_leakage]` estimated monthly loss, with the 1-Agent start at `[starter_price]/mo`. If your real numbers differ, I’ll tighten it.

---

## 24-Hour Follow-Up

### Email

Subject: Quick check on the MySam numbers

Hey `[First Name]`,

Quick check: did the missed-lead math in the proposal match what you see day to day?

I based it on:

- `[monthly_leads]` lead opportunities per month
- `[missed_rate]` missed or delayed
- `[close_rate]` expected conversion if captured
- `[won_value]` conservative value per won lead

If any of those are too high or too low, I can rerun the price from your real data.

-- `[Sender]`

### SMS

Did the missed-lead math look close? I can rerun the MySam price from your actual lead volume/close rate if you want it tighter.

---

## ROI Reminder

### Email

Subject: The price is smaller than the leak

Hey `[First Name]`,

One thing I want to make sure does not get buried:

The MySam agent is not priced against software. It is priced against the leak.

Estimated monthly leakage: `[monthly_leakage]`  
1-Agent starting price: `[starter_price]/mo`

If MySam recovers even part of the missed calls, slow responses, or unworked follow-ups, the system has a clear job: pay for itself by capturing opportunities that are already showing up.

-- `[Sender]`

### SMS

Main point from the proposal: MySam is priced against the leak, not the software. Estimated monthly leakage: `[monthly_leakage]`. Start price: `[starter_price]/mo`.

---

## Objection: Price

Hey `[First Name]`,

Totally fair to pressure-test price.

The clean way to look at it is this: if the monthly leak is `[monthly_leakage]`, the 1-Agent start at `[starter_price]/mo` only needs to recover `[break_even_count]` won opportunities per month to justify itself.

If that break-even number feels unrealistic, we should revisit the assumptions. If it feels realistic, the risk is not the price. The risk is leaving the leak in place.

---

## Objection: Staff Can Handle It

Hey `[First Name]`,

I get it. The goal is not to replace good staff. It is to stop forcing staff to be everywhere at once.

MySam handles the repetitive capture, routing, reminders, and follow-up so the team can focus on the conversations that actually need a human.

---

## Close The Loop

Hey `[First Name]`,

I do not want to keep poking you if this is not a priority right now.

Should I close this out for now, or do you want me to keep the MySam proposal open and revisit after `[event/date]`?