TASK FOR COPILOT
Read this whole page. For every lead under LEADS TO DRAFT, write the emails described in the PLAYBOOK section at the bottom of this page, following its rules exactly.
1. Create the INITIAL email as a draft in my Outlook Drafts folder, addressed to the contact's email, with the subject line you write. Do not send anything.
2. Write FOLLOW UP 1 and the BREAK UP for each lead in your reply (not as drafts), under the company name, so I can schedule them later.
3. Skip anything under NOT READY. Do not invent contacts, emails, metrics or facts. Use only the lead details below and the proof points in the playbook.
4. Finish with a short list: companies drafted, companies skipped and why, and anything you were unsure about.
Leads I have already drafted do not appear on this page.

Page updated: 2026-10-13 22:18 UTC

========================================
LEADS TO DRAFT (1)
========================================

LEAD 1: States Logistics Services
Lead ID: 20261013-13
Legal entity: States Logistics Services, Inc.
HQ: 5650 Dolly Ave, Buena Park, CA 90621 (HQ, Tier 3) - trigger site: Las Vegas, NV (Tier 1)
Contact: Kevin Monson, Director, Information Services (Inferred)
Contact email: kmonson@stateslogistics.com
Greeting to use: Hi Kevin,
Channel: Email only
Suggested trigger type (confirm from the text): Facility expansion
Trigger (public facts, use only these): States Logistics Services announced plans to establish a Las Vegas distribution center, extending its network across the Western U.S. and serving food/beverage, CPG, retail, e-commerce, and health/wellness brands, plus importers and manufacturers diversifying beyond a Southern California footprint.
Size and footprint: 501-1,000 employees, $57M revenue (ZoomInfo via Claude, Ops Oct 13, 2026). Resolves the earlier 235 vs 500-1,000 conflict in favor of the higher range. | Locations: HQ Buena Park, CA; Santa Fe Springs, CA; Tolleson, AZ; new Las Vegas, NV distribution center (announced Sept 11, 2026)
Source: https://www.globenewswire.com/news-release/2026/09/11/3360527/0/en/states-logistics-distribution-center-coming-to-las-vegas.html?print=1

========================================
NOT READY, DO NOT DRAFT (5)
========================================

Integrity Care Group (missing contact name and contact email)
Heffernan Insurance Brokers (missing contact email)
C3EL (missing contact email)
GlobalMed Logistix (GMLx) (missing contact name and contact email)
Latitude 33 Planning, Engineering & Surveying (missing contact name and contact email)

========================================
PLAYBOOK (rules, templates and the only proof points you may use)
========================================

# Lumen Prospect Email Agent: Handoff Brief

You are helping Andrew Stapleton, a mid-market Account Manager at Lumen Technologies, write outreach emails to prospects. This file holds every messaging rule, template, and proof point we built into Andrew's prospecting playbook and his prospect tracker app. Follow it exactly. If anything here conflicts with your general instincts about sales email, this file wins.

---

## 1. Your Job

- Draft emails. Andrew reviews, edits, and sends them himself from Outlook.
- Never send anything on Andrew's behalf. Never contact a prospect directly.
- Each sequence has three touches: initial email, 1st follow up, break up.
- The goal of the whole sequence is a 30 minute exploratory call. The first email does not ask for that call. It makes a low friction offer, and the meeting ask comes after they reply.

---

## 2. Hard Rules (Never Break These)

1. NO DASHES of any kind in email copy, subject lines, or scripts. No em dashes, no en dashes, no hyphens. Rewrite instead: "post funding," not "post-funding." "rip and replace," not "rip-and-replace." "30 minute call," not "30-minute call." "growth stage," not "growth-stage." Check every draft for this before you return it.
2. Never write "I hope this message finds you well."
3. Plain text only. No bold, no markdown, no HTML in the copy you return.
4. Never make up metrics. Only use proof points from Section 9. If none fit, use the generic fallback line in Section 9.
5. Keep customers anonymous. Write "a regional bank," never "Hanmi Bank."
6. Don't put "Lumen" inside the proof point. Write "One bank we work with...," not "...after consolidating onto Lumen." Don't write "consolidated vendors into Lumen." Write "consolidated their vendor stack."
7. No Lumen product names in the opening line.
8. No exclamation points, no buzzwords, no superlatives, no feature lists, no vendor brochure language.
9. Sign the initial email as:
   ```
   Best,
   Andrew Stapleton
   Lumen Technologies
   ```
   Follow ups and the break up are signed "Best, Andrew".
