Sales EmailTemplate

E-commerce · Operations Manager · After Demo

Referral Request for E-commerce Operations Manager: After D…

The query is practical: what should a referral request email to a E-commerce Operations Manager say for after a demo? Start with a direct answer, add one proof point about carts that die, support queues that spike after campaigns, and inventory surprises, and close with ask who else needs to see it, or whether a narrower use case is the

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 referral request work for a E-commerce Operations Manager?

  • Include a forwardable paragraph.
  • Speaks to carts that die, support queues that spike after campaigns, and inventory surprises instead of a generic "value prop."
  • Fits how a operations manager actually reads: Keep it operational: problem, impact, ask.
  • Replay the two moments they leaned in, and the one concern they named.
  • Explain why they'd look good for making the intro.

When should I send this to a E-commerce Operations Manager?

Ask after you've given them a reason to want to help, not after the first coffee. 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 operations manager, Keep it operational: problem, impact, ask.

What this Operations Manager actually cares about

A operations manager in E-commerce is protecting throughput, SLAs, and the team's Saturday. They want fewer exceptions, cleaner handoffs, and emails that include the facts. Strategy sermons bounce. The hook that earns a look is a bottleneck, a missed SLA, or a tool that creates rework. The ask should stay at this size: a working session on one process, with an agenda. Delete trigger: A vision paragraph with no owner and no metric. They protect throughput, SLAs, and the team's Saturday, so keep the ask at "a working session on one process, with an agenda."

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 practical.
  • Don't attach a commission offer unless that's already your model.
  • 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 'who do you know?' is lazy and gets no names.
  • Don't send a 19-page deck that relitigates features they skipped.
  • Don't brag about your own store unless it's relevant.
  • A vision paragraph with no owner and no metric.

How does this after demo scenario compare?

DimensionFor this template
Best send windowSame day, then 3 days if silent
Ideal lengthKeep it operational: problem, impact, ask.
Primary aska working session on one process, with an agenda
Industry metric to citeconversion rate, AOV, and repeat purchase within 90 days
TonePractical. Use verbs. Name the process.
Unlike after meetingThey have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposalPricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

Could you intro me to [role] at [Company]?

Body

Hi [First Name],

I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason].

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. Ideal person: [role] at a [company type] dealing with carts that die, support queues that spike after campaigns, and inventory surprises. Not trying to spray this across your whole book.

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

If you want changes to the blurb, tell me and I'll rewrite it.

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

Questions people ask before they hit send

Only if that's already how you work and it won't make them look mercenary. Many operators prefer a clean intro. If you do mention a fee, keep it secondary to why the intro helps the other person. 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.