What this team is actually trying to do#
- “Build a list of fifty companies I can actually defend.”
- “Send from my own mailbox without wrecking my domain.”
- “Know which message worked before I hire anyone.”
- “Not pay per seat for a team of one.”
Start with fifty accounts, not five thousand#
The instinct is to make the list large because the reply rate will be low. It is exactly backwards at this stage. You are not running a volume machine, you are running an experiment with a sample size of one product and no proven message, and a large list mostly guarantees that the message never improves before the domain does.
Fifty accounts you can each say a specific sentence about is a week of work and it produces something a big list never does: an answer to why they replied, which is the input to everything that follows.
One mailbox, sent carefully#
At this volume you need one sending identity, not a pool. What you do need is the discipline that applies to a pool — a daily ceiling well under what your provider allows, hard bounces suppressed immediately, and an easy way out for anyone who does not want to hear from you.
Your domain is likely the same one your product's transactional mail leaves from, which raises the stakes rather than lowering them. A burnt domain at this stage is a genuinely expensive mistake.
The signal is what makes a founder's email work#
Founders have one enormous advantage and one disadvantage. The advantage is credibility: you can write about the problem in a way no rep can. The disadvantage is that you cannot fake relevance at scale, and you have no brand to lean on.
A public trigger resolves both. It supplies the reason to write today, and it lets the specificity you genuinely have land on an account that has a reason to care this week.
Build the record now, not at the first hire#
Every founder-led motion eventually gets handed over, and the handover is usually a mailbox and a spreadsheet. What the first hire needs is the sequence that worked, the objections that recurred, and where each conversation reached.
That costs almost nothing if the conversation, the deal and the paperwork were on one record from the first email — and it is very expensive to reconstruct afterwards.
What carries the workflow#
Every one of these is documented at /docs.
Questions#
Terms used on this page#
The full vocabulary is in the glossary.
Go deeper#
Other kinds of team#
Run it on one record
Signals, prospect search, sequences, deliverability, pipeline, e-signature and invoicing.