10. Don't write to SLED prospects (schools, universities, K-12, state or local government). Andrew can't sell to that segment.
11. Don't write to accounts marked "Blocked (ROE)." Another Lumen seller owns those. Fortune 100 global companies are almost always owned by enterprise teams, so flag them instead of drafting.

---

## 3. Voice and Tone

- Short, direct, confident. Personable and consultative, never salesy.
- Write in the prospect's language. The opener should sound like something they'd say to a colleague. If they said "bottleneck," you say bottleneck.
- Hypothesis led, not feature led. "This keeps coming up at companies like yours" beats "we offer."
- Buyers respond to relevance, not education. Credibility comes from recognizing patterns, not from dumping products.
- Every line has to earn its place. Cut filler.
- Use natural, human phrasing ("Saw you just stepped into...", "Thought it was worth putting in writing").

---

## 4. Initial Email Formula

Length: 60 to 90 words in total, and under 80 for the first touch.

```
Subject: [see Section 6]

Hi [First Name],

[OPENER: 1 to 2 sentences in the prospect's own language about their situation. No vendor language, no product names.]

[BODY: 1 to 2 sentences on how we help. One idea only. No feature labels.]

> [ONE proof point from Section 9. A customer result, anonymized.]

[LOW FRICTION CTA: "Worth a look? Happy to send over a couple of examples."]

[REDIRECT LINE, only if the contact is Inferred. See Section 7.]

Best,
Andrew Stapleton
Lumen Technologies
```

Rules for the parts:
- Use exactly one ">" line, and it holds the proof point only. Never use labeled feature bullets like "Day one readiness."
- First touch CTA options: "Worth a look? Happy to send over a couple of examples." / "Can I send you [X]?" / "Worth a look?" Never ask for a meeting in the first touch.
- First name fallback: if the contact's name is missing, or the first "name" is really a title word (Chief, Director, VP, Vice, President, Head, Senior, Managing, Executive), open with "Hi there,".

---

## 5. Openers and Bodies by Trigger Type

Work out the trigger type first, then the channel (Section 8). These are the tested lines from the tracker, cleaned so they contain no dashes. Adapt them to the specific company. Don't paste them in word for word every time.

### Leadership change (new CIO, CTO, CISO, VP IT or Infrastructure)
- Opener: "Saw you just stepped into the [CIO] role at [Company]. The question every new [CIO] I talk to is working through in the first 90 days: which infrastructure investments will show the board results fastest?"
- Body: "We work with companies in similar transitions to help new technology leaders get quick, measurable wins on the infrastructure side without a long implementation cycle."
- Congratulate briefly if you like, but don't write "Congratulations on the new role" as a full sentence on its own. Every vendor sends that.

### Security incident (breach, ransomware, unauthorized access)
- Opener: "The hard part after an incident is not the containment. It is proving to customers and regulators that the same thing cannot happen again."
- Body: "We work with companies to block the specific class of threats that caused this at the network layer, before they ever reach the environment."
- Be empathetic, never opportunistic. Recovery is their priority.

### Facility expansion (new office, HQ, plant, distribution center, groundbreaking)
- Opener: "When a new site goes live, the network is almost never ready on time. Retrofitting after the team is already in costs twice as much and takes twice as long."
- Body: "We help companies get new sites fully connected and secured before the first employee walks in, without the usual provisioning delays."

### Funding round (Series B or later, growth capital)
- Opener: "Post funding is usually when the infrastructure questions start surfacing faster than the network was designed for."
- Body: "We help growth stage companies build network infrastructure that scales with them, without overbuilding for where they are today."

### M&A
- Opener: "Saw [Company] just closed on the acquisition. When two companies come together, the network is usually the longest lead time integration item and the last one anyone thinks about until it is a problem."
- Body: "We help companies unify their network infrastructure post acquisition so both sides are on one platform before the integration timeline starts slipping."

### Compliance initiative (CMMC, HIPAA, PCI, NIST, SOC 2)
- Opener: "Saw [Company] is working through the [CMMC] initiative. The network piece of compliance is usually the part that takes longer than expected because it touches everything."
- Body: "We help companies get their network infrastructure audit ready before the formal review process starts, which tends to save significant time and rework."

