BirdsEye ROI, Email and Social Copy Pack

Written against positioning-why-i-built-it.md. That file is the authority on angle and voice, and it outranks anything here.

The earlier version of this pack led with platform internals: the log size, the spam share, and the tracked revenue total. It was replaced because those are facts about the tool's database, not reasons anybody buys. The retired version is kept at copy-emails-social-v1-data-led.md.bak for reference only.

FACTS.md still governs any number that does appear. It is a ceiling, not a brief. Most copy in this pack needs no platform figure at all.

What this pack sells: a busy owner looks at his phone for four seconds between jobs and knows what the business made. For the agency, a per service and per area report he is proud to send on a Friday.

Banned from every subject line, opening line, and hook 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, do not use in any ad, email, or post: "Most call tracking tells you the phone rang. BirdsEye tells you which ring paid." It argues with a category instead of talking to a person. Deck only.

Product URL used throughout: https://birdseyeroi.com

Voice rules applied: money words over metric words, short sentences, no em dashes, no emojis, no hype adjectives, full https:// URLs, one CTA per email.

Dollar figures shown anywhere in this pack are product illustrations, the way a bank ad shows a balance. Never a named client, testimonial, logo, case study, or claimed result. We have none.

Section 1: Cold outreach email sequence, 5 emails

Two audiences, two voices, one cadence. Every email below carries an Operator track and an Agency track. They are not the same email with a swapped subject line, because the two buyers do not have the same problem.

The operator wants to know if today paid. The agency already knows the calls came in and needs to prove they were worth paying for. Send one track or the other. Never mix them into one send.

Email 1, Day 0

Subject (operator): What was your last call worth? Alternate A: Four seconds, and you know if today paid Alternate B: A question about the calls coming into {{Business Name}}

Subject (agency): The report you have to defend on Friday Alternate A: Proving the leads were worth paying for Alternate B: You are not short on calls

Preview text (operator): Not how many calls. What they were worth. Preview text (agency): Per service, per area, ready to send.

Body, operator track (96 words):

This is for whoever watches the money at {{Business Name}}.

Somebody called you an hour ago. Do you know what that call was worth?

Most systems will tell you it lasted six minutes. Six minutes is not a number you can spend.

I built BirdsEye so an owner can look at his phone for four seconds between jobs and know what the business made. One number on the screen. The last call with a dollar next to it. Nothing to dig through.

Worth showing you what your last 90 days would look like that way?

CTA: Reply "show me" and I will send the one screen it puts on your phone.

Body, agency track (94 words):

For whoever builds the client reporting at {{Business Name}}.

You are not short on calls. You are short on proof.

Friday comes, the client asks how it is going, and the honest answer takes two hours in a spreadsheet you rebuild every month.

BirdsEye turns the calls you already produce into a report with dollars on it, broken out per service and per area. Something you send, not something you build. On brand, and good enough to go out without editing.

Want to see the format before you give me any time?

CTA: Reply "report" and I will send the format we would run for one of your accounts.

Email 2, Day 3

Subject (operator): It should already be on the screen Alternate A: You should not have to go looking for it Alternate B: End of the day, without you asking

Subject (agency): The Friday text Alternate A: "How are the leads doing?" Alternate B: Stop defending volume

Preview text (operator): A chart at the end of the day that tells you it worked. Preview text (agency): The answer that takes two hours, in one send.

Body, operator track (88 words):

The actual reason I reached out.

Nobody wants another dashboard. You already have logins you never open.

So this is not a place you go look. It is a number that shows up. End of the day and end of the week, a chart you do not have to interpret. Up or down, and what the work was worth.

If you have to learn it, I built it wrong.

That is the test I hold it to, and it is the only feature that matters to somebody running crews all day.

CTA: Reply "day" and I will send you what the end of day view looks like.

Body, agency track (105 words):

Every agency owner knows the text. Friday afternoon, and it says "how are the leads doing?"

The work is real. You did it. The problem is proving it before Monday.

So the report is the product. Per service and per area, each line carrying a dollar figure. Roofing did this. HVAC did that. The north side beat the south side. Here is what changed since last month.

Your client does not want a call log. He wants to see he is winning, on one screen, without you narrating it.

You stop defending volume and start showing what it was worth.

CTA: Reply with one account name and I will send the report shape for it.

Email 3, Day 7

Subject (operator): You do not have to change your phone numbers Alternate A: Your numbers stay on the trucks Alternate B: Nothing changes on your side

Subject (agency): You keep your stack. It gets a dollar column. Alternate A: Nothing gets ripped out Alternate B: Whatever your accounts are sitting on already

Preview text (operator): Same numbers, same forwarding, different screen. Preview text (agency): No migration. Just the column nobody has.

Body, operator track (108 words):

