Speak a four-beat intro script that lands cleanly and earns a fast reply.

A Four-Beat Template for email introductions gives you a spoken script with four jobs to do: name the reason for the message, introduce each person in one line, connect them with a concrete overlap, and close with a next step. Each beat answers a question the reader would otherwise ask. Beat one covers why this note exists now. Beat two covers who is writing and who is being introduced. Beat three covers why these two people should spend time together. Beat four covers what happens after the reader finishes. Write the four jobs on a card and keep it beside your screen. When you speak from a card with four jobs rather than four sentences, you can vary the wording on every message without losing the structure.
Assign a fixed order and a length budget to each beat before you try a live message. Beat one earns two sentences at most: the reason you are writing and the event or question that prompted it. Beat two gets one sentence per person, written as role plus a recognizable detail, such as the team they run or the problem they own. Beat three gets two or three sentences and must name a specific overlap rather than a vague compliment. Beat four gets one sentence with a single, low-effort action. Total the budget and aim for under one hundred and twenty words. When a draft runs long, cut from beat three first, because that beat is where enthusiasm turns into a paragraph nobody asked for.
Decide what counts as evidence for beat three before you write. A useful overlap is something both people can verify in one line: a shared project, a complementary skill, a customer segment one person understands and the other serves, or a decision one person is currently making. Weak overlaps sound like nice to meet you both or you should know each other, which push the work of finding a reason back onto the reader. Keep a short list of current openings, such as a role being hired or a launch being planned, and match each intro to one item on that list. If you cannot name a verifiable overlap, delay the intro and ask one of the two people a question first.
Write the four jobs, not the final sentences, on a card you can read while speaking. Jobs survive rewording, while sentences break the moment a name changes or a detail is wrong. On the card, note the greeting style you use for each audience, the one fact you must include, and the action you want in beat four. Include a reminder to check the spelling of both names before you speak, since a mispronounced name is the hardest error to fix later. Keep the card in a note you can open in the same window where you write. After a week, the four jobs become automatic and the card turns into a checklist.
Start the message in the field where you will send it rather than in a separate document. Put the cursor in the body, take one breath, and say the greeting and beat one as a single unit. Speaking in place removes the copy-and-paste step that usually introduces duplicate greetings and mismatched punctuation. Keep your pace slightly slower than conversation, because names and company terms need a fraction more clarity than ordinary words. If you stumble in beat one, keep going and finish the beat; a small self-correction spoken immediately is easier to clean than a restart. Pause for one second between beats, which gives you a moment to hear whether the previous sentence closed the job it was meant to close.
Treat each beat as a separate spoken paragraph and say the transition out loud. Phrases such as the reason I am writing, let me introduce both of you, and here is what I suggest next act as markers that keep you inside the structure. They also help the reader scan the message later. Do not read the markers from the card word for word; say them in your own phrasing so the note does not sound like a form letter. When you finish beat three, stop talking for a moment and decide the single action for beat four before you speak it. That pause is the difference between a clear ask and three half-asks stacked in one sentence.
Handle names deliberately. Say each full name once, then use first names for the rest of the message. If a name is unusual, spell it after you say it, for example say the name, then say spelled as it sounds letter by letter. This sounds awkward in speech but produces a correct message, and the correction is cheaper than a follow-up apology. Say the company or team name in full the first time and shorten it later. When two people share a first name, add a short descriptor each time, such as the designer or the analyst, so the reader never has to guess which person a sentence refers to.
Close the spoken draft with the action, then stop and read. Do not add a second paragraph of thanks, background, or offers to help, because those additions are what turn a tight intro into a long one. Read the text once for the four jobs: reason, people, overlap, action. If a job is missing, say the missing sentence at the end rather than editing the middle. If the note is over the budget, remove the weakest sentence from beat three. When the four jobs are present and the names are right, send it. A short intro that arrives today beats a polished one that waits for better wording.
Short beats come from specific nouns, not from short words. Compare a vague sentence about helping teams work better with a sentence about shortening a weekly review from ninety minutes to forty. The second one is longer in characters and far more useful, because it gives the reader something to react to. Before you speak, choose one concrete noun for each beat: a project name, a role, a deadline, a decision. Say that noun early in the sentence. If you cannot find a concrete noun for beat three, you do not yet have a reason to introduce the two people, and the honest move is to delay the message.
Cut the phrases that add length without adding information. Openers such as I hope this message finds you well, I wanted to reach out, and just a quick note all delay the reason for writing. Replace them with the reason itself. The same rule applies to closers: let me know if you have any questions can become a single suggested time. Keep one courtesy line if your audience expects it, and put it in the greeting rather than in a paragraph of its own. When you review a draft, count the sentences that could be deleted without changing the request; if there are more than two, the message is carrying filler.
Give beat four one action and one owner. An action is a decision the reader can make in under a minute, such as reply with a yes, pick one of two times, or send a short note to the other person. Two actions split attention and usually produce neither. Name who moves first, for example ask the person being introduced to reply to the thread, or ask the introducer to propose a time. Avoid open-ended invitations to connect sometime, because they turn a clear intro into a scheduling project. If the honest next step is nothing, say that the note is informational and no reply is needed.
Read the draft aloud as a final length check. Speaking the text back exposes sentences that run out of breath and clauses that pile up, which are the same places a reader will slow down. Mark any sentence you cannot finish in one breath and split it. Then check the ratio of names to pronouns; a paragraph with three instances of them or this is harder to follow than one that repeats a name. Finally, verify that the subject line matches beat one, because a mismatched subject is the most common reason a good intro goes unread. These three checks take under a minute and catch most length problems.
Once a spoken intro reads well, keep the version that worked instead of trusting memory. Save the text in a note named for the situation, such as vendor intro, hiring intro, or customer intro, and add one line describing the overlap you used. Do not save the names or the personal details; save the structure, the markers, and the action pattern. When a similar situation appears, open the note, speak the four beats again with the new details, and compare the result with the saved example. This habit turns one good message into a repeatable pattern without turning it into a stiff form letter that readers recognize and ignore. Download Voiskey for Mac and Windows if you want the spoken draft to land polished at the cursor while you practice the pattern.
Build a small library of three intros rather than thirty. Most people need one version for a warm contact, one for a cold contact, and one for a referral. Each version has the same four beats but a different tone in beat one: warm notes can reference the last conversation, cold notes must earn attention with a specific reason, and referral notes should name the person who suggested the contact. Store the three side by side so the differences are obvious. When you write a new message, start from the closest version and change only what the situation requires. Keeping the set small also makes it easy to reread all three before a busy morning.
Use the app's learning to keep names and terms consistent across the library. Voiskey learns names, jargon, acronyms, and spelling preferences, so a spelling you correct once tends to stay corrected. Say product names, team names, and unusual surnames clearly during early sessions, and fix the text immediately when something appears wrong. Add the corrected spelling to the note beside the intro so a colleague using the same library produces the same result. If your group introduces the same partners repeatedly, the team plan offers shared vocabulary and workflows, which keeps spelling consistent without a separate style guide or a long review meeting.
Review the library on a fixed schedule, for example the first Monday of each month. Delete intros for situations that no longer occur and update any note whose overlap language has gone stale. Read each saved example aloud once and mark the sentence you would now cut. Then record the date beside the version you keep, so a later reader knows how old the pattern is. This short review prevents the library from becoming a museum of messages that no longer match the work. The goal is three current patterns you can speak from memory, not a large archive you never open.
Track what happens after you send, because replies are the only reliable measure of whether the four beats did their job. For each intro, note whether the recipient replied, whether the two people connected, and which beat the reply referenced. A reply that asks who the other person is points to a weak beat two. A reply that asks why they should talk points to a weak beat three. A reply that agrees but never schedules points to a vague beat four. Keep this log for two weeks, then fix the beat that produced the most questions rather than rewriting the whole template.
Refine one beat at a time so you can tell which change helped. If beat three is weak, collect three overlaps that produced an immediate reply and use their shape as the new pattern. If beat four is weak, replace open invitations with one proposed action and one proposed owner. Change only that beat for the next five intros and compare the reply rate with the previous five. This is not a formal experiment, but it is honest enough to stop you from making five changes at once and learning nothing. Write the change and the result in the same note as the library.
Keep the spoken workflow fast by separating drafting from deciding. Speak the four beats, read the result once, and make a single decision: send, delay, or drop. Delay is correct when a name, an overlap, or an action is missing. Drop is correct when you cannot state why the two people should talk. Most rambling comes from trying to decide while speaking, which produces extra paragraphs restating the same uncertainty. Decide first, then speak, then send. Voiskey keeps this loop short because the polished text appears where you already type, so the step between speaking and sending is a single read.
End the review with a written standard you can hand to someone else. The standard should say what counts as a complete intro, the word budget, the one action allowed in beat four, and the check for names and overlap. Add one example of a good intro and one of a message that should have been delayed. When a colleague starts using the same pattern, ask them to speak one intro and compare it with the example before they send anything to a real contact. Download Voiskey, run your next three intros through the four beats, and keep the reply log beside the library so the pattern improves on evidence.
Voiskey is an AI voice typing app that works at the system level. Press a shortcut, speak the four beats in order, and the polished text appears at the insertion point in your message window. It removes filler words, stutters, false starts, and self-corrections, so a rushed delivery still lands as a clean note you can send after one read.
Speak from the four jobs rather than a memorized paragraph, and say each beat as one sentence. With Voiskey you can stop after the fourth beat, review the text at the insertion point, and correct a single phrase by voice instead of retyping. Because it adapts punctuation, formatting, tone, and phrasing to what you are doing, the note reads like a written message.
Yes. Voiskey learns names, jargon, acronyms, and spelling preferences as you use it. Say the two names in the intro clearly during your first messages, correct any misspelling once, and later notes will carry the right form. Keep a short list of frequent contacts and their preferred spellings near your screen. The team plan adds shared vocabulary and workflows, so colleagues introducing the same people stay consistent.
Speak the four beats at your normal pace, let Voiskey polish the text at the insertion point, then type only the parts that need a personal detail such as a project name, and edit once before sending. Because it composes in the field where you already type, there is no copy-paste step between tools. Most short intros finish in well under a minute, which makes the loop practical for a daily habit.

Download Voiskey for Mac and Windows and turn the four-beat intro into a one-minute habit.
Use it across macOS, Windows, iOS, and Android