Should I write emails that a department head can forward?

Yes. Many won't champion something they can't explain in one skim. Write a paragraph their VP could understand without a briefing. That's often the real audience even when their name is on the To line. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What subject line works for E-commerce proposal follow-up emails (after a demo)?

Name the situation and the business object, not your excitement. Something like "Happy to trim [option] if budget is the blocker" outperforms "Just checking in" because a department head can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

How many times should I follow up with a Department Head (after a demo)?

Wait until the review window you agreed on. If none was set, five business days. Same day with the recap. A value bump 3 days later if they went quiet. After that, send a breakup note and archive it. A department head who wants it will answer a clean close more often than a fifth bump.

Should I lower the price in the follow-up?

Not as an opening move. Ask what's blocking the decision first. If budget is the issue, trim scope or phase the work. Discounting before you know the objection trains them to wait you out. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Should I include a recording in the demo follow-up?

If you recorded it and they agreed, yes, plus timestamps for the two parts they cared about. A raw 40-minute link with no map is homework. Add the three bullets they'd need to brief a colleague. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

E-commerce · Department Head · After Demo

Proposal Follow-Up for E-commerce Department Head: After De…

Use this proposal follow-up template when you're emailing a Department Head in E-commerce (after a demo). They saw the product. Now they're comparing, forwarding, or quietly deciding it wasn't for them. Keep the note aligned with Respectful of internal politics without being coy.

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

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this proposal follow-up work for a E-commerce Department Head?

Give them a clean no so they don't ghost out of politeness.
Speaks to carts that die, support queues that spike after campaigns, and inventory surprises instead of a generic "value prop."
Fits how a department head actually reads: Give enough context that they can forward the email upward.
Replay the two moments they leaned in, and the one concern they named.
Offer a smaller package so budget isn't a binary wall.

When should I send this to a E-commerce Department Head?

Wait until the review window you agreed on. If none was set, five business days. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" as the default, then adjust around they buy faster before peak and go dark during it. time the ask. If you're emailing a department head, Give enough context that they can forward the email upward.

What this Department Head actually cares about

A department head in E-commerce is protecting their team's load and their standing with leadership. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless. The hook that earns a look is a department KPI, a staffing bind, or a tool the team already hates. The ask should stay at this size: a working review they can invite a deputy to. Delete trigger: Going over their head in the same thread. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless.

How E-commerce changes the note

E-commerce buyers are operators chasing conversion, repeat purchase, and a calmer ops week. If you only talk about 'brand experience,' they'll assume you've never stood in a warehouse in December. A credible proof point in this vertical sounds like: lifted repeat purchase 14% with post-purchase follow-ups that didn't feel like coupons. Watch the language. Words that land here include AOV, SKU, 3PL, merchandising, contribution margin, returns. If you cannot name a peak-season miss, a new channel, or a 3PL meltdown, wait until you can. If you cannot name a peak-season miss, a new channel, or a 3PL meltdown, wait until you can.

How should I customize this template before I send it?

Replace the pain line with a DTC brand whose post-purchase email is still a generic coupon blast.
Keep the tone respectful of internal politics without being coy.
Quote the exact option names from the proposal so they don't reopen the PDF.
Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
Don't brag about your own store unless it's relevant.

What mistakes should I avoid with this after demo note?

Asking 'any thoughts?' after a 12-page proposal invites silence.
Don't send a 19-page deck that relitigates features they skipped.
Don't brag about your own store unless it's relevant.
Going over their head in the same thread.

How does this after demo scenario compare?

Dimension	For this template
Best send window	Same day, then 3 days if silent
Ideal length	Give enough context that they can forward the email upward.
Primary ask	a working review they can invite a deputy to
Industry metric to cite	conversion rate, AOV, and repeat purchase within 90 days
Tone	Respectful of internal politics without being coy.
Unlike after meeting	They have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposal	Pricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

Happy to trim [option] if budget is the blocker

Body

Hi [First Name],

Before this sits in a pile, I can cut [option] or split the rollout.

The version of this that matters for operators chasing conversion, repeat purchase, and a calmer ops week is lifted repeat purchase 14% with post-purchase follow-ups that didn't feel like coupons. I left [optional module] as optional on purpose. We can ship [core] first and keep [nice-to-have] for later.

Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start.

If the answer is not now, I can archive this cleanly.

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

On the date you both named. If you didn't name one, five business days is fair for most mid-market deals. Enterprise legal reviews can take longer, so ask what their review path looks like instead of guessing. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Related templates

Want a custom draft instead? Try the email generator.