Outbound advice assumes someone else does the work. Build a list, warm the domains, run the sequences, handle the replies, written as if these are separate jobs because in most companies they are.
You are one person who also builds the product, answers support and does the invoicing. So the question is not what best practice looks like. It is what fits in five hours a week and still produces conversations.
It does fit. Here is the version that survives contact with your actual calendar.
The target: fifty conversations, not a pipeline
Set the goal properly, because the wrong goal is what makes this fail.
You are not building an outbound engine. At your stage you are trying to have fifty real conversations with people in your market, some of which become customers, most of which teach you something you will put in the product or the positioning.
That reframing changes three decisions:
Volume stops mattering. Fifty conversations over a quarter needs maybe 400–600 well-chosen approaches. Not 10,000.
Learning counts as a result. A conversation that ends in “we solve this with a spreadsheet and it is fine” is a useful outcome. Under a pipeline target it looks like failure.
You can do it by hand. At this volume, manual research beats automation on yield, and you are the best person in the company to write the message.
The five-hour week
Two sessions. Protect them like customer calls, because they are the thing that produces customer calls.
Session one: Monday, 2 hours, list and send
30 minutes: build the list. 40–50 companies for the week. By hand or from a saved search, filtered tightly.
Tight means tight: one industry, one size band, one region, one role. If your list contains two kinds of company, you cannot learn anything from the response rate because you will not know which kind responded.
45 minutes: write the first lines. One sentence per prospect, specific to them. This is the only part of the message that varies and it is where the entire reply rate lives.
Realistically you will do this properly for about 25 of the 50. Do those 25 and send a cleaner, non-personalised version to the rest, then compare the response rates. That comparison is one of the more useful experiments available to you, and almost nobody runs it.
30 minutes: enrol and send. Load into the sequence, check the merge fields do not break, start it.
15 minutes: LinkedIn. Connection requests to the same 50 people. Same list, second channel, almost no extra cost, which is the entire argument for multichannel at your scale.
Session two: Thursday, 1.5 hours, replies and calls
45 minutes: replies. Properly. This is where your advantage over a funded competitor lives: you can answer a question about the product authoritatively and immediately, and they cannot.
30 minutes: a calling block, if your market takes calls. Ten dials to people who opened something. Not cold, warm, a dial to someone who has read two emails converts several times better than a cold one.
15 minutes: the week’s numbers. Three figures: approaches sent, replies, conversations booked. Written down somewhere you will see them next week.
The remaining 1.5 hours: daily reply checks
Fifteen minutes a day, first thing. Nothing else.
That is the system. Five hours, 50 approaches a week, two channels, every reply answered within a day.
What to cut
The list of things you are allowed to skip, which is longer than most advice admits.
Cut: multi-step sequences past three touches. Steps four through eight produce a small fraction of replies and cost you reputation and time. Three touches, then stop.
Cut: A/B testing. You do not have the volume for a meaningful result. At 200 sends a month, a difference between two subject lines is noise. Change one thing at a time and judge it over a month, informally.
Cut: four channels. Email and LinkedIn. Add a third only when the first two are working and you have evidence about which one is doing it.
Cut: dashboards and reporting. Three numbers in a note. Nothing else.
Cut: CRM, for now. Below roughly 50 open conversations, your outreach tool’s own view is enough. A CRM you maintain badly is worse than no CRM.
Cut: dedicated IPs, warmup tools, placement monitoring services. Below a couple of thousand sends a month these solve problems you do not have. Deliverability for non-technical founders covers the minimum that actually matters.
Cut: cold calling, at the start. It is the highest-conversion channel and the most time-expensive per contact. It is a poor fit for a five-hour budget until email has told you which message works.
What not to cut
Four things, and skipping any of them wastes the whole effort.
Warmup. Three to four weeks before real sending. Start it today in the background while you do everything else, this is the one thing that genuinely requires waiting, so start the clock now.
Separate sending domains. Not your main company domain. If cold email damages it, your invoices and support mail suffer.
Verification. Before every send. One bad list undoes two months of reputation, and at your volume you cannot afford to rebuild.
Daily reply checks. A reply answered three days later is usually a reply wasted. Fast answers are your only structural advantage.
The two-hour setup
Once, before any of the above.
- Buy two domains, close variants of your brand, not keyword spam. (20 min)
- Create three mailboxes per domain, six total. That supports around 200–300 sends a day eventually, which is more than you will need. (30 min)
- Check authentication, SPF, DKIM, DMARC. Usually configured by the provider; verify with a free checker anyway. (20 min)
- Start warmup. Then leave it alone for three weeks. (10 min)
- Write the three-touch sequence, leaving the first line as a merge field. (30 min)
Three weeks later you start sending. Use the waiting time to build the first two lists and to have ten conversations with people you already know in the market, which will change the sequence before you ever send it.
The message, at this scale
You have one advantage a company with an SDR team does not: you can write as the founder, and that is a genuinely different email.
Use it directly. “I built this because [specific thing I kept running into]” is a sentence nobody with a sales team can send credibly. It earns replies that a polished sequence does not, including replies that are just advice, which at fifty conversations is exactly what you want.
Three rules:
Short. Under 100 words. You are asking for a reply, not explaining the product.
One specific thing about them. The sentence that proves you chose them. Everything else can be templated.
An easy out. “If this is not relevant, no need to reply” raises response rates and costs nothing. People answer honest messages.
And ask a question that is answerable without a meeting. “Is this how you handle X at the moment?” gets answers from people who would never book a call, and those answers are the point.
When to stop doing it yourself
Three signals that the manual version has done its job.
You know which message works. When one approach reliably outperforms and you can say why, that knowledge is what makes automation safe. Automating before you know it just scales a guess.
Replies take more than 45 minutes twice a week. A good problem, and it means the system is working and the constraint has moved.
You are turning down the list. When you have more well-fitting companies than five hours allows, the bottleneck is capacity rather than knowledge, and more volume is finally the right answer.
At that point the next step is usually campaigns that refill themselves, saved searches and signals topping up the list so Monday’s half-hour disappears, then a second person, then a third channel. In that order.
The short version
Aim for fifty conversations, not a pipeline. That needs 400–600 approaches over a quarter, which fits in five hours a week.
Two sessions: Monday for the list and the sends, Thursday for replies and a short calling block, plus fifteen minutes a day on replies.
Cut long sequences, A/B testing, extra channels, dashboards, a CRM and most deliverability tooling. Do not cut warmup, separate domains, verification or daily reply checks.
Write as the founder, keep it under 100 words, name one specific thing about them, and ask a question they can answer without booking anything.
Automate when you know which message works, not before.
Next: the founder’s first 90 days of outbound, or deliverability for non-technical founders.
Frequently asked questions
How much time does cold outreach take for a solo founder?
Around five hours a week: two hours on Monday for list building, writing first lines and sending, ninety minutes on Thursday for replies and calls, and fifteen minutes a day checking replies. Plus a two-hour one-off setup.
How many cold emails should a solo founder send?
Roughly 50 approaches a week, or 400–600 a quarter. That is enough to produce fifty real conversations, which is the actual goal at this stage. Higher volume costs time you do not have and teaches you nothing extra.
What can a solo founder skip in outbound?
Sequences past three touches, A/B testing, more than two channels, dashboards, a CRM below about fifty open conversations, dedicated IPs, and cold calling at the start. Never skip warmup, separate sending domains, list verification or daily reply checks.
When should a founder stop doing outbound manually?
When you can say which message works and why, when replies take more than 45 minutes twice a week, and when you have more well-fitting companies than your hours allow. Automating before you know what works just scales a guess.