Request-Path Response Templates¶

From Ron Davis — AWS Marketplace discovery & GTM · From listed to bought.

Five paste-ready replies for the moments a buyer acts on your listing — demo request, private-offer request, co-sell add-on, the follow-up, and the post-call private offer. Swap the brackets, keep the structure.

The one thing to remember: A request is a timed asset. The buyer raised a hand because a need is live now — reply within the day, name a next step, and make saying yes a single click. Every hour you wait, intent decays.

1 · Reply to a demo request¶

Buyer clicked "Request a demo." Goal: book the call, qualify lightly.

Subject: Re: your demo request — [Product] on AWS Marketplace

Hi [name] — thanks for raising your hand on [Product]. So I make the 20
minutes count: what's the outcome you're trying to hit, and is there a
timeline or event driving it? Grab whatever slot works here → [scheduling
link]. If it's easier, reply with two windows and I'll send an invite.
Either way you'll leave with a clear view of fit and next steps. — Ron

2 · Reply to a private-offer request¶

Buyer wants pricing. Goal: get the 3 inputs you need to cut it.

Subject: Re: private offer for [Product]

Hi [name] — happy to put a private offer together on AWS Marketplace.
Three quick inputs and I can have it in your account fast: (1) the term
you're planning — 12, 24, or 36 months; (2) the seats / usage tier you
expect; (3) the AWS account ID the offer should land in. If committed
spend (EDP/MACC) matters on your side, flag it and I'll structure so it
draws down. I'll send the offer link and walk you through accepting. — Ron

3 · Reply that adds AWS co-sell¶

Buyer is AWS-committed or has a rep. Goal: register the opportunity and pull the field in.

Subject: Re: [Product] — want me to loop in your AWS team?

Hi [name] — since this runs on AWS, I can register it as a co-sell
opportunity in ACE so your account team is in the loop and any funding or
credits you're eligible for are on the table. If you can share your AWS
account ID and the rough monthly spend this touches, I'll frame it to the
outcome you're after — not just my product — so it actually gets worked.
Want me to register it before our call? — Ron

4 · The follow-up¶

No reply in 3–5 business days. One nudge, then let it rest.

Subject: Still worth 20 minutes on [Product]?

Hi [name] — circling back on your request. If the timing slipped, no
problem — want me to check in next quarter, or is this still live? If it's
live, here's my calendar → [scheduling link]. If it's dead, a one-word
"pass" is a gift and I'll stop chasing. — Ron

5 · The post-call private offer¶

Right after the demo. Goal: deliver the offer and make acceptance frictionless.

Subject: Your [Product] private offer — ready to accept

Hi [name] — great talking today. As discussed: [term] at [price], landing
in AWS account [ID]. Your private offer is live here → [private-offer
link]. Accepting takes about two minutes and it bills through your existing
AWS agreement (draws down committed spend if you have it). I've attached the
one-pager for your internal sign-off. Anything blocking a yes this week? — Ron

Do: reply same day · name one next step · ask for the AWS account ID early · make acceptance one click · register co-sell before the call when it fits.

Don't: let a request sit overnight · send a wall of features · bury the link · ask "when works for you?" with no options · skip ACE and expect credit.

Want the request path wired, not just templated? Book a free 30-min call → https://calendly.com/itsrondavis/vellocity-gtm-discovery-30-min Weekly GTM teardown → https://itsrondavis.substack.com