--- title: "AWS re:Invent 2026: A Marketplace Prep Checklist" url: https://www.suger.io/resources/blog/aws-reinvent-2026-marketplace-prep/ canonical: https://www.suger.io/resources/blog/aws-reinvent-2026-marketplace-prep/ type: Blog description: "AWS re:Invent 2026 runs Nov 30–Dec 4. The marketplace prep to finish first: co-sell pipeline, offer readiness, listing hygiene and follow-through." --- # AWS re:Invent 2026: A Marketplace Prep Checklist > Canonical HTML version: https://www.suger.io/resources/blog/aws-reinvent-2026-marketplace-prep/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. AWS re:Invent 2026: A Marketplace Prep Checklist # AWS re:Invent 2026: A Marketplace Prep Checklist re:Invent rewards the sellers who did the work beforehand. The marketplace, co-sell and offer prep worth finishing before you land in Las Vegas. [![Stacy Wu](/authors/stacy-wu.jpg)](/resources/blog/author/stacy-wu/) [Stacy Wu](/resources/blog/author/stacy-wu/) Aug 27, 2026 ![AWS re:Invent 2026: A Marketplace Prep Checklist](/images/blog/aws-reinvent-2026-marketplace-prep/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-reinvent-2026-marketplace-prep%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Cloud%20GTM. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-reinvent-2026-marketplace-prep%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Cloud%20GTM. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-reinvent-2026-marketplace-prep%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Cloud%20GTM. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-reinvent-2026-marketplace-prep%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Cloud%20GTM. "Summarize with Perplexity") Table of Contents - [Six weeks out: decide who you are actually going to meet](#six-weeks-out-decide-who-you-are-actually-going-to-meet) - [Six weeks out: get your co-sell pipeline in order](#six-weeks-out-get-your-co-sell-pipeline-in-order) - [Three weeks out: make sure you can transact](#three-weeks-out-make-sure-you-can-transact) - [Three weeks out: listing hygiene before the traffic arrives](#three-weeks-out-listing-hygiene-before-the-traffic-arrives) - [The week itself: capture, don’t close](#the-week-itself-capture-dont-close) - [After the event: the follow-through that pays for the trip](#after-the-event-the-follow-through-that-pays-for-the-trip) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _AWS re:Invent preparation for marketplace sellers is the work you finish before the event so the conversations you have there can convert: a qualified target list, co-sell referrals already submitted, offers ready to send, and a listing that survives a traffic spike._ * * * AWS re:Invent 2026 runs November 30 to December 4 in Las Vegas. Almost everything that determines whether the trip pays for itself happens before you get on the plane. The failure pattern is consistent. A team arrives with a booth, collects a few hundred badge scans, comes home, and discovers that nobody can tell which of those conversations was real, that the one genuinely hot account needs a private offer nobody has drafted, and that the follow-up email goes out eleven days later to a contact who has already forgotten the conversation. The event was fine. The preparation wasn’t. Here is what to finish first. * * * ## **Six weeks out: decide who you are actually going to meet** Start from the account list, not the booth. A re:Invent target list is the small set of accounts where a conversation at the event would meaningfully advance a deal — not everyone attending, and not everyone in your CRM. Three groups are worth the effort: open opportunities where an in-person meeting compresses the cycle, existing customers with an expansion or renewal ahead of them, and AWS sellers who cover your target accounts. That last group is the one most teams under-invest in, and it is the one the event is uniquely good for — the AWS field is all in one place for a week, which is true of no other time of year. Book those meetings before the calendar fills. By mid-November the people you want are fully booked. ## **Six weeks out: get your co-sell pipeline in order** Submit your referrals before the event, not after. A referral submitted in advance gives the AWS seller covering that account a reason to meet you at the show, and it means the conversation starts from a shared record rather than from an introduction. This is also the moment to clean up what is already submitted. Stale referrals with no recent activity, missing next steps, or a contact who has left the company all make you look like a partner who does not maintain their pipeline — which is exactly the impression you do not want going into a week of AWS conversations. If your co-sell hygiene needs work, [the ACE guide for ISV sellers](/resources/blog/aws-ace-guide-for-isv-sellers/) covers what a submission needs to survive review, and [how co-sell works](/resources/blog/how-co-sell-works/) covers the motion end to end. ## **Three weeks out: make sure you can transact** Have the offers drafted before somebody asks for one. The worst outcome at an event is a buyer saying yes and your team needing a week to turn that into paper. For each target account, know in advance what you would send: the pricing, the term, the payment schedule, and who has to approve it internally. [Private offers](/platform/private-offers/) can be drafted and held rather than sent, so the deal desk work happens in November when it is calm rather than in December when it is not. If the buyer is procuring through a reseller, confirm the partner relationship is in place first — a multiparty offer discovered at the booth is a January deal, not a December one. Check the unglamorous things too: that the people who need to approve an offer are not all on vacation the week of the event, and that whoever is staffing the booth can actually reach them. ## **Three weeks out: listing hygiene before the traffic arrives** An event drives traffic to a listing that most teams have not looked at in months. Before that happens, read your own listing the way a buyer would: is the description current, are the screenshots from this version of the product, is the pricing right, and does the trial or demo path actually work? This matters more than it sounds. Event traffic is the highest-intent traffic you get all year, and it arrives at a page you have not audited since launch. The [marketplace listing readiness checklist](/resources/blog/marketplace-listing-readiness-checklist/) is the longer version of this audit. ## **The week itself: capture, don’t close** At the event, optimize for the quality of the record rather than the volume of scans. A badge scan with no context is worth close to nothing three weeks later. The discipline that works is small: for every conversation that matters, capture who they are, what problem they described in their words, and what the agreed next step is. Log it the same day. A conversation recorded on Tuesday and written up on Friday has already lost the detail that made it useful. ## **After the event: the follow-through that pays for the trip** Follow up within a week, while the conversation is still recent. Convert the real ones into referrals, send the offers you already drafted, and — this is the part teams skip — record which pipeline actually came from the event. Without that last step you will have the same argument next year about whether the trip was worth it, and no data to settle it. Suger’s [reporting](/platform/reporting/) exposes the `cosell_referral` and `marketplace_offer` datasets, so referrals created and offers sent in the weeks around the event can be measured against everything else you did that quarter. * * * ## **Frequently asked questions** **When is AWS re:Invent 2026?** AWS re:Invent 2026 runs November 30 to December 4, 2026, in Las Vegas. AWS publishes the current dates and registration details on its own event page. **What should a marketplace seller prepare before re:Invent?** A target account list, co-sell referrals submitted in advance, private offers drafted and ready to send, and an audited listing. The transaction mechanics should be settled before the event, not during it. **Should I submit co-sell referrals before or after the event?** Before. A referral already in the system gives the AWS seller covering that account a reason to meet you, and the conversation starts from a shared record rather than an introduction. **How soon should I follow up after re:Invent?** Within a week. Log each meaningful conversation the same day it happens, then send offers and referrals while the discussion is still fresh — detail decays fast after an event. **How do I know whether the event was worth it?** Decide the measurement before you go. Track referrals created and offers sent in the weeks following the event against your baseline, so the answer is a number rather than an argument. * * * ## **Takeaways** - re:Invent 2026 runs November 30 to December 4. The work that decides whether it pays off happens weeks earlier. - Build a target list of accounts where a meeting moves a deal, and book those meetings before mid-November. - Submit and clean up co-sell referrals in advance — it gives the AWS field a reason to meet you and starts the conversation from a shared record. - Draft the offers before you travel, and audit the listing before event traffic reaches it. - Decide how you will measure event-sourced pipeline before you go, or you will have the same argument next year with no data. * * * Get the transaction mechanics settled before the show: see how [private offers](/platform/private-offers/) and [co-sell](/platform/cosell/) work in Suger, or [book a demo](/schedule-demo/). ## Sources Primary sources for the platform rules cited above. Last verified August 27, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS re:Invent](https://aws.amazon.com/events/reinvent) — The 2026 dates and location stated in this post: November 30 – December 4, Las Vegas. - [Suger docs: Available datasets](https://doc.suger.io/analytics/available-datasets/) — The cosell\_referral and marketplace\_offer datasets used to measure event-sourced pipeline after the show. ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.