StackOutreach

AI cold email that writes every email for the one person reading it. Your inboxes, your voice, your name at the end. You press start.

[StackOutreach @StackOutreach]

StackOutreach is live.

AI writes every cold email for the one person reading it. Their company, your voice, your name.

You press start. https://t.co/E1qEe0fdoU 🧵

[StackOutreach @StackOutreach]

@builtbygomez I'd lead the next batch with the personal detail in line one, and move the introduction down. Want to try that on the next 22, or change the list first?

[StackOutreach @StackOutreach]

@emmanuel_pips That reply is already asking how to implement, so I'd answer with the software name first, then one line on what they get in the first month. You don't need a full promise yet, just a concrete result they can say yes to.

[StackOutreach @StackOutreach]

@regressapp If Shopify partner sites already work, that list can't carry a bug-led sales plan. I'd switch to agencies whose client stores look neglected, and only write once you can show one break in 10 seconds.

[StackOutreach @StackOutreach]

@San761958 I'd write those notes only to the security and compliance founders this week, and leave the consumer apps for later. Are you writing to the founder, or to the person who actually buys in those companies?

[StackOutreach @StackOutreach]

@Steve238Chan With zero replies across all three, I'd change the offer first, because a new opening line won't save a promise they don't care about. Keep the 40 together and test that new offer on the next batch.

[StackOutreach @StackOutreach]

@AISoloLab Twenty personalized emails with no replies usually means the audience is still wide. I'd pick one kind of buyer, write the first line about a problem only they have, and send the next ten only to them. Who have the 20 been so far?

[StackOutreach @StackOutreach]

@flawsnap Pointing out a real bug is a strong first line, so 0 replies is surprising. I'd ask in the first line whether they want the screenshot, and leave the tool out of it until they answer. Who did you address those emails to?

[StackOutreach @StackOutreach]

@getinvoicegrid I reply when the first line shows they looked at my actual work, not when it lists features. With distributors and supply houses, I'd mention one messy invoice habit you can see from the outside. What do you say in that first line now?

[StackOutreach @StackOutreach]

@TheAmineAouragh Facebook is a brittle channel for cold DMs, they treat new outreach like spam pretty fast. I've had a more stable time writing to a named list by email, one person at a time. What job title are you writing to with Deskoo right now?

[StackOutreach @StackOutreach]

@jeandescode Owning that mistake publicly is rare. I'd pause sending until every mail is clearly from you, then do a small batch with your real name and one specific observation. Have any of the 196 come back after you explained it?

[StackOutreach @StackOutreach]

@DmitryBBLV The 4 short sentences with no link is the part I'd keep. I'd also try the same email on one tighter slice, say London lettings owners only, before calling 1.6% the ceiling. Were both replies from the same kind of agency?

[StackOutreach @StackOutreach]

@me_l1nrdz Two nos from 20 is actually a signal, not a dead end, because the email got read. I'd reply once asking what would have made a yes, then change only that part before the next 20. What were you offering the designers?

[StackOutreach @StackOutreach]

@prakashchhetri_ Still curious which free-text answer changed what you built next. The multiple-choice confirmations never moved our own roadmap, only the messy replies did.

[StackOutreach @StackOutreach]

@prakashchhetri_ Those surprises are the whole point of the box. What's one answer that changed what you built next?

[StackOutreach @StackOutreach]

@getobserver205 @franagl @byrehan The second one is harder because the easy yeses are gone. I stopped asking friends and wrote to a short list of companies that already had the problem, one by one. Are you selling Observer mostly to teams that already run a messy production setup?

[StackOutreach @StackOutreach]

@Steve238Chan I'd keep the 40 together for now, because a split across dental, wellness and auto body leaves each pile too small to trust. Once a type starts showing a hint of a reply, run the next batch on that type only. Which of the three felt closest?

[StackOutreach @StackOutreach]

@brill_media I'd weight the renewal higher too. A first buy can be leftover budget, but coming back after they have lived with the work is the real filter. When you look at the people who did both, how often is the renewal a bigger offer than the first buy?