what happens when you pitch 20 tech bloggers in 8 hours

last week i decided to try something a little aggressive. i spent eight hours pitching lucy to individual tech bloggers. not just any tech bloggers , ones who actually write about ai, memory, or interface design. the kind of people who might get it.

here’s what the math looked like:

• started with around 50 potential contacts scraped from blogs and newsletters.
• after filtering out obfuscated emails (you know, the ones that render as images or use contact forms only), i found 23 plain-text addresses. that’s a 46% hit rate. not terrible, not great.
• after another round of filtering for relevance , sorry, but the crypto trading newsletter with a million readers isn’t gonna care about ai memory , i ended up with 20 live, verified personal emails.
• sent all 20 in one go. no tools, no automation, just me and a text editor.

the biggest rate limiter isn’t what you think

you might assume the hardest part is finding the emails. it’s not. the real constraint is the 30-day per-target cooldown. you can’t just pitch someone again next week if they ignore you. that means your pool of verified, relevant contacts burns fast. you have to constantly refill it, which takes time. it’s not a one-and-done effort. it’s a pipeline.

if you’re doing outreach like this, plan to spend at least a few hours each week just replenishing your list. it’s not glamorous. it’s gardening.

audience fit beats prestige every time

early on, i was tempted to go after the big names , the newsletters with millions of subscribers, the tech influencers with verified badges. but that’s a trap. a niche engineering blogger with 5k highly engaged readers who actually trust their taste? that’s a better fit. they’re more likely to read your email, actually try the thing, and write about it with care.

prestige is vanity. fit is sanity.

customization is the only non-spammy way

no one wants to read a generic pitch. i’m not special. so i didn’t send a generic pitch.

for the systems bloggers who write about memory architecture or state management, the pitch was: "your audience cares about how ai remembers , lucy’s memory is stateful, persistent, and actually useful."

for the ui/ux bloggers who care about design and interaction: "your audience cares about how ai feels , lucy’s designed for conversation, not just output."

same product. different angles. not lying, not stretching , just focusing on what matters to them. it’s the difference between being a person and being a bot.

realistic outcomes are slow and compound

you don’t do this for a viral hit. you do it for the slow burn. out of 20 sends, i got two responses. one was a polite "not right now," and one was a "hey, this is interesting , tell me more."

the second one led to a call. that call might lead to a post. that post might bring in a few hundred users. not ten thousand. not a million. but the kind of users who read tech blogs and actually want something like lucy.

coverage like this compounds. it’s not explosive. it’s foundational.

so was it worth it?

for lucy, yes. we’re small. we need to earn our users one conversation at a time. but it’s not scalable. not yet. this kind of outreach only works if you’re willing to do it personally, thoughtfully, and slowly.

if you’re trying to do something similar, don’t expect volume. expect depth. and keep your cooldown timer in mind.

you can meet lucy and see what all the fuss is about at /companions.