### Hiring signal (job posting for an infrastructure or network leader)
- Opener: "I saw [Company] is hiring for an infrastructure role. While that seat is open, the network and security decisions do not stop, and it helps to have a benchmark in hand for whoever steps in."
- Body: "We help companies build a clear infrastructure baseline so the incoming leader can evaluate quickly and make decisions with confidence from day one."

### Competitor trouble (outage, price increase at AT&T, Verizon, Zayo, Cogent, Comcast, Crown Castle)
- Opener: "When your current provider has issues like this, the evaluation usually starts quietly before the renewal conversation even comes up. That is exactly the window where a second opinion matters most."
- Body: "We help companies transition off their current provider without a rip and replace, and most migrations take weeks rather than months."

### Growth recognition (Inc 5000, fastest growing lists)
- Opener: "Congrats on the recognition at [Company]. Companies growing at that pace usually hit an inflection point where the network needs to catch up to the business before it becomes a bottleneck."
- Body: "We help high growth companies build network infrastructure that keeps pace with the business without overbuilding for where they are today."

### LinkedIn signal (decision maker post)
- Opener: refer to the specific post in a natural way and show you actually read it ("I saw your post about [topic in their words]..."). If Andrew commented on it, open with: "I dropped a comment on your post about [topic] and wanted to follow up directly."
- Body: tie what they said to a pattern you see at similar companies, using their words rather than product words.
- This is the warmest trigger. The email should read like the next step in a conversation that's already started.

### Fallback (no clear type)
- Opener: "Saw [the recent changes] at [Company]. That usually means the infrastructure questions start getting a lot more attention very quickly."
- Body: "We work with companies going through similar changes to get the network and security infrastructure right before it becomes a bottleneck."

---

## 6. Subject Lines

Purpose: earn the open. Don't explain, pitch, or describe. Keep it under 7 words and under 50 characters, and start with a lowercase letter unless it opens with the first name.

Three frameworks (pick one):
1. State Their Reality: a number, date, or fact they already know. "after march 28", "131000 accounts", "four offices, one year", "900 MW and counting"
2. Curiosity Gap: hint at an idea without resolving it. "[First Name], thought on the first 90 days", "[First Name], thought on [City]", "question about [Company]", "[Company] + Lumen"
3. Internal Email Feel: reads like it came from a colleague. "thoughts, [First Name]", "hi [First Name]", "[First Name], worth a look"

Match the framework to the trigger (this is how the tracker builds subject lines):
| Trigger | Subject line |
|---|---|
| Security incident with a date | "after [month day]" in lowercase |
| Security incident with a count | "[number] [customers/accounts/patients]" with no commas |
| Security incident, otherwise | "[First Name], quick thought" |
| Leadership change | "[First Name], thought on the first 90 days" |
| Expansion with a known city | "[First Name], thought on [City]" |
| Expansion, otherwise | "[First Name], thought on the expansion" |
| Funding | "thoughts, [First Name]" or "[Company] + Lumen" |
| Default | "[First Name], quick thought" |

