- A product that runs on the cloud
- A marketplace listing only makes sense if buyers can deploy and use the product in the provider's environment. A working build is acceptable, even if it is a first version. Without it, the listing cannot be submitted and the work stops at readiness.
- Your pricing and contract position
- Marketplace offers need a stated way to buy, such as a subscription or a private offer. Your approved structure is acceptable, in rough form. Without a decision, listing copy cannot describe how buying works and the offer stays unfinished.
- A list of accounts you want to reach
- Co-sell briefs are written for named companies, so someone must choose them. A short list with a reason for each is acceptable. Without it, the pitch pack stays generic and provider sellers have nothing specific to act on.
- A contact for technical submission
- Someone in your team must complete the provider's technical forms and answer reviewers. An engineer with time set aside is acceptable. Without that person, approved copy waits for answers and the submission cannot move forward, because reviewers ask technical questions only your team can answer.
- Customers you may name
- Provider sellers ask for proof that others already buy. Customers who have agreed in writing to be named are acceptable, and none is also acceptable. Without consent, no customer is named and the pitch relies on the product alone.