← All posts · 2026-10-15

A founder booked a call 6 minutes after this email. Here's why.

I run Dependables. We build things for consumer brands, and I hire commission-only account executives to sell them. Most weeks I also do my own outreach. This post is about one kind of email I send, and what happened when founders opened it.

One startup founder replied 6 minutes after my first email. He wrote: "Great to meet you! I booked a time to connect tomorrow." I didn't send a calendar link and ask him to pick a slot. He went and booked it himself.

Before we go further, two things to be clear about. These replies came from my own outreach to founders. They are not student results, and nobody in the course sent them. And plenty of my emails get no reply at all. I'm not going to give you a reply rate, because I'd be guessing, and a made-up number would mislead you.

The email

Here is the shape of the email, using a real build. We picked WowCube, a company that makes a modular puzzle console. Nobody asked us to, and we built them a new site anyway. It's live at wowcube.meetthedependables.com.

The email that goes with a build like this is short:

Subject: I built WowCube a new site

I liked WowCube enough that we just went ahead and built you one: wowcube.meetthedependables.com

It's live. There's a growth plan, a week-one plan and 20+ ad concepts on there as well. Nothing behind a form.

If it's sharper than what you've got now, I'd take 20 minutes to walk you through it.

That's most of it. A link, a line about what's there, and a small ask at the end.

To be precise: the 6-minute reply came from a different founder, to an email built the same way. I'm not claiming WowCube replied. The WowCube build is here because it's public and you can open it.

What the usual email looks like

Compare it with the one most founders get every day. Something like:

Subject: Quick question about your growth

We help brands like yours build high-converting pages. Do you have 15 minutes this week for a quick intro call?

No link. Nothing to look at. Every line could be sent to any company by anyone. The founder has to give up time before they know if the sender is any good. So they do the easy thing and archive it.

Why the first one gets answered

Three reasons, and none of them is clever wording.

It's about them. The first line is about the founder's own company. People open things about their own business.

They can check it. The founder doesn't have to trust me. They click, look for thirty seconds and decide if we're any good. Every claim in the usual email has to be taken on faith. The link in this email can be checked.

The work is already done. Saying yes to a call is a risk of wasted time. When the work already exists, the call has an obvious topic. The founder knows what they're getting before they agree to anything.

The other replies I've had follow the same pattern:

• A consumer-food co-founder wrote "Love the initiative." 54 minutes after the first email, then asked if I wanted to hop on a call that day.
• A startup co-founder wrote "Sweet, let me take a look." 11 minutes after an email that included ads we'd made for them.
• A founder wrote "Site looks amazing — let's chat" a day after the follow-up.

Notice that last one. It came after a follow-up. Some people don't answer the first email even when they like the work. They're busy. A follow-up that adds something gives them a second chance.

The same move, aimed at a hiring manager

When you apply for a sales job, you're sending a cold email. The hiring manager is the founder. You're the stranger asking for their time.

Most applications look like the usual email. "I'm passionate about sales and a hard worker. I'd love to hop on a call to discuss the role." Every word is a claim, and there's nothing to check.

Here is a work-first version for an SDR role:

Subject: Built this for your pipeline

Hi Jordan,

I'm applying for the SDR role. Instead of telling you I can prospect, I picked one company that looks like your customers and did the work.

Here's the account plan, the first email I'd send them, and a 2-minute recording of how I'd open the call: [link]

If it's close to how your team works, I'd like to talk about the role.

Riley

Jordan and Riley are made up. The structure is the one I use.

I read applications from the hiring side. When one like this lands, I react the way that food co-founder did. Initiative is a big part of the job. A rep who builds something useful before anyone asks is showing me what they'll do with my prospects.

How to build yours

You don't need to build a website. Keep it small enough to finish this week.

• Pick one company. One you'd actually like to work for.
• Make one finished thing. A one-page account plan, three cold emails for their product, a 60-second screen recording walking through their sign-up flow, or a short recorded mock call.
• Make it specific. Use their product, their customers and their website. Generic work is just a longer version of the usual email.
• Label it honestly. Call mock work mock work. Don't use their logo in a way that suggests you already work together. "Here's what I'd send" is honest.
• Write five lines. What you made, the link, one line on why, and a small ask.
• Follow up once with something new. A second idea, a second email, a note on something they just launched.

Then expect silence from some of them. That's normal. Work-first gives a reader a real reason to answer. It doesn't promise an answer, an interview or a job. What it does is get you read by people who would otherwise archive you in two seconds.

Try it

Write your first one with the free Work-First Email tool. If you want the full method, from your LinkedIn profile to your first offer, start here.