Drafting a Cold Outreach Email by Voice

Speak a cold message that sounds written, not recited.

Voiskey Voiskey Team
Gmail DictationChrome ExtensionDrafting Cold Outreach

Plan the Message Skeleton First

A cold outreach message fails for predictable reasons: it opens with the sender, buries the reason for writing, and asks for something vague. Voice input does not fix those problems by itself, and it can make them worse when a nervous speaker fills the space with warmup phrases. Plan the skeleton before you dictate. Write four labels in a note: who this person is, why you are writing now, the one thing you want, and the smallest next step. Speak to those labels in order. The skeleton keeps the message short and stops you from improvising an introduction the reader will skip. Drafting a Cold Outreach message is easier when those four labels are already written and waiting.

Fill the skeleton with facts before you record anything. For the first label, write one sentence about the reader's role or recent work, using information you can actually point to. For the second, write the reason the timing matters, such as a launch, a change in team, or a shared deadline. For the third, write the ask in a single sentence. For the fourth, write the next step you can deliver, such as a short call or a sample. Facts you have written down are easier to speak cleanly than facts you are still deciding. Keep the note open beside the window while you speak.

Decide the length before you speak. A cold message should fit on one screen, and most should be shorter than that. Set a limit in the note, such as ninety words, and stop when you reach it. Voice input can produce text quickly, and quickly produced text tends to grow. A fixed limit forces you to choose the strongest reason rather than listing every reason you can think of. The reader's attention is the scarce resource, and a short message respects it without sounding abrupt. If the note reaches the limit before the ask, cut context rather than the ask itself.

Choose the one action you want before you write a single sentence. If you want a reply, ask for a reply. If you want a short call, ask for a short call and offer two times. If you want permission to send a sample, ask for permission. A message with two asks usually gets neither. Write the action at the top of the note and check the draft against it before you send. This decision shapes the opening, the body, and the closing, and it separates a clear message from a polite fog. Write the action as a verb so it is easy to check.

Speak the Opening Without Warmup Words

The opening line should do one job: give the reader a reason to keep reading. Most weak openings describe the sender, the company, or the weather. A strong opening names something specific about the reader and connects it to the reason you are writing. Say it in one breath, then stop. Do not clear your throat with phrases like I hope this finds you well or I wanted to reach out. Those phrases cost words and give the reader nothing. The first sentence should be the one you would keep if you could only send one sentence. Then say the second sentence.

Speak the opening before you speak the rest, then read it back. If it sounds like a template, rewrite it with one concrete detail. If it sounds like a compliment with no substance, replace the compliment with an observation the reader can verify. The test is simple: would this sentence still make sense if it were sent to a different person? If yes, it is too general. A specific opening earns the second sentence, and the second sentence earns the ask that follows it. Write the revised line in the note before you speak the rest of the message. Say it twice.

Keep the opening free of numbers you cannot support. A claim about growth, savings, or popularity invites a challenge and shifts attention away from the reader. If a number matters, place it later and tie it to a source the reader can check. The opening should create relevance, not prove a case. Voice dictation makes it easy to add impressive-sounding phrases; the edit pass is where you remove them. Fewer claims at the start means fewer objections before the ask. If you cannot source it quickly, leave it out and keep the opening focused on relevance. Then move on to the ask.

Read the opening aloud after you dictate it. If you run out of breath, the sentence is too long. If you stumble on a clause, the reader will too. Split it into two sentences and say each one plainly. The spoken version is a good test of clarity because it exposes the places where your own voice hesitates. Keep the version you can say without rehearsing. That version is usually the one a stranger can understand on the first read. A sentence you can say in one calm breath is usually a sentence a stranger can follow. Keep it plain and short.

Keep the Ask Short and Specific

The ask is the reason the message exists, so it deserves its own sentence. Put it after the shortest possible context and before any apology for taking the reader's time. Say exactly what you want: a yes or no, a fifteen-minute call, a forward to the right person, or permission to send one file. Vague asks such as let me know if you are interested give the reader nothing to do and no reason to reply. A specific ask is easier to answer, and an easier ask gets answered more often. Write the ask at the top of the note and keep it there.

Offer the reader a low-cost next step. A short call, a single question, or a link to a sample is easier to accept than a large commitment. Say the cost out loud, such as fifteen minutes or one reply, so the reader can judge it. If you are asking for a meeting, offer two specific times rather than an open calendar request. Two times turn a decision into a choice, and a choice is easier to make than a blank page. Write the cost beside each time so the reader can choose without asking. Two clear options are usually enough.

Remove every condition that makes the ask harder. Phrases such as whenever you have a chance or if it is not too much trouble sound polite but weaken the request. Say the ask once, plainly, and let the reader decide. If the ask depends on something the reader must check, name the thing and offer to wait. Do not stack apologies or explanations around it. A clean ask respects the reader's time more than a heavily softened one. Read the ask once more and remove any phrasing that turns a request into a hint. Then read the ask once more aloud.

End the message after the ask. A cold message does not need a long closing, a signature block full of links, or a summary of everything you just said. One short line that makes the next step easy is enough. If you want a reply, say that a one-line answer is fine. If you want a call, repeat the two times. The last sentence should reduce effort, not add it. A message that ends cleanly is easier to act on than one that trails off into background. A short ending also makes the follow-up easier to write in the same voice.

Edit for Tone and Specifics

Edit the draft in two passes rather than one. In the first pass, check the specifics: the reader's name, the role, the reason, the ask, and the next step. In the second pass, check the tone. Voiskey already removes filler words, stutters, false starts, self-corrections, and grammar slips, so you can spend the edit on meaning. Read the message as if a stranger had sent it to you. Would you know why they wrote, what they want, and what happens next? If any answer is missing, fix that before you polish a single adjective. Then read the ask sentence on its own.

Cut any sentence that does not support the reason or the ask. Cold messages accumulate background because the sender is nervous, and every extra sentence gives the reader another reason to stop. Highlight the sentence that states the reason and the sentence that states the ask, then delete anything that does not connect to either. If a detail is important, move it into a short clause rather than a separate paragraph. The edit is subtraction more than addition, and the result should feel lighter than the draft. If the highlighted sentences are far apart, the message has too much in between.

Check the tone for pressure and presumption. Words such as obviously, clearly, and just imply that the reader should already agree or should not need an explanation. Replace them with plain statements. Remove any claim about what the reader thinks, feels, or needs unless they told you. A cold message earns attention by being useful, not by telling the reader what they should want. Read each sentence and ask whether it would feel presumptuous if a stranger said it to you. If a sentence sounds like advice the reader did not ask for, cut it or make it a question.

Use Voiskey to read the draft back to yourself before you send. Speaking the message aloud exposes rhythm problems that silent reading hides. If a sentence is hard to say, it is probably hard to read. If the ask feels awkward when spoken, it will feel awkward in the inbox. Make the change, say it again, and keep the version that sounds natural. The spoken test is not about performance; it is a fast way to find the places where the writing is working against the reader. Then read the whole message once more for the rhythm between sentences. Then send.

Send and Log the Follow-Up

Send the message, then log it in the same place you track other outreach. Record the date, the reader, the ask, and the next step you offered. A short log prevents you from sending the same message twice and helps you follow up at the right time. Do not rely on memory for a follow-up that belongs three weeks out. Write the date you will check back, and keep the log where you will see it during your weekly review. Outreach without a log becomes a series of disconnected attempts. Keep the log to one line per message so it stays readable.

Plan the follow-up before you send the first message. Decide how long you will wait and what the follow-up will add. A follow-up that only repeats the first message adds nothing; a follow-up that offers a new detail, a shorter ask, or a specific time adds a reason to reply. Write one sentence in the log describing the follow-up angle. If you cannot think of an angle, the first message may have been too vague, and the follow-up will not rescue it. A follow-up with a new angle is a second attempt, not a repetition.

If you have not installed the app on the machine you use for outreach, download Voiskey there and dictate the follow-up in the same window you used for the first message. Keeping the tool consistent makes the second message easier to write in the same voice as the first. Install it, open the thread, and speak the follow-up in one short burst. Then read it once and send. Consistency between the first message and the follow-up matters more than a perfectly polished follow-up. Read the first message before you dictate the follow-up so the two match.

Review the outreach log monthly and look for patterns. Which openings got replies, which asks were answered, and which follow-ups produced a conversation? Keep the patterns, not the individual messages. If a particular opening shape works, reuse the shape rather than the exact wording. If a follow-up angle never works, stop using it. The log is a small feedback loop, and its value comes from review rather than from collection. A monthly read turns scattered messages into a method you can repeat. Keep the winning shapes in a short note and retire the rest without regret. Review the log quarterly.

FAQ s

Press the shortcut in the message field, speak the message, and polished text appears at the insertion point. Voiskey removes filler words, stutters, and false starts, and it adapts tone and phrasing to the goal, so the first draft arrives close to something you can edit.

It can help, because it removes the filler and false starts that make spoken text sound recited. Speak one concrete observation about the reader, then review the line in the edit step. The app adapts punctuation and tone, but the specificity has to come from you.

Speak the ask as its own sentence after the shortest context, then read it in the edit step. Keep one action, state its cost, and end the message after it. Voiskey's adaptation handles punctuation and formatting, but you still decide what the ask is.

No. Voiskey is a system-level typing app, so it places spoken text at the insertion point but does not send messages or schedule follow-ups. You open the thread, press the shortcut, speak the follow-up, and review it yourself before sending.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows to draft and refine cold messages in your compose window.

Use it across macOS, Windows, iOS, and Android

Use it across