Please pass this to whoever handles the phones at {{Business Name}}.

The first thing people ask is whether they have to reprint the trucks, the yard signs, and the door hangers. No.

BirdsEye reads the tracking numbers you already have across Twilio, SignalWire, CallFire, and CallRail. Your numbers stay. Your forwarding stays.

What changes is what you see. Every call carries a dollar figure and a plain answer to what the person actually wanted.

And the junk drops out before it reaches the number, so what is left on the screen is real work, not robocalls and people selling you SEO.

CTA: Give me 20 minutes and I will put your own calls on screen with dollars on them: https://birdseyeroi.com

Body, agency track (112 words):

The practical version for {{Business Name}}.

You do not rip anything out. Whatever mix of Twilio, SignalWire, CallFire, and CallRail your accounts sit on, BirdsEye reads all of it and adds the one column nobody else has: what the call was worth.

Then it splits that by service and by area, which is how your client thinks about his own business anyway. He does not think in channels. He thinks about the fact that the roof jobs came from the north side and the drain jobs did not.

Junk calls drop out before the totals, so the number you send survives the client checking it against his own booked work.

CTA: Give me 20 minutes and I will build the view against one live account: https://birdseyeroi.com

Email 4, Day 12

Subject (operator): Why I built this Alternate A: I was tired of guessing Alternate B: The short version of the whole thing

Subject (agency): Why I built this, and why it looks like a client report Alternate A: I built the report I was tired of rebuilding Alternate B: The honest version, twelve days in

Preview text (operator): No pitch. Just the reason it exists. Preview text (agency): Including how the commercial side actually works.

Body, operator track:

Twelve days of emails, so here is the honest version.

I built this because I was tired of guessing.

The calls were tracked. They were tracked in four different places. And at the end of the month I still could not tell you which spend produced the jobs. So I put it in one place and made every call carry a dollar.

Now I look once and I know. That is the whole product. The transcribing, the reading, the junk filtering, all of it only exists so that one look is true.

One more thing, so you read the rest of this correctly. This is not a monthly software bill you approve and then have to justify. We work on a revenue share and profit share basis, which only makes sense if the calls are producing money we can both see. What that looks like for {{Business Name}} is a conversation, not a number I am going to invent in an email.

CTA: Book 20 minutes, we will walk your own calls, then talk structure: https://birdseyeroi.com

Body, agency track:

Twelve days in, so here is the honest version.

I built this for myself first. I was running lead flow and I could not prove, on a Friday, that any of it landed. I could prove the phone rang. Nobody pays for the phone ringing.

So I made every call carry a dollar. Then I made the output something I would be proud to send instead of something I had to sit on a call and explain.

The commercial side, plainly. This is not a per-seat license you buy, mark up, and resell. We work on revenue share and profit share, built around what the call data actually surfaces. Your account count, your provider spread, and who owns the client relationship all change the shape of it, which is exactly why it is a call and not a price sheet. Quoting you a structure before I know those things would be a guess, and you would be right to discount a guess.

CTA: Book 20 minutes and we will talk structure against your real account mix: https://birdseyeroi.com

Email 5, Day 18, break-up

Subject (operator): Closing your file Alternate A: Last one from me Alternate B: I will stop here

Subject (agency): Closing the loop on this Alternate A: Fit or no fit, both are useful Alternate B: Last note on this

Preview text (operator): No pitch. Just the close-out. Preview text (agency): One thing worth keeping either way.

Body, operator track:

Last note to {{Business Name}}.

A few emails and no reply, which usually means one of three things. You have this handled, the timing is wrong, or it is not the fire you are fighting this quarter. All three are fine and none of them need an answer.

I am closing your file so I stop landing in your inbox.

If it comes back around, the thing worth keeping is small. Whatever you end up using, make it put a dollar on the call. A call count is not money, and you should not have to dig for the part that is.

Everything is at https://birdseyeroi.com whenever.

CTA: Reply "later" and I will check back in six months. Otherwise this is the last one.

Body, agency track:

Last note to {{Business Name}}.

No reply usually means the fit is not there, the timing is not there, or you already have somebody doing this. All fine, and none of them need explaining.

Closing the loop so I stop crowding your inbox.

One thing worth keeping either way. The report you send is more of your product than the leads are. A client who can see, per service and per area, what your work was worth does not have the "I am not sure this is working" conversation with you in month seven. He has it with somebody else.

https://birdseyeroi.com if it comes up.

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

Section 2: Warm nurture sequence, 3 emails

Trigger: booked a demo, attended, did not close. Entry point is 3 days after the demo.

Written in the operator voice by default, because most demos are operators. Each email carries an Agency swap giving the paragraph that changes when the prospect is an agency owner. Swap the paragraph, keep the rest.

Nurture Email 1, Day 0 (3 days post-demo)

Subject: The one screen from our call Alternate A: The part that actually puts the dollar on the call Alternate B: Picking up where the demo left off

Preview text: Not a recap. The single screen that mattered.

Body:

Thanks for the time on the demo. Rather than a recap of everything, here is the one piece that matters for your situation.

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.

After that, the screen stops being a list and starts being money. The end of day number is just true, and you can look at it for four seconds and be done.

That is the layer a phone provider does not have. A provider can tell you the call happened. It has no idea what the call was worth.

Nothing else changes on your side. Your numbers, your forwarding, and your providers stay where they are.

Agency swap (replace the "end of day number" paragraph):

After that, the report writes itself. Per service and per area, each line carrying a dollar figure, sorted so the client sees which service is carrying his month without you explaining it to him.

CTA: Reply with your two biggest service lines and I will write out what the rules would look like for them.

Nurture Email 2, Day 6

Subject: The objection I should have answered on the call Alternate A: If the hesitation is the commitment, read this one Alternate B: What I did not explain well during the demo

Preview text: The real hesitation, answered straight.

Body:

Thinking back on our call, I do not think I answered the real hesitation, so let me do it now.

It is usually one of two things.

The first is "we already have call tracking." True, and it is also the point. This does not replace Twilio, SignalWire, CallFire, or CallRail. It reads what you already have and adds the part none of them do, which is the dollar on the call. Your numbers stay. There is almost nothing to switch.

The second is that nobody wants another monthly bill to justify when the quarter gets tight. On that one: this is not a subscription. We work on a revenue share and profit share basis, tied to money we can both see. What it looks like for you depends on your volume and your service lines, which is why it belongs on a call and not in an email where I would be guessing at your numbers.

If the hesitation is something else entirely, tell me the real one and I will answer it straight.

Agency swap (replace the first hesitation paragraph):

The first is "we already have call tracking for these accounts." True, and it is the point. This sits on top of whatever each client is already on and adds the column you cannot produce today, which is what the call was worth. No migration, no client conversation about changing numbers.

CTA: Reply with the actual hesitation and I will answer it in one email. No second demo required.

Nurture Email 3, Day 14

Subject: Should I close this out? Alternate A: Where do you want to leave this? Alternate B: Open or closed, either is fine

Preview text: One question, and no follow-up if the answer is no.

Body:

No pitch here, just housekeeping.

You have seen it, so there is nothing left for me to show you. One direct question instead: should I keep this open or close it out?

If it is timing, name the quarter and I will go quiet until then. If it is a no, that is genuinely fine and I will stop.

If it is still a maybe, the fastest way through is not another demo. Send me one month of your calls and I will put a dollar on each one and send it back. You will know in about a minute whether that number is worth having in your pocket.

Agency swap (replace the last paragraph):

If it is still a maybe, the fastest way through is not another demo. Give me one month of calls from a single account and I will send back the report you would have handed that client on a Friday. Then you are judging the actual deliverable instead of a screenshare.

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

LinkedIn is the agency owner. Facebook is the operator. X and Instagram split between them and are labeled per post. The two voices should be audibly different when read back to back.

LinkedIn, 6 posts, agency owner audience

LinkedIn 1

Friday, 4pm. The text comes in. "How are the leads doing?"

You know the answer is good. That is not the problem.

The problem is that proving it takes two hours of pulling numbers out of three places and rebuilding the same spreadsheet you rebuilt last month, and by the time it is ready the client has already decided how he feels.

Nobody churns over a bad month. They churn when they stop being able to see it worked.

So build the proof before the text arrives. Per service, per area, dollars on every line, ready to send.

Field	Column name in the CSV	Populated	Safe to merge
Business name	`Business Name`	300 of 300	Yes
City	`City`	300 of 300	Yes
State	`State`	300 of 300	Yes
Niche	`Niche`	300 of 300	Yes
Email	`Email`	300 of 300	Send field, not body copy
First name	`First Name`	0 of 300	No. Never merge.

BirdsEye ROI, Email and Social Copy Pack

Section 1: Cold outreach email sequence, 5 emails

Email 1, Day 0

Email 2, Day 3

Email 3, Day 7

Email 4, Day 12

Email 5, Day 18, break-up

Section 2: Warm nurture sequence, 3 emails

Nurture Email 1, Day 0 (3 days post-demo)

Nurture Email 2, Day 6

Nurture Email 3, Day 14

Section 3: Social posts, 20 total

LinkedIn, 6 posts, agency owner audience

Facebook, 6 posts, local service owner audience

X / Twitter, 4 posts

Instagram, 4 captions

Section 4: Ten headline variants and ten hook lines

Headlines, for ads, page headers, and section titles

Hook lines, for video openers, ad first frames, and post line one

Merge fields available in batch 1

Pre-send check for this pack