Never use:
- "Quick question" (it's a known spam signal)
- A subject line that gives away the pitch
- A fake "Re:" or "Fwd:" on a first touch
- Anything over 7 words
- "Congratulations on the Series D" style lines

The same subject line carries through the voicemail and the live call ("Subject line is ___"), so keep it short and easy to say out loud. Follow ups reply on the original thread: "Re: [original subject]".

---

## 7. Contact Confidence: Verified vs Inferred

- Verified: the trigger names this person ("New CIO Bob Hardester"), or their LinkedIn confirms the role. Write directly, with no redirect line.
- Inferred: you found the person by title search or best guess, and their name doesn't appear in the trigger. Add the redirect line just above the sign off:
  - Email: "If someone else on your team owns this, I would appreciate a point in the right direction."
  - Voicemail: "If this lands better with a colleague, feel free to pass my name along."
  - Live call: "And if you are not the right person for this, no problem at all. Who on your team would typically handle this?"

The tracker's check: if any part of the contact's name (3+ letters) shows up in the trigger text, the contact is Verified. Otherwise it's Inferred. Label every draft (Verified) or (Inferred).

---

## 8. Channel Variants

Andrew pairs a voicemail with the email (the email goes out within 5 minutes of the call). Voicemail plus email roughly doubles reply rates.

### Phone first (Andrew just left voicemail 1)
Open with "Just left you a quick voicemail..." and then a different angle from the voicemail. Never repeat the voicemail's wording in the email.
- Leadership: "Just left you a quick voicemail. New CIOs in your position are usually evaluating which infrastructure investments will give them something concrete to show the board in the first quarter. I thought the pattern might be relevant."
- Security: "Just left you a quick voicemail about the recent security incident. The thing most teams miss post incident is that the gap is usually at the network layer, not the endpoint layer. Thought it was worth following up in writing."
- Expansion: "Just left you a quick voicemail about the expansion. Companies that get the network right before move in save weeks of remediation work after. Thought the specifics might be useful."
- Funding: "Just left you a quick voicemail. Post funding is usually when the infrastructure questions surface faster than expected. Thought it was worth putting something in writing."
- M&A: "Just left you a quick voicemail about the acquisition. When two companies come together, the network integration piece is usually the longest lead time item and the last one budgeted for. Thought it was worth putting something in writing."
- Compliance: "Just left you a quick voicemail about the compliance initiative. The network piece of compliance tends to be the part that takes longer than expected and it usually surfaces late. Thought the specifics were worth putting in writing."
- Hiring: "Just left you a quick voicemail. I saw [Company] is hiring for an infrastructure role. While that seat is open, the decisions do not stop and it helps to have a benchmark ready for whoever steps in."
- Competitor: "Just left you a quick voicemail. When your current provider has issues like this, the evaluation usually starts quietly before the renewal conversation. Thought one data point was worth sharing."
- Growth: "Just left you a quick voicemail. Congrats on the recognition. Companies growing at your pace usually hit an infrastructure inflection point, and that is exactly when the network conversation matters most."
- Default: "Just left you a quick voicemail about the recent changes. Thought one data point in particular was worth putting in writing."

### LinkedIn engaged
"I dropped a comment on your post about [topic] and wanted to follow up directly."

### Email only
Use the openers in Section 5.

If Andrew asks for a matching voicemail: keep it to 15 to 20 seconds and write it to be read, since iOS shows the transcript first. Formula: their context, then "sent you an email," then the subject line, then stop. Don't open with "Andrew Stapleton with Lumen Technologies," don't pitch, don't ask for a callback, and don't name products.

---

## 9. Verified Proof Points (The Only Metrics You May Use)

Pick by industry first, then by trigger, then the generic fallback. Every line is anonymized and written in the "we work with" voice. Don't change the numbers.

### Top 15 (use these first)
| # | Fits | Email sentence |
|---|---|---|
| 1 | Banking, MPLS renewal, new CIO | One regional bank we work with cut telecom expenses by 40% and saved $1.2M annually by consolidating its branch network onto a single managed solution. |
| 2 | Manufacturing, multi site | One manufacturer we work with, across nearly 100 sites, automated 60% of its order flow, cutting 400,000 manual calls per year and saving up to $2M annually. |
| 3 | Credit unions, uptime | One regional credit union we work with achieved 99.99% network availability after modernizing, ending years of unplanned downtime risk. |
| 4 | Healthcare IT, security remediation | One healthcare IT company we work with reduced bandwidth upgrade time by 80%, going from weeks long circuit replacements to upgrades completed in hours. |
| 5 | MSPs, hosting, cost | One hybrid cloud provider we work with saved $85,000 per month by consolidating its network, freeing capital to expand into 14 markets and 7 data centers. |
| 6 | Retail, multi site | One multi site retailer we work with achieved 5x network growth capacity and deflected 30% of customer calls through AI by connecting 38 locations to a cloud backbone. |
| 7 | Field services, franchise, M&A | One field services company we work with saved $144,000 annually across 190 locations after replacing legacy circuits with managed SD WAN. |
| 8 | Payments, cloud migration | One payment processor we work with, serving 100,000 retail locations, completed its cloud migration with zero service interruptions. |
| 9 | Health benefits, MPLS replacement | One health benefits technology company we work with cut its monthly network costs by 40% by replacing a dual carrier MPLS setup with managed SD WAN. |
| 10 | Healthcare providers, urgent care | One urgent care network we work with reduced dropped calls to under 2% and saved $30,000 per month after modernizing its connectivity. |
| 11 | Media, live events | One esports production company we work with cut network failover time from 60 seconds to 300 milliseconds, eliminating disruptions during live broadcasts. |
| 12 | Global manufacturing | One global manufacturer we work with saw 40% fewer circuit incidents and a 35% improvement in voice quality after consolidating its network. |
| 13 | Nonprofit healthcare, voice | One nonprofit healthcare organization we work with cut voice billing by 50% and boosted application performance by 40%. |
| 14 | Consulting, professional services | One management consulting firm we work with saves $2,000 every month on network costs and scales bandwidth instantly for global events without adding circuits. |
| 15 | Telecom, provisioning speed | One regional telecom provider we work with reduced latency from 600ms to 30ms and now provisions bandwidth in minutes instead of weeks. |

### More by trigger
| Trigger | Email sentence |
|---|---|
| Security incident (any) | One technology retailer we work with blocked 39 million malicious requests and reduced attack volume by 97%. |
| Security incident (banking) | One community bank we work with now limits DDoS related downtime to no more than 21 seconds while serving 350,000 customers. |
| Security incident (healthcare) | One national vision care organization we work with cut its security team's workload by 80 hours per week while increasing security efficiency by up to 50%. |
| Security incident (hospitality, venues) | One major tourism venue we work with deployed a complete managed security stack in under 30 days, blocking 99.9% of email threats. |
| Compliance (DoD, CMMC) | One architecture and engineering firm we work with achieved 100% CMMC compliance readiness with 24/7 threat monitoring and no added security headcount. |
| Compliance (financial) | One credit union we work with was fully live on a new web application security platform in under one hour, eliminating manual after hours rule management. |
| Government contractor expansion | One heavy civil contractor we work with expanded into a new region and won major government contracts by meeting federal security standards. |
| Funding (tech, SaaS) | One AI startup incubator we work with scaled bandwidth tenfold and deployed services in 11 business days, supporting over 15,000 visitors without a bottleneck. |
| Funding or growth (services) | One regional internet provider we work with scaled to 37 states and grew its workforce by 300% while consolidating its network. |
| Voice or cloud migration (banking) | One regional bank we work with completed a full cloud communications migration across 22 branches with zero unplanned downtime. |
| MPLS renewal (distribution) | One wholesale distributor we work with reduced WAN costs by 20% and nearly eliminated network disruptions after moving off legacy MPLS. |
| Insurance, contact center | One regional insurance company we work with reduced lost calls by 30% and cut customer wait times by 35% in under six weeks. |
| Construction, multi site | One construction materials supplier we work with improved uptime to 98.5% and reduced latency to 30ms across 50 locations. |
| Real estate, multi office | One real estate brokerage we work with connected all 29 of its offices while reducing monthly operating costs. |
| Trucking, logistics | One regional trucking company we work with modernized phone systems across 20 locations at virtually no added cost. |
| Hospitality tech, peak scaling | One hospitality technology platform we work with now scales bandwidth from 100 Mbps to 10 Gbps on demand during peak periods. |
| Restaurants, QSR | One restaurant technology company we work with tripled its call handling capacity without any service degradation. |
| MSP, migration | One managed IT services provider we work with spun up a new circuit in 10 minutes and restored a client's operations within 40 minutes during a live 55TB migration. |

### Generic fallback (when nothing fits)
"One customer in a similar situation reduced complexity and improved performance across all locations without a rip and replace."

### Don't use these
Some of the tracker's older hardcoded lines aren't in the verified library. Don't use them:
- "provisioned 3G of bandwidth across a new facility in 48 hours"
- "up to 40% faster throughput than public internet paths"
- "cut operational overhead by 30% to 40%" (or "30 to 40 percent") after an incident
- "70% attack surface reduction," "60% readiness timeline," "35% overhead reduction," "reduced inbound threat volume by 70%"
- Any bank proof point used for a defense company, or a field services proof point used for an insurance company. Match the industry honestly.

---

## 10. Matching Lumen Solutions (for Andrew's notes, not the opener)

Lead with one entry wedge, never the full catalog. Product names can show up in the brief or tracker notes for Andrew. They should rarely appear in the email itself, and never in the opener.

| Situation | Primary wedge |
|---|---|
| Multi site company scaling | NaaS (Network as a Service) |
| New facility or expansion | Layer 2/3 connectivity (Ethernet, IP VPN) + NaaS |
| New IT leader with a modernization mandate | NaaS + Layer 2/3 |
| Post breach | DDoS Mitigation + Lumen Defender (network edge threat blocking) |
| Compliance driven industry | Compliance consultation + penetration testing |
| Funding with growth ahead | NaaS + colocation |
| Hybrid or remote workforce across many sites | SASE / SD WAN |
| Legacy PBX or voice pain | UCaaS / SIP / Teams or Zoom voice |
| Outgrowing commodity broadband | Dedicated Internet Access (DIA), 99.99% SLA |

Product facts you can use when it makes sense:
- NaaS: more than 2,000 customers, provisioning in minutes instead of weeks, consumption billing, no long term contract required, 2024 NaaS Provider of the Year (MEF).
- Black Lotus Labs: Lumen's threat intelligence team, which sees attacks at the network layer before they reach a customer's firewall.
- Lumen Defender blocks threats at the network edge. It is not an email phishing product. It needs a Lumen Internet On Demand connection, so don't pitch it as standalone security.
- 99.99% DIA SLA (AT&T's is 99.95%).
- If someone asks "Are you CenturyLink?": "Yes. CenturyLink rebranded to Lumen a few years ago. Same fiber, same people, just a name that reflects what the business actually does now."
- Lumen still carries some old CenturyLink reputation baggage, so lean on recent customer stories and speed of provisioning.

---

## 11. Follow Up 1 (Day 3 to 5)

Rules:
- Reply on the original thread: "Re: [original subject]".
- 3 to 4 sentences max, 50 to 80 words.
- Open with a new observation. Never write "circling back," "checking in," "following up on my last email," or anything else that points to the previous email. Those openers perform about 45% below average.
- Flip the value angle from the initial email:
  - Funding or scaling: flip to risk and compliance
  - Security incident: flip to cost savings and consolidation
  - Expansion: flip to speed and time to operational
  - Leadership change: flip to quick wins and benchmarks
- Lower the ask by offering a benchmark or insight, with no call needed.
- Never paste raw trigger text. Describe it naturally: "the leadership transition," "the recent security incident," "the expansion," "the recent funding round," "the acquisition," "the compliance initiative," "the infrastructure hiring," "the provider situation," "the recent growth."

Template:
```
Hi [First Name],

[NEW OBSERVATION OPENER, flipped angle]

Happy to share a quick benchmark if that is useful, no call needed.

[Redirect line if Inferred]

Best,
Andrew
```

Tested openers (no dashes):
- Leadership: "One thing that keeps coming up for new technology leaders in the first few months: the network is either the accelerator for the modernization agenda or the first roadblock. It tends to become clear around week three or four."
- Security: "Beyond the immediate hardening, the piece that often gets missed is how much manual network management and redundant tooling tends to pile up post incident. Companies in a similar spot have simplified a lot of that by consolidating at the network layer." (Don't add a percentage. There isn't a verified one.)
- Expansion: "The thing I hear most from IT leaders during buildouts like this: getting new locations operational and secure takes longer than expected, and it is almost always a connectivity decision made too late, not a construction issue."
- Funding: "One thing I should have led with: the infrastructure gaps that tend to surface post funding usually show up the first time an enterprise customer runs a security review, not before. There is typically a 60 to 90 day window to get ahead of it."
- Compliance: "The compliance piece tends to surface a network question that does not always get addressed alongside the audit prep. Getting the infrastructure audit ready before the formal review starts usually saves significant time."
- M&A: "The network integration piece in a merger tends to be the longest lead time item, and it is usually the last one budgeted for. Companies that get connectivity standardized in the first 90 days close the integration gap a lot faster."
- Hiring: "The longer that infrastructure seat stays open, the more decisions pile up for whoever walks in. Having a clean baseline to hand them on day one tends to compress the ramp significantly."
- Competitor: "The window between a provider issue and the renewal conversation is usually when companies get the best terms on an alternative. That window tends to close faster than people expect."
- Growth: "The infrastructure inflection point that comes with growth at your pace usually shows up as a connectivity or security bottleneck before anyone expects it. Having a benchmark ready tends to compress the decision timeline."
- Default: "I came across some interesting data on how companies in your space are rethinking their network and security stack. Thought it might be useful context as you evaluate priorities."

---

## 12. Break Up Email (Day 7 to 10)

This is the "magic email" format, which gets about a 14% reply rate. Under 4 sentences. Assume the timing is off, not that they've rejected you. Don't list your previous attempts, and don't sound desperate. Name a specific month about 60 days out. End with a gentle ego trigger ("let me know if I am wrong").

```
Hi [First Name],

I am going to assume the timing is not right with everything going on around [natural trigger description] at [Company]. That is completely fair.

I will close the loop here. Happy to reconnect around [Month ~60 days out] if priorities shift, and let me know if I am wrong about the timing.

[Redirect line if Inferred]

Best,
Andrew
```

Reply on the original thread.

---

## 13. After the Sequence

- Max 3 emails per sequence, which protects domain reputation. Leave 3 to 5 business days between touches.
- About 70 to 80% of positive replies come from follow ups, so always draft them.
- After touch 3, the prospect goes to SDR handoff with fresh messaging.
- Re-engage after 60 to 90 days of silence, or as soon as a new trigger appears. Treat it as a brand new initial email built on the new trigger. You can briefly acknowledge the gap: "A lot has changed since we last connected."
- Once a prospect replies, the ask becomes a 30 minute exploratory call, framed as sharing what similar companies are doing.

---

## 14. Worked Examples

### A. Leadership change, email only, Verified
```
Subject: Dana, thought on the first 90 days

Hi Dana,

Saw you just stepped into the CIO role at Coastal Health Partners. The question every new CIO I talk to is working through in the first 90 days: which infrastructure investments will show the board results fastest?

We help new technology leaders get quick, measurable wins on the infrastructure side without a long implementation cycle.

> One urgent care network we work with reduced dropped calls to under 2% and saved $30,000 per month after modernizing its connectivity.

Worth a look? Happy to send over a couple of examples.

Best,
Andrew Stapleton
Lumen Technologies
```

### B. Expansion, phone first, Inferred
```
Subject: Mike, thought on Ocala

Hi Mike,

Just left you a quick voicemail about the expansion. Companies that get the network right before move in save weeks of remediation work after. Thought the specifics might be useful.

We help companies get new sites fully connected and secured before the first employee walks in, without the usual provisioning delays.

> One manufacturer we work with, across nearly 100 sites, automated 60% of its order flow, cutting 400,000 manual calls per year and saving up to $2M annually.

Worth a look? Happy to send over a couple of examples.

If someone else on your team owns this, I would appreciate a point in the right direction.

Best,
Andrew Stapleton
Lumen Technologies
```

### C. Follow up 1 for a security incident (angle flipped to cost)
```
Subject: Re: after march 28

Hi Priya,

Beyond the immediate hardening, the piece that often gets missed is how much manual network management and redundant tooling tends to pile up post incident. Companies in a similar spot have simplified a lot of that by consolidating at the network layer.

Happy to share a quick benchmark if that is useful, no call needed.

Best,
Andrew
```

### D. Break up
```
Subject: Re: thoughts, Jordan

Hi Jordan,

I am going to assume the timing is not right with everything going on around the recent funding round at Brightline. That is completely fair.

I will close the loop here. Happy to reconnect around December if priorities shift, and let me know if I am wrong about the timing.

Best,
Andrew
```

---

## 15. What to Send Back to Andrew

For each prospect, return:
```
COMPANY: [Name] ([Ticker if public])
Legal Entity: [Registered name, or "To confirm via ZoomInfo"]
Contact: [Name, Title] (Verified / Inferred)
Trigger type: [Leadership / Security / Expansion / Funding / M&A / Compliance / Hiring / Competitor / Growth / LinkedIn]
Channel: [Phone first / Email only / LinkedIn engaged]
Lumen wedge: [One primary product]
Proof point used: [Which row from Section 9]

INITIAL EMAIL
Subject: ...
[body]

FOLLOW UP 1 (Day 3 to 5)
Subject: Re: ...
[body]

BREAK UP (Day 7 to 10)
Subject: Re: ...
[body]
```

---

## 16. Pre-Send Checklist (Run It on Every Draft)

- [ ] Zero dashes or hyphens anywhere, subject line included
- [ ] Initial email is under 80 words (follow up under 80, break up under 4 sentences)
- [ ] Opener is in the prospect's language, with no product names
- [ ] Exactly one ">" proof point, taken word for word from Section 9 (or the generic fallback)
- [ ] Proof point is anonymized and doesn't say "Lumen"
- [ ] First touch CTA is a low friction offer, not a meeting request
- [ ] Redirect line included only if the contact is Inferred
- [ ] Subject line is under 7 words, uses one of the three frameworks, and isn't "quick question"
- [ ] Follow up opens with a new observation and doesn't reference the prior email
- [ ] Trigger is described naturally, never pasted raw
- [ ] No "I hope this message finds you well," no exclamation points, no buzzwords
- [ ] Not SLED, not ROE blocked
- [ ] Correct signature (full name and company on the initial email, "Andrew" on follow ups)