Logo

Outreach Only Works If You Actually Do It

For a long time, I told myself I was too busy to do outreach.

There was always something more pressing. A feature to finish. A bug to fix. A product decision to think through. The list had no bottom.

But the real reason I avoided it?

I didn’t want to feel the silence.

The Lie I Was Telling Myself

I convinced myself that if I built something good enough, people would find it.

That the work would speak for itself.

That outreach was something aggressive salespeople did — not builders trying to create something real.

That belief kept me comfortable and broke at the same time.

Because here’s the thing nobody tells you when you’re deep in a product: building doesn’t move the needle. Conversations do.

A perfectly integrated feature means nothing if no one’s using it.

What Changed

I didn’t have a breakthrough moment. No single conversation that flipped a switch.

What changed was simpler and harder than that: I started showing up every day.

I set a floor for myself. Two to three contacts a day, minimum. Not replies — initiated contacts. DMs, emails, follow-ups. Something that required me to put myself in front of another person.

The goal is 20 a day. I’m not always hitting it. But the floor? That I protect.

And what I’ve noticed is this: the days I hit two or three, I feel like I did something real. The days I skip it, I feel like I hid.

Follow-Ups Are Where It Actually Happens

Early on, I thought outreach was about the first message.

It’s not.

The first message is just permission to have a conversation. Most of the time, nothing comes from it immediately. Someone reads it, means to reply, gets distracted. Life happens.

The follow-up is where you separate yourself from everyone else who messaged them once and disappeared.

I used to skip follow-ups because they felt pushy. Now I see them differently. A follow-up isn’t pressure — it’s showing that you actually meant the first message.

The Urge to Build Instead

It’s still there. I’m not going to pretend it isn’t.

There’s always a product reason to disappear into the code for a day. Or a week. An integration that needs work. A flow that could be smoother. A feature that would make the pitch easier.

But I’ve started to recognise that voice for what it is: an escape from the discomfort of outreach.

Building feels like progress because you can see the output immediately. Outreach feels like chaos because you can’t control when — or whether — anyone responds.

The thing is, I’m learning that the chaos is the point. Learning to sit in the uncertainty, follow up anyway, and keep going is what builds the muscle.

I’m Actually Learning Sales

This might sound obvious, but it took me longer than it should have: there’s a process to this.

Once someone engages, there’s a next step. And a step after that. It’s not just “reply, close.” It’s a conversation with a shape — building context, understanding what they actually need, knowing when to move forward and when to slow down.

I’ve started paying attention to that shape. Reading about it. Thinking about where each conversation is in the process rather than just hoping it goes somewhere.

That shift — from “doing outreach” to “understanding the sales process” — has made me significantly less anxious about it. It’s a skill. It can be learned. Like any other.

What I Know Now

Outreach isn’t glamorous. It doesn’t compound the way code does. You can’t push it to GitHub and feel like you shipped something.

But it’s the only activity I’ve found that reliably creates new opportunities.

Not content. Not SEO experiments. Not a better product.

Conversations.

Two to three a day, every day, and you’d be surprised what starts to accumulate on the other end.

The needle doesn’t move when you’re ready.

It moves when you show up.

Current Focus