# AWS Offer Desk

> List a SaaS product and price private offers on AWS Marketplace. Paste your AWS Marketplace SaaS listing setup and a
> private offer draft, and get the fit verdict, the irreversible choices, the exact fee tier and the offer pre-check
> against AWS Marketplace rules, then the listing plan or the offer review.
> Built on the SkillSafe skill @samber/aws-marketplace-playbook, from samber/developer-platform-skills (MIT), by
> Samuel Berthe.
> Not affiliated with or endorsed by Amazon Web Services.
> Scope: an ISV seller's own SaaS listing on AWS Marketplace and its private offers - whether to list, the irreversible
> account and pricing-model choices, going Public, private offers, CPPO resale authorizations, commitment drawdown and
> co-selling through ACE and ISV Accelerate. Not job offers, not sales quotes, not buyers or resellers, not listing copy,
> not metering code.

https://aws-offer-desk.skillsafe.ai/

## What is free
- The listing: the pricing model (SaaS contract, contract with consumption, subscription, free), the stage (not registered, registered, integrating, Limited, Public, first offer sent, co-selling), another public paid product, one dimension per line (api name | display name | kind: entitled, metered or custom-for-offers | unit | public price), the public contract terms, a free trial, planned public price changes (dimension | old | new | date), the seller account, the hosting, a third-party service off AWS, the Deployed on AWS badge, Partner Central, the buyers, how you sell today, the offer owner, engineering weeks, a target date and the countries.
- The private offer draft (optional): the buyer and the buyer country, an existing customer moving the renewal, the renewal flag, a replacement offer, the total contract value (USD, written as $120k, USD 120,000, 120000 or 1.2M), the term, the installments (date | amount), net terms, auto-renewal, a reseller (CPPO) with the wholesale price, professional services, the expiry and the buyer-side notes.
- The fit verdict (transact_with_commit, transact_no_commit, skip_for_now) with the answers behind it; the recommended pricing model; the irreversible-choice register (seller_account, pricing_model, dimension_api_name, custom_dimension, reseller_authorization, auto_renewal_optout, offer_terms), each with the item it names, what locks it, the decision from the input and "unassigned" owner and date.
- The listing checks, each with an id, a subject where one id repeats, the rule and pass, fix, fail, note or n/a: seller_account; model_fit; dim_listed, dim_dup, dim_name, dim_custom, dim_metered and dim_free (a dimension is its API name plus its kind); public_terms; price_change and price_window (one change per 90 days† after an increase); trial_days (7-90 days†); billing_channel (no card capture, no links to other clouds); first_offer_public (a public paid listing before any private offer); commit_burn (commit language only with the badge); badge; partner_link; offer_owner; target_date.
- The fee on the pre-tax total contract value, line by line (base, rate, fee, net): new private offers 3%† under $1M†, 2%† from $1M† to $10M†, 1.5%† above; every renewal 1.5%† at any size; CPPO +0.5%† on the wholesale price, out of your payout; South Korea buyers +1%†; professional services 0.5%†, or 0%† inside a qualifying multi-product offer set (check eligibility); 3%† for a SaaS public offer. Tier ids: public, new_under_1m, new_1m_10m, new_over_10m, renewal.
- The offer pre-check: tcv, term, renewal_flag, inst_model, inst_line, inst_sum, inst_date (an installment is its index plus its date), inst_before, inst_first, net_terms (Net 15 to Net 120†), auto_renewal, replace, expiry, pmp, cppo_sor, cppo_wholesale, korea, ps and rep_comp; the buyer pre-check (aws_account, private_marketplace, invoice, active_agreement, commitment, currency, country) as ready, missing or unknown.
- The co-sell ladder (ACE > FTR > ISV Accelerate > promotion credits) with this quarter's rung and the condition to move up: FTR roughly 2-4 weeks†; ISV Accelerate by invitation after 5 launched† and 15 qualified† opportunities and $2,000† of AWS revenue; AWS-referred opportunities answered within 5 business days†; field engagement 6-12 months† after listing.
- The timeline to the first deal from today: registration with KYC (up to two weeks, reported), integration in parallel, a week of Limited testing (the page's own assumption), Public review in 7-10 business days†, 3-6 weeks† from registration to Public, and the first offer - with a warning when the target date falls before it.
- Exports: the register (.csv), the checks (.csv), the fee breakdown (.csv), everything (.json), the fixed dimension list (every line as pasted with its flags above it - nothing renamed or removed, because API names never change) and the offer summary for the deal desk (.md, copied from the draft; the one thing it may add is the renewal flag an existing customer's renewal needs).
- Saved listings keep a compact snapshot of the checks: reopening one, or pasting a listing of the same name, shows what changed since it was saved.
- Every AWS figure carries a dagger: 90 days†, 1, 12, 24 or 36 months†, 7-90 days†, the 20%† AMI fee, 7-10 business days†, 3-6 weeks†, the fee tiers above, USD, EUR, GBP, AUD and JPY†, Net 15 to Net 120†. Practitioner claims say reported: KYC up to two weeks, reported; offers set to 30 days and extended, reported.
- † verify against the current AWS Marketplace Seller Guide before quoting it.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or offer), `listing` (the listing setup as read), `dimensions` (one line per dimension), `offer` (the offer draft as read, or empty), `carry` (offer only: the plan's model, fit, register and fixes), `facts` and an optional `retry_note`.
- `plan` replies with `summary`, `verdict` (`fit`, `why`), `model` (`pricing`, `why`), `register` (`choice`, `item`, `decision`, `owner`, `by`), `fixes` (`check`, `subject`, `change`), `timeline` (`step`, `wait`), `cosell` (`rung`, `next`), `footnote` and `caveats`.
- `offer` replies with `summary`, `fee` (`tier`, `rate`, `amount`, `net`), `checks` (`check`, `subject`, `finding`, `change`), `terms` (`installments` starting keep or fix, `net_terms`, `renewal`, `expiry`), `buyer_precheck` (`item`, `status`), `message` (each item on its own line), `footnote` and `caveats`. It needs the offer draft.
A reply stays on the page when the form changes after it ran, under an out-of-date banner, and its downloads and copies keep working; each plan fix and each offer check copies on its own, and the plan's handoff carries its model, fit and register into the offer lane.
The page holds every reply to its own facts, matching rows by the same composite identity its facts use (a register row is its choice plus its item; a check row is its id plus its subject): the plan keeps the page's fit verdict, model and co-sell rung, one register row per page row, a fix for every listing fail and a timeline with every wait marked; the offer keeps the page's fee tier, amount and net, one row per offer check that fails or warns, keep or fix on the installments as the page says, the renewal flag when it is missing, the buyer pre-check statuses, and a message one item per line with no commit-burn language unless the badge is held and no signature date earlier than review allows; both carry the dagger on every AWS figure, reported on every practitioner claim, the footnote, no URL, no backticks and no implied AWS endorsement.

## Links
- API tutorial: https://aws-offer-desk.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/aws-marketplace-playbook
- Source repository: https://github.com/samber/developer-platform-skills