Should I mention the original product pitch again?

No. They already have it. Quote their last operational sentence and offer a thinner artifact. Restacking features tells them you weren't listening. If the work changed, say what changed in one line. Then stop. The conversation is the asset, not your slide 4.

What if they said loop in my CTO and then went dark?

Ask once whether the CTO still owns it, and offer to write that person a 1-page note the CEO can forward. Don't email the CTO from a cold thread without permission. Don't CC both to force a meeting. Permission is the product here.

Is a breakup email too aggressive after one reply?

Archive language isn't a breakup tantrum. It's a filing question. CEOs respect people who will leave. Send it after the quiet follow-up, not as the first restart. If they still want it, they will say later. If they don't, you saved both calendars.

Can I call instead of emailing the bump?

Not unless they already take your calls. A voicemail that recites the pitch after a written yes is how you become a story in their exec Slack. Stay in the thread they chose. If they want a call, they will propose a clock.

How much of their quote should I paste?

One sentence, the operational one. Don't paste a paragraph they wrote on a phone. Don't quote something political they would hate seeing forwarded. If the quote would embarrass them, paraphrase the constraint and still give them the later door. That's the working rule here.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · CEO · Replied Then Silent

Follow-Up Email When a SaaS CEO Replied Then Went Silent

When a SaaS CEO answers once and then disappears, your follow-up should quote their last sentence and ask a cheaper question. They already spent political energy. Don't restack the deck. A board week, a security owner, or a freeze eats threads.

Copy-ready template

Subject

Re: [Their Last Topic] still on, or archive?

Body

Hi [First Name],

You said [Quote their last line about timing / owner / the pilot]. Then the thread went quiet, which at CEO often means a board week landed, [Security Owner] hasn't looked, or a freeze hit [Company Name].

Would a 1-page version of that plan still help, or should I archive until after [Date they named / next board]? Reply later or archive. I won't paste the old slides.

[Your Name]
[Your Title]
[Your Company]

Why this follow-up works

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

When should I send this to a SaaS CEO?

Give it 6 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 board, look up the board date if it is public and land the day after, not during. A second silence gets one archive note 5 days later. Do not weekly-drip a CEO who already talked to you. That trains them to mute the thread they once joined. If they said next quarter, put it on your calendar and mean it. Showing up early reads as you didn't listen the first time.

What this CEO 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 customer calls. Collaborative, short, no guilt. A CEO will forgive a late bump. They will not forgive a forwarded thread with nothing new. Don't invent a 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 P&L can tell a chase from a continuation. This should read like you are still in the room finishing their sentence.

How SaaS changes the note

SaaS threads die after a first yes because the CEO is not the implementer. They said interesting, then handed you to a CTO, a security queue, or a CS lead who already has a stack. Your job is to restart the conversation they joined, not to pretend the buying process is a funnel you own. Quote them. Shrink the next step. Name the freeze if one is public. Evaluation windows in this industry swing from two weeks for a point tool to a full quarter when questionnaires pile up. A CEO who went quiet after a reply is often waiting on someone else's calendar, not losing interest in the problem. Write like a peer who will archive without drama. That is rare enough to get a one-word answer.

Customization tips

Use their real words. Paraphrase only if the quote would embarrass them in Slack.
If they named a date, write on that date, not three days early.
Don't CC the CRO to apply heat. They will feel it.
Attach nothing. Offer the thinner page after they pick later or send.
If a champion went quiet too, ask the CEO who owns it now, once.

Common mistakes

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

How this scenario compares

Dimension	For this template
Best send window	6 business days, or the date they named
Ideal length	Under 75 words, quote plus one door
Primary ask	Send a thinner page, later, or archive
Unlike a no-response note	They already spent energy. Quote them.
Unlike a proposal bump	You may not have a PDF on the table yet

Questions people ask before they hit send

They needed to check with a CTO, a fire started, or your last ask was bigger than they meant to take on. A good follow-up shrinks the next step and references what they already said so they don't have to reload context between customer calls.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1035.