BirdsEye ROI, Email Sequence Library, Part 2

Sequences 6 through 10. Sequences 1 through 5 live in email-sequence-library-part-1.md. Nothing in this file has been sent. This is a review draft for Mike.

The first version of this file led with platform internals and was replaced. It is kept at email-sequence-library-part-2-v1-data-led.md.bak for reference only.

The angle, which outranks everything below

positioning-why-i-built-it.md is the authority.

For the operator: he looks at his phone for four seconds between jobs and knows what the business made. One number. The last call with a dollar next to it. A chart at the end of the day that tells him it worked.

For the agency owner: his problem is not generating calls, it is proving they were worth paying for. He wants a per service and per area report he is proud to send to a client on a Friday.

Two voices, not one. Sequence 8 is agency-native and reads peer to peer. Sequences 6, 7, 9, and 10 are written in the operator voice by default, and every email in them carries an Agency swap giving the paragraph that changes when the contact is an agency owner. Swap the paragraph, keep the rest. Never send a body that mixes the two.

Banned from every subject line, preview line, and opening line in this file: the spam share, the total call count, and the tracked revenue total. Junk calls dropping out before they reach the number may appear late in a body as reassurance. Never as the lead.

Retired, never reuse: "Most call tracking tells you the phone rang. BirdsEye tells you which ring paid." Deck only.

Offer handling, applies to every email below

The offer is a revenue share and profit share arrangement, not a subscription. Terms are discussed on a call and never written into an email. No percentage, split, tier, minimum, or deal structure appears anywhere in this file, and none may be added later without Mike's sign-off. Where an email needs to reference commercial terms, it points to the call.

Numbers

FACTS.md is a ceiling on any figure that appears, not a brief. Most emails below need no platform figure at all. Dollar figures shown in creative are product illustrations, the way a bank ad shows a balance. No client names, testimonials, quotes, logos, case studies, or results are invented anywhere in this document.

Merge fields, hard limits

Only four fields exist and are safe to merge: Business Name, City, State, Niche. All four are populated on 300 of 300 rows in icp-contacts-first-300.csv.

There is no first name. The First Name column is empty on all 300 rows, so no email in this file uses one, and none may be rewritten to use one. Roughly 128 of the 300 addresses are role inboxes (info@, service@, office@, support@, contact@, sales@, admin@, estimates@, scheduling@), which is why several emails below open with no salutation at all. That is deliberate, not an omission.

Business names run up to 92 characters and some carry commas, ampersands, and registered-trademark marks, so {{Business Name}} always sits inside a sentence and never alone on a salutation line.

Sequences 6, 7, and 9 go to people already in a conversation, where a real name may have been captured on a call. If it was, a sender may hand-personalize. The copy is written to work with nothing but the business name.

Voice rules applied

No em dashes. No emojis. No stacked hype adjectives. Short sentences. Money words over metric words: made, paid, worth, landed, not attribution, ingest, normalize, unify. Full https:// URLs. Banned words, not used anywhere in this file: revolutionary, game changer, unlock, supercharge, seamless, cutting edge.

Sequence 6: Post-proposal follow-up

Who it is for: A prospect in pipeline stage 5, Proposal. They sat through discovery and a demo, we captured their numbers, a written proposal has been delivered, and they have gone quiet.

Voice: Operator by default. Each email carries an Agency swap.

Entry trigger: Proposal delivered, plus 48 hours of no reply.

Exit trigger: Any of the following, immediately and automatically. A reply of any kind. A verbal yes or no. A booked call. A stated later date. If the prospect replies, the sequence stops and a human takes the conversation, per the cadence rule that automation never talks over a live human.

Length: 4 emails over 10 days, which matches the 10 day maximum for stage 5. If day 10 passes with nothing, the record moves to the 90 day re-approach list with a dated wake-up. It is not deleted and it does not rot in the active list.

Note for the sender: every email in this sequence assumes the proposal carried a dated decision deadline. If it did not, fix that in the proposal before running this sequence, because half of the leverage in these four emails is the date.

Email 6.1, Day 2

Subject: The one page in that proposal that matters Alternate A: Page 2, not page 4 Alternate B: Start with your own numbers

Preview text: Read the page with your numbers on it before the price page.

Body:

A short note about the proposal for {{Business Name}}, because most proposals get read in the wrong order.

The instinct is to jump to the price page. I would rather you start on the page before it, the one built entirely out of the numbers you gave me on our call. What a booked job is worth to you. What you close. What you are paying to get the phone to ring.

That page is not our pitch. It is your business, written down. If any figure on it is wrong, everything after it is wrong too, and I would rather fix it now than argue about a conclusion built on a bad input.

So the useful question is not whether you like the proposal. It is whether that page is accurate.

Agency swap (replace the second paragraph's examples):

The page before it, the one built out of the numbers you gave me. Your account count. What each account is worth to you a month. What a lost client costs you and how often it happens.

CTA: Reply with any figure on that page that looks off and I will rerun the model on the corrected number today.

Email 6.2, Day 4

Subject: The assumption worth checking before you sign anything Alternate A: What a job is actually worth to you Alternate B: The number that moves the whole model

Preview text: One input, and it moves everything downstream.

Body:

One assumption in the proposal deserves a second look, because it is the one that moves the numbers most.

It is what a booked job is worth to you. Not the ticket, the whole thing. The job plus what that customer comes back for.

Most owners underrate it by a lot, because the number that lives in their head is the invoice from the last job rather than the average across a year. Set it too low and everything downstream reads pessimistic. Set it too high and you are building on a wish.

That is the single input I would want you comfortable with before signing anything, and it is knowable from your own books rather than argued about.

Worth saying plainly: the whole point of the arrangement is that this number gets measured instead of assumed. Once every call carries a dollar, you stop estimating it and start reading it.

Agency swap (replace the second and third paragraphs):

It is what a retained client is worth to you over the life of the relationship, not what he pays you this month. Most agency owners undercount it, because the number in their head is the monthly retainer rather than the retainer times how long a happy client actually stays.

That matters here because everything this produces points at retention. A client who can see what your work was worth does not leave in month seven.

CTA: Reply "measure" and we will pin that number down against your own books before you decide.

Email 6.3, Day 7

Subject: Who else needs to see this? Alternate A: Is this waiting on someone else? Alternate B: Silence usually means one of three things

Preview text: Not a nudge. A question about who is actually in the room.

Body:

Following up on the proposal with {{Business Name}}, and being direct about why.

When a proposal goes quiet after a good demo, it is almost never because the prospect changed their mind. It is usually one of three things. It is sitting with somebody who was not on our call, a number in it needs internal checking, or something more urgent landed that week.

All three are normal. All three are also solvable faster with me involved, because I can answer a question in one email that would otherwise take your team an afternoon of guessing at what we meant.

If it is with a partner, a spouse, an operations lead, or whoever signs, I am happy to walk them through their own page of the document in fifteen minutes with no repeat of the demo. Commercial terms are a conversation, not a paragraph, so that is the right setting for them anyway.

Agency swap: none. This email is the same for both audiences.

CTA: Reply with who else needs to see it and I will send a time that works for both of you.

Email 6.4, Day 10

Subject: Your decision date is today Alternate A: Closing this out unless you say otherwise Alternate B: Open, later, or closed

Preview text: One word back and I will do the right thing with the file.

Body:

The proposal for {{Business Name}} carried a decision date, and that date is today, so this is the honest close-out rather than another follow-up.

A proposal without a deadline is a proposal nobody reads twice, which is why it had one. I am not going to pretend the date is dramatic. It just means I stop guessing and start doing whatever you actually want done with this.

Three answers, all fine.

Open, and I hold it as it stands and we talk this week. Later, and I name the quarter you give me and go quiet until then. Closed, and I close it and stop landing in your inbox.

A clean no is genuinely a good outcome from where I sit. It frees the slot and I stop spending your attention.

Whatever the answer, the thing worth keeping from all of this: make whatever you use put a dollar on the call, and make the number show up without you going to look for it.

Agency swap (replace the last paragraph):

Whatever the answer, the thing worth keeping: make the top of your client report say what the work was worth, per service and per area, before he has to ask.

CTA: Reply with one word: open, later, or closed.

Sequence 7: Referral request

Who it is for: Anyone currently getting value from BirdsEye. Active accounts past their first real reporting cycle, and also non-customers who received something useful from us, such as a read on their own calls.

Voice: Operator by default. Each email carries an Agency swap.

Entry trigger: A value event, confirmed by a human before send. Any one of: first full month of revenue visible in the account, a positive reply about a specific result, a support interaction that closed well, or a delivered one-off analysis a non-customer thanked us for. Never send this on a date alone. A referral ask sent before the value landed costs more than it earns.

Exit trigger: A referral is made, a decline is given, or 14 days pass after email 2. Suppress from all referral sends for 180 days afterward either way.

Length: 2 emails, 6 days apart. Two is the whole sequence. There is no third referral email, because the third one converts a happy customer into an annoyed one.

Email 7.1, Day 0

Subject: Who else is guessing? Alternate A: One name, if one comes to mind Alternate B: A quick ask, and an easy no

Preview text: No form, no portal, no program. Just one name if you have one.

Body:

A short ask, and a genuinely easy no.

You know what it is like to look at the phone and just know what the day made. Most operators in {{Niche}} do not have that. They are still answering "which ad brought in the best job last month" with a guess and a feeling about which weeks felt busy.

If one person comes to mind who is in that spot, I would like an introduction. Not a list. One name is more useful than ten, because one name means you actually thought about who it would help.

What I will do with it: a fifteen minute conversation, their numbers, and an honest answer about whether this fits. If it does not fit, I tell them so and we are done. Nobody gets sold at on your recommendation.

If nobody comes to mind right now, say so and I will not ask again for a while. That is a completely fine answer and it costs you nothing.

Agency swap (replace the second paragraph):

You know what it is like to have the Friday report already built. Most agency owners do not. They are still rebuilding a spreadsheet the morning the client asks, and defending a volume number that was never the point.

CTA: Reply with one name and how you know them, and I will take it from there.

Email 7.2, Day 6

Subject: Something worth forwarding instead Alternate A: No name needed, just forward the idea Alternate B: Lower effort version of the same ask

Preview text: One idea. It travels on its own.

Body:

Following up on the introduction I asked about, with a lower-effort version.

If naming somebody feels like putting your name on the line, skip it. Forward this instead, to anyone or nobody.

A guy running a business gets about four seconds between jobs. Gloves off, phone out, thumb. In those four seconds he should be able to see what the business made today and what the last call was worth, and almost nobody can. Not because the data does not exist, but because it is sitting in three places and none of them put a dollar on it.

That idea does the work on its own. Anyone running paid lead flow reads it and immediately wants to know their own number, which is exactly the conversation worth having.

Everything is at https://birdseyeroi.com if they want to look before talking to anyone.

And if you would rather not forward anything at all, that is fine too. This is the last note about it either way.

Agency swap (replace the third paragraph):

Friday afternoon, the text comes in: how are the leads doing. The work was good. Proving it takes two hours of rebuilding the same spreadsheet, and by the time it is ready the client has already decided how he feels. The proof should be sitting there before the text arrives, per service and per area, ready to send.

CTA: Forward this to one person who runs paid lead flow, or reply "no thanks" and I will drop it.

Sequence 8: Partner and affiliate outreach

Who it is for: People positioned to refer real volume, not one-off names. The four types that qualify:

1. SEO and local marketing agencies serving home services, who already owe a client a monthly answer they cannot fully produce
2. GoHighLevel, CRM, and marketing-automation consultants who sit inside the client's stack and get asked about call data constantly
3. Pay-per-call operators and lead brokers with provider diversity
4. Coaches, mastermind operators, and community owners whose audience is local service businesses running paid lead flow

Voice: Agency-native throughout. Peer to peer. Nothing in this sequence explains what call tracking is. No Agency swap is needed because there is no operator version of this sequence.

Entry trigger: Manually qualified by a human as fitting one of the four types above, with a real reason recorded for why this person sees volume. Nobody enters this sequence off a scraped list.

Exit trigger: A reply of any kind, a booked call, or completion of email 3. Any reply moves the conversation to a human immediately.

Length: 3 emails over 10 days.

Terms handling, non-negotiable: BirdsEye runs on revenue share and profit share. Partner economics are part of that same conversation and are discussed live, on a call, never in an email. Not a range, not a hint, not an example. Any email in this sequence that acquires a number before Mike approves one is broken and must be pulled.

Email 8.1, Day 0

Subject: The Friday report your clients are actually grading you on Alternate A: A partnership note, not a pitch Alternate B: You own the relationship. This is the missing half.

Preview text: You already have the client. This is the proof he wants.

Body:

This one is about a partnership, so I will be direct about what it is.

Your clients grade you on a report. You can show them rankings, traffic, spend, and calls. What almost nobody can show them is what the calls were worth, split per service and per area, on one page they read in ten seconds without you narrating it.

That is what BirdsEye produces. It reads whatever mix of Twilio, SignalWire, CallFire, and CallRail your accounts sit on, puts a dollar on each call, and lays it out the way the client thinks about his own business. Junk drops out before the totals, so the number holds up when he checks it against his booked work.

I am looking for a small number of partners who already sit inside that client relationship, because you can put this in front of a client in a week and I would spend six months earning the same introduction cold.

How the commercial side works is a short conversation, not an email paragraph, and I would rather have it live than send you a document you have to interpret.

CTA: Reply "partner" and I will send two times this week for a fifteen minute call.

Email 8.2, Day 4

Subject: Nobody churns over a bad month Alternate A: They churn when they stop being able to see it worked Alternate B: Where agency retention actually breaks

Preview text: The retention math, and where the report sits in it.

Body:

Following up with the specific reason this is worth your time.

Clients do not leave over a bad month. Everybody has bad months and everybody knows it. They leave when they quietly stop being able to see that the work landed, and by the time that shows up as a conversation, the decision was already made weeks earlier.

Volume reporting accelerates that, because volume is a number nobody can verify against anything. He cannot check 400 calls against his own books. He can check "the roof line produced this much on the north side," and once he can check it, he starts trusting the whole document.

A partner who hands a client a per service and per area revenue view is in a different business than a partner handing over a call count. That difference shows up in retention, which is where agency economics actually live.

It also makes the report something you are proud to send rather than something you spend a call defending.

CTA: Reply "show me" and I will walk through the report view against one of your client situations on a call.

Email 8.3, Day 10

Subject: Closing the partner loop Alternate A: Last note on the partnership Alternate B: Fit or no fit, both are useful

Preview text: A no here is genuinely useful. It tells me who to talk to.

Body:

Last note from me on this.

I have sent two notes about partnering and have not heard back. That usually means the fit is not there, the timing is not there, or this is not the quarter for a new vendor conversation. All three are fine and none of them require an explanation.

I am closing the loop so I stop landing in your inbox.

If it becomes relevant later, the shape of it is simple. You already own the client relationship and the reporting obligation. BirdsEye owns the layer that puts a dollar on the call and turns it into a page you can send. How that works commercially is a fifteen minute conversation whenever you want to have it.

Everything is at https://birdseyeroi.com in the meantime.

Thanks for the attention either way.

CTA: Reply "later" with a month and I will check back then. Otherwise this is the last one.

Sequence 9: Onboarding

Who it is for: A signed account. This goes to a real human who said yes, so the tone is warmer than cold outreach. It still cannot rely on a first name unless one was captured on the call, so every email below reads correctly with nothing but the business name.

Voice: Operator by default. Each email carries an Agency swap.

Entry trigger: Signature logged and the account moved to stage 7, Won. The handoff to delivery has happened.

Exit trigger: First real use, defined concretely as: the account has logged in, connected at least one provider, and seen a dollar figure produced by their own revenue rules. That is the activation event. Once it fires, the account leaves onboarding and moves to the regular account cadence. If day 10 arrives without activation, the sequence stops and a human calls. An unactivated account is a churn risk, not an email problem.

Length: 4 emails over 10 days.

Terms handling: the arrangement was agreed on a call and stays there. These emails reference the agreement without restating any part of it.

Email 9.1, Day 0, immediately after signature

Subject: You are in. Here is the first 20 minutes. Alternate A: Your account is live, start here Alternate B: First login, and exactly what to do in it

Preview text: Three steps, about 20 minutes, and the number is on your phone.

Body:

Welcome aboard. {{Business Name}} is set up and the account is live.

Rather than a tour, here is the shortest path from login to a number you can actually use. Three steps, about twenty minutes total.

1. Connect your providers. BirdsEye reads Twilio, SignalWire, CallFire, and CallRail. Connect whichever ones you use. Nothing on your side moves. Your tracking numbers and your forwarding stay exactly as they are.
2. Confirm your service names. This is the step people skip and then wonder why the money view looks thin. A dollar figure has to attach to a real service name, not to whatever four ways a caller happened to describe the same job.
3. Set your first revenue rule. What is a booked roof worth. What is a drain job worth. One rule on one service line is enough to start. You are not modeling the whole business today.

After step 3 the screen stops being a list and starts being money.

Anything unclear in those three steps is on me, not on you. Ask and I will answer the same day.

Agency swap (replace the line after step 3):

After step 3 the report has something in it worth sending. Start with one account and one service line, then widen once you can see the shape of it.

CTA: Log in and finish step 1: https://birdseyeroi.com

Email 9.2, Day 1

Subject: The step everyone skips Alternate A: This is the setting that makes the number real Alternate B: Your revenue rules, and why they come first

Preview text: A provider says the call happened. Rules say what it was worth.

Body:

Quick follow-up on the setup, because one step decides whether the rest of this is useful.

Revenue rules are what put the dollar on the call. You set what a booked roof is worth, what a drain job is worth, what a service call is worth. Per service, per niche, as rough or as exact as you want to be.

That is the whole reason this exists. A phone provider can tell you the call happened. It has no idea what the call was worth, and a call that nobody priced is just a row.

You do not have to model the entire business to get value out of it. Start with your two biggest service lines. Set a rule for each. Look at what the last 30 days says back. Refine once you can see the shape of it.

The platform normalizes the messy service text into real, consistent service names first, so the rule you set today still matches next month instead of quietly splitting your best service line across four spellings.

Agency swap (replace the fourth paragraph):

Start with one account and its two biggest service lines. Set a rule for each. Look at what last month says back, then widen. The first client report is more persuasive than the tenth one, so get one right before you scale it across the book.

CTA: Set one revenue rule on your biggest service line today, and reply with the service name if you want me to check it with you.

Email 9.3, Day 4

Subject: Ask it a question instead of building a report Alternate A: Skip the report, just ask Alternate B: The fastest thing in the product

Preview text: A sentence, not a saved view.

Body:

Checking in four days in, with the part people find last and should find first.

Nobody wants a fifth dashboard. So there is Hawkeye, a chat layer over your own calls. You type the question the way you would say it out loud and it answers from the call log. No report to build, no filter combination to guess at, no training session.

Try these two first.

Which service line made the most last month.

Which callers wanted work done urgently and never heard back from anybody.

That second one is usually where the money is hiding, because it is a list of people who already called you once, wanted to give you work, and got nothing. Most of them are still fixable this week.

Underneath it, every call gets read and the important parts get pulled out as real fields: what they wanted, how urgent it was, how the call ended, whether anybody followed up. That is what makes a plain question answerable instead of leaving you with a wall of transcript.

Agency swap (replace the two example questions):

Which service line made this client the most last month.

Which of his callers wanted work urgently and never got called back. That second list is a conversation you get to have with him rather than one he has about you.

CTA: Open Hawkeye and ask it one question about your own calls: https://birdseyeroi.com

Email 9.4, Day 10

Subject: Ten days in. What does the number say? Alternate A: Your first real read Alternate B: Time for the honest check-in

Preview text: Not a check-in about software. A check-in about your number.

Body:

Ten days in with {{Business Name}}, so this is the check-in that matters.

Not "how are you finding the software." The real question. What is the number telling you, and does it match what you expected before you could see it?

Three things worth looking at now that there is enough there to look at.

The end of day view. If you cannot read it in four seconds, tell me and we fix the layout, because that is the entire point.

The service level rows, not the totals. The gap between service lines inside one trade is usually wider than anyone guesses, and the total hides it.

The follow-up gaps. Urgent, and nobody called back. That list is money that already called you once.

If any of those three look wrong rather than surprising, tell me. Wrong means we fix something in the setup. Surprising means it is doing its job, and that part is worth a conversation.

Given how our arrangement works, your number and mine point the same direction. That is the entire reason it is structured the way we discussed.

Agency swap (replace the first of the three items):

The report itself. Open it the way your client will and read it cold. If it needs you to explain it, tell me and we fix the layout, because a report that needs a narrator is not finished.

CTA: Reply with what the number is saying and I will tell you straight whether it looks configured correctly.

Sequence 10: Proof drip

Who it is for: Long-horizon contacts. Cold prospects who did not convert but did not say no, prospects on the 90 day re-approach list, closed-lost records with a timing reason, and anyone who asked to be checked back in with later.

Voice: Operator by default. Each email carries an Agency swap.

What "proof" means in this sequence, since it changed. The earlier version of this sequence drip-fed platform statistics. That was the tool talking about itself. Now each email delivers one idea the reader can act on with any tool, including none. The proof is that the thinking is useful before any money changes hands.

Entry trigger: Any of: day 21 of the cold cadence reached with no reply, a "later" reply, a closed-lost with a timing reason rather than a fit reason, or a prospect who explicitly asked for a nudge down the road.

Exit trigger: Any reply, a booked call, or an unsubscribe. Any reply stops the drip and moves the person to a human immediately.

Length: 5 emails over 90 days. Days 0, 14, 35, 60, 90.

The rule that makes this sequence work: emails 1 through 4 contain no ask, no CTA to book, and no product pitch. Each one delivers a single genuinely useful idea and stops. Email 5 is the only one that asks for anything. If a future editor adds a soft pitch to emails 1 through 4, the sequence loses the only thing that earns it a read at day 60.

Email 10.1, Day 0

Subject: Four seconds Alternate A: The exercise nobody can pass on the first try Alternate B: One idea, no pitch

Preview text: Nothing to click, nothing to book.

Body:

No pitch in this one. One idea and an exercise that takes a minute.

You get about four seconds. Gloves off, phone out, thumb, before the next thing starts. That is the real attention span of somebody running a business, and it is the only window most owners actually have to check on their own company.

Here is the exercise. Decide right now what the one number is that you would want on that screen. Not five numbers. One.

Most people cannot answer it on the first try, and that is the finding. If you cannot name the number, no dashboard is going to help, because you will open it, look at nine tiles, feel vaguely informed, and close it.

Name the number first. Then go make something put it in front of you.

That is the whole email. Nothing to click.

Agency swap (replace the second and third paragraphs):

Your client gets about ten seconds with your report before he decides how he feels about the month. Everything after that is him confirming the feeling.

Here is the exercise. Decide what the one line at the top of that report should say. Not the whole page. One line, and it should be a number he can check against his own books.

CTA: None. This email deliberately has no call to action.

Email 10.2, Day 14

Subject: A call count is not money Alternate A: The unit is wrong Alternate B: Second note, still no pitch

Preview text: An exercise you can run tonight with a spreadsheet.

Body:

Second note, still no pitch. Another one that is useful whether or not you ever talk to me.

Every call report you have ever been handed is denominated in calls. That is the provider's unit, not yours. You do not deposit calls.

The exercise. Pull last month. Mark the calls that turned into actual work. Put what each one was worth next to it. Add the column.

Now compare that total to the call count you were reporting on. Those two numbers have almost nothing to do with each other, and only one of them is the business.

Almost nobody does this, because it takes an afternoon by hand. That is exactly why the call count survives as the number everybody quotes. It is not the right number. It is the easy one.

Do it once by hand and you will never look at a call count the same way again, regardless of what software you end up using.

Agency swap (replace the fourth paragraph):

Now compare that total to the volume number on the last report you sent. Then ask which of the two your client could actually verify against his own books. Only one of them survives contact with his bookkeeping, and it is not the big one.

CTA: None. Nothing to book here.

Email 10.3, Day 35

Subject: Six minutes is not a number you can spend Alternate A: Two four-minute calls Alternate B: Why duration tells you nothing

Preview text: Third note, no ask attached.

Body:

Third note, no ask. This one is about a habit that costs people real money.

Two calls come in. Both last four minutes.

One is a homeowner with a burst pipe who books same day. One is somebody price shopping for a job next spring who will call five other companies this afternoon.

Your log treats them identically. Both are a row with a duration on it. Duration is the one thing about a call that has no relationship at all to whether it was worth anything, and it is the field every system puts front and center.

The point holds regardless of tooling. If the most visible fact about a call is how long it lasted, the system is showing you the least useful thing it knows.

Worth doing on your own: go look at the five longest calls from last month, and the five shortest. See which group actually produced work. The answer is usually not what the sort order implies.

Agency swap (replace the last paragraph):

Worth doing on your own: take the account you are least sure about and sort last month's calls by duration. Then mark which ones produced work. If the sort tells you nothing, that is the answer, and it is also the reason volume reporting keeps losing you renewal conversations.

CTA: None.

Email 10.4, Day 60

Subject: The number should come to you Alternate A: Pull versus push Alternate B: Fourth note, still nothing to click

Preview text: Why the login you never open was never going to work.

Body:

Fourth note, still nothing to click. This one is the least obvious of the four and possibly the most useful.

Every reporting tool ever sold to a busy operator has the same design flaw. It assumes you will go to it.

You will not. You have logins right now you have not opened since the day somebody set them up, and it is not laziness. Going to look is an act of discipline you have to spend on a day that already has crews, trucks, and a customer who is unhappy about something.

Anything that requires you to remember to check it will eventually be checked by nobody.

So the test for any tool you evaluate from here on is simple. Does the number come to me, at the end of the day and the end of the week, without me asking? If the answer is no, it does not matter how good the screens are. You are going to stop opening it in about three weeks and the whole thing will have been a cost with no benefit.

That test is free and it disqualifies most of the category.

Agency swap (replace the third and fourth paragraphs):

Neither will your client. He has a login to a dashboard you set up for him and he has opened it twice, both times because you asked him to on a call.

Anything that requires him to go look will eventually be looked at by nobody, and then the value of your work becomes invisible to the person paying for it.

CTA: None. Last one without an ask.

Email 10.5, Day 90

Subject: Four notes, no pitch. Here is the one ask. Alternate A: Now the ask Alternate B: Your own number instead of my ideas

Preview text: Everything so far was thinking. This one is about your numbers.

Body:

Four notes, no ask in any of them. This is the one with the ask, and then I stop.

Here is what I have sent, condensed.

Name the one number you would want in four seconds, or no dashboard will help. Count what the calls were worth, not how many there were. Duration is the least useful fact about a call and the most visible one. If the number does not come to you, you will stop looking at it.

Every one of those is free, works with any tool, and is worth doing whether or not we ever speak. That is also their limit. They can tell you the shape of the problem. They cannot tell you the size of yours.

So the ask is the only one worth making. Let me put a dollar on your own calls and show you your figures instead of my ideas. What last month actually made, split by service. Which callers wanted work and never got called back. If it comes back clean, you have lost twenty minutes and gained a benchmark, and I will say so plainly rather than manufacture a problem to sell against.

Everything is at https://birdseyeroi.com.

Agency swap (replace the fourth paragraph):

So the ask is the only one worth making. Give me one month from one account and I will send back the report you would have handed that client on a Friday, per service and per area, with dollars on every line. Then you are judging the actual deliverable instead of my opinions about reporting.

CTA: Reply "my numbers" and I will send two times this week.

Sender checklist before any of this goes out

1. Rewrite {{Business Name}} and {{Niche}} into whatever syntax the sending platform expects, and map them to the Business Name and Niche columns exactly. Never map anything to First Name, it is empty on all 300 rows.
2. Confirm the correct track is selected. Sequence 8 is agency only. Sequences 6, 7, 9, and 10 ship operator by default, with the Agency swap applied when the contact is an agency owner. Never a mixed body.
3. Confirm no subject line, preview line, or opening line contains a spam share, a total call count, or a tracked revenue total.
4. Confirm the retired category line appears nowhere in the send.
5. Confirm no email contains a percentage, split, tier, or price. Terms are a call, always.
6. Confirm any product figure that does appear is on FACTS.md, and any dollar figure in creative sits inside a product frame with no business attached.
7. Confirm the reply-stops-the-sequence rule is wired in the sending tool for all five sequences. Automation never talks over a live human.
8. Sequence 7 requires a human to confirm the value event before send. It is not date-triggered.
9. Sequence 10 emails 1 through 4 must ship with no call to action. If the sending platform appends a default footer CTA, disable it for this sequence.