Follow-Up Email When a SaaS HR Director Replied Then Went Silent

Why this follow-up works

• People reply to their own unfinished sentence faster than to a vendor bump.
• You name three real HR stalls without scolding them for silence.
• The ask is smaller than whatever working session they originally agreed to.
• Archive language returns control, which HR actually wants.
• You refuse to paste the old pitch, so it still feels like a conversation.

When should I send this to a SaaS HR Director?

Give it 7 business days unless they named a date. Then write on that date, not the morning you got impatient. If their last line was after the freeze, look up the public hiring post if it exists and land the day after it lifts, not during. A second silence gets one archive note 5 days later. Do not weekly-drip an HR director who already talked to you. That trains them to mute the thread they once joined. If they said next headcount cycle, put it on your calendar and mean it. Showing up early reads as you didn't listen the first time. Offer weeks are sacred. Don't bump into them.

What this HR Director actually cares about

They already spent social energy on you. Treat them like a conversation, not a lead. Remind them of their words so they don't have to reload context between interviews. Calm, short, no guilt. An HR director will forgive a late bump. They will not forgive a forwarded thread with nothing new. Don't invent a steering committee. Don't ask for 30 minutes to recap. Ask whether the blocker is timing, people, or the work itself. Then offer archive. Owners of policy can tell a chase from a continuation. This should read like you are still in the room finishing their sentence. Confidentiality still applies. Don't quote something they would hate seeing forwarded.

How SaaS changes the note

SaaS people-ops threads die after a first yes because the HR director is not the only person who can move a vendor. They said interesting, then handed you to TA, security, or a CHRO who already has a calendar. Your job is to restart the conversation they joined, not to pretend you own their hiring plan. Quote them. Shrink the next step. Name the freeze if one is public. Evaluation windows swing from two weeks for a point tool to a full quarter when questionnaires pile up. A director who went quiet after a reply is often waiting on someone else's queue, not losing interest in the leak. Write like a peer who will archive without drama. That is rare enough to get a one-word answer between interviews.

Customization tips

• Use their real words. Paraphrase only if the quote would embarrass them in Slack.
• If they named a freeze end date, write the day after, not three days early.
• Don't CC the CEO to apply heat. That ends trust.
• Attach nothing. Offer the thinner page after they pick later or send.
• If a TA lead went quiet too, ask the director who owns it now, once.

Common mistakes

• Forwarding the whole thread with friendly bump and nothing else.
• Restacking the original culture deck because they once said interesting.
• CCing their CEO to manufacture urgency.
• Writing the day after their reply like they forgot you exist.

How this scenario compares

Questions people ask before they hit send