Phantom Cloud / personas
Theo, your BDR.
Researches every prospect. Personalizes every email. Sends only what fits.
Day one
Theo's first hour.
Asks for 5 ICP names plus a one-liner about what you sell.
Theo will not write blind.
Reads your README plus last 10 commits to your primary repo.
Calibrates the value-prop in your own words.
Researches each prospect (LinkedIn, recent posts, public engineering blog).
One personalized hook per email.
Drafts up to 5 cold emails.
Each one cites a specific trigger.
Sends only when you green-light each one.
Send / Edit / Skip each.
Connected to
Theo's toolbelt.
Slack
ConnectedGitHub
Optional, for value-prop calibrationTheo needs Slack so you can hand him ICP names. GitHub on your own repo lets him calibrate your value-prop in your words.
In Slack
What Theo's first DM looks like.
Slack DM
Theo
Theo here.
Theo
Before I write anything, I need 5 ICP names + a one-liner about what you sell. Reply with the names and the line and I will be back in 30 seconds with 5 emails ready to review.
Theo (after you reply)
Got it, "we sell webhook reliability for payments-engineering teams." I read your README and last 10 commits to confirm. I researched the 5 names you sent.
Theo
3 of them have a public trigger from this week (engineering post, conference talk, fundraise). 2 do not, so I wrote shorter messages for those. Drafts ready. Send each / Edit each / Skip each.
Draft
Cold to warm trigger (engineering post)
- To
- Sam Patel, VP Eng at Filament
- Subject
- Webhook reliability for Filament's payments rewrite
Hi Sam, Read your engineering blog post yesterday about the Filament payments rewrite. The reliability section was the part that stayed with me. Moving from synchronous to async webhook delivery is exactly the cliff most payments teams fall off. We built Phantom to sit on top of that path. It watches webhook health, jitters retries on 503s, and DMs the on-call human only when a queue is genuinely stuck instead of pinging on every 502. 20 minutes next Tuesday or Thursday for a walkthrough? - Cheema
Draft
Cold to fresh ICP, no public trigger
- To
- Dana Reyes, CTO at Loomwave
- Subject
- Quick on Loomwave's payments backbone
Hi Dana, Loomwave came up in a payments-engineering conversation this week and I wanted to introduce myself. We work with teams running webhook-heavy infrastructures and the recurring problem we solve is: the on-call has to read the queue every morning to know what is broken. Phantom does that read. It DMs you only when something needs you. Worth a 15-minute walkthrough? Happy to send a 2-minute video instead if that is faster. - Cheema
Draft
Cold with a conference-talk trigger
- To
- Avery Chen, Director of Eng at Mantle
- Subject
- Re: your QCon talk, the queue-depth section
Hi Avery, Caught your QCon talk on the Mantle payments backbone last week. The queue-depth slide (the one where you said "we built our own dead-letter dashboard") is where the conversations get interesting for us. We built Phantom on the same intuition. Agents should watch the queue and only ping a human when the queue is genuinely stuck. Curious if the dashboard you built is something you would replace or augment. Either way, 15 minutes to compare notes? - Cheema
What slips past you that Theo catches.
The receipts.
- The lead you would never have written to because you didn't have time.
- The trigger sitting in someone's engineering blog from yesterday that fits your ICP perfectly.
- The cold email you would have sent generic instead of personalized (and gotten ignored).
- The follow-up you forgot existed.
- The 5 emails you would have spent 90 minutes on.
Hire Theo in 30 seconds.
Bring your provider key. Connect Slack. Pick Theo. He is in your DMs by the time you finish naming him.
Theo needs you to give him the ICP names. Slack DM is the channel. GitHub on your own repo lets him calibrate your value-prop in your words.