Audit and rewrite cloud marketplace listings for higher conversion

Create a Google Doc with your current listing content, including title, short description, long description, categories, search terms if available, screenshots, videos, pricing or private-offer notes, deployment model, support links, reviews, and FAQs. Add the approved product positioning, proof points, security or compliance statements, integration list, and customer-safe claims. Include the relevant AWS Marketplace or Microsoft Marketplace listing requirements your team must follow so the rewrite does not create a submission problem. Mark each claim as approved, needs confirmation, or do not use. This gives Claude enough context to improve the listing without inventing marketplace-sensitive details.

Use Claude to define the different people who may read the listing: business sponsor, technical evaluator, cloud architect, security reviewer, procurement owner, marketplace seller, and partner seller. For each reader, document what they need to understand before clicking, sharing internally, requesting a private offer, or starting procurement. Add decision questions such as deployment fit, integration fit, risk, support, ROI, contract path, cloud credit use, and vendor credibility. Keep this buyer brief in the same Google Doc so every rewrite can be judged against it. A strong marketplace listing should answer multiple buyer jobs quickly without becoming a dense product brochure.

Create a marketplace buyer brief for this offer.

Product or offer summary:
{{product_summary}}

Current listing:
{{current_listing}}

Target industries or segments:
{{target_segments}}

Marketplace channel:
{{marketplace_channel}}

Create buyer jobs for:
1. Business sponsor
2. Technical evaluator
3. Cloud architect or IT owner
4. Security or compliance reviewer
5. Procurement owner
6. Partner or cloud seller

For each, include:
- What they need to understand
- Questions the listing must answer
- Proof they need
- Friction that could stop conversion
- Listing sections that should address them

Do not invent product capabilities.

Collect three to five direct competitor listings from AWS Marketplace or Microsoft Marketplace, then add one strong adjacent listing from a different but related category. Use Perplexity for category research when you need to understand common marketplace terms, buyer expectations, or how similar offers are positioned. Compare title structure, first-screen clarity, use-case language, proof, screenshots, pricing path, security language, support links, and private-offer clarity. Document what competitors explain well, what they leave vague, and what your listing can credibly make easier for the buyer. This turns competitor research into practical conversion criteria instead of a generic swipe file.

Feed Claude your listing, buyer brief, competitor benchmark, approved proof, and marketplace constraints. Ask it to score headline clarity, category fit, buyer pain, use-case specificity, proof strength, screenshot usefulness, security confidence, deployment clarity, pricing or private-offer clarity, CTA strength, and procurement readiness. Require a severity rating for every issue so the team can separate conversion blockers from polish improvements. For each gap, ask for the buyer question that remains unanswered and the exact listing section where the fix belongs. The audit should produce a prioritized issue log, not a loose list of opinions.

Audit this cloud marketplace listing for conversion and procurement readiness.

Our listing:
{{our_listing}}

Buyer brief:
{{buyer_brief}}

Competitor benchmark:
{{competitor_benchmark}}

Approved proof points:
{{approved_proof_points}}

Marketplace constraints:
{{marketplace_constraints}}

Evaluate:
1. Title and headline clarity
2. Category and search fit
3. Buyer pain and use case clarity
4. Proof and trust
5. Screenshots and visual explanation
6. Security and compliance confidence
7. Deployment and integration clarity
8. Pricing, trial, or private-offer clarity
9. CTA and next-step strength
10. Procurement readiness

For each issue, give severity, buyer question left unanswered, why it matters, and the exact section to fix.

Use Gong snippets, sales notes, partner seller feedback, marketplace inquiries, and late-stage procurement questions to collect the actual phrases buyers use. Focus on questions about deployment, integrations, cloud budgets, committed spend, private offers, security review, migration effort, business case, and time to value. Use Claude to clean the phrases into a voice-of-buyer bank without losing the original wording. Add the strongest phrases to the rewrite brief so the listing sounds like the buying process instead of internal product marketing. If you do not have Gong data, use recent sales notes or partner-channel questions as the minimum viable source.

Extract marketplace buyer language from these calls, notes, and questions.

Source material:
{{buyer_conversation_notes}}

Buyer brief:
{{buyer_brief}}

Product context:
{{product_context}}

Extract phrases and questions related to:
1. Procurement path
2. Cloud budget or committed spend
3. Private offer or contracting
4. Deployment and implementation
5. Security or compliance review
6. Integration requirements
7. ROI or business case
8. Competitive comparison

For each phrase, include the buyer concern, suggested listing section, and whether it is safe for public wording, internal-only, or needs approval.

Use Claude to rewrite the listing title, short description, long description, feature bullets, use-case bullets, deployment notes, screenshot captions, FAQ section, support language, and CTA options. Require every important claim to be tied to an approved proof point or marked for review. Keep the copy direct and marketplace-friendly: buyers should quickly understand who it is for, what problem it solves, how it deploys, what proof supports it, and how procurement moves forward. Do not add integrations, certifications, partner badges, pricing statements, or customer claims unless they are approved. Save the rewrite in Google Docs with comments for product, partner, legal, security, and alliance reviewers.

Rewrite this marketplace listing using the audit, buyer language, and approved proof.

Current listing:
{{current_listing}}

Audit findings:
{{audit_findings}}

Buyer language:
{{buyer_language}}

Approved proof points:
{{approved_proof_points}}

Marketplace constraints:
{{marketplace_constraints}}

Create:
1. Listing title
2. Short description
3. Long description
4. Feature bullets
5. Use case bullets
6. Deployment notes
7. Screenshot captions
8. FAQ section
9. Support or next-step language
10. CTA options
11. Claims that require approval

Rules:
- Do not invent integrations, certifications, pricing, or claims
- Make procurement value clear
- Use plain buyer language
- Keep marketplace constraints in mind

Before publishing, review whether each screenshot supports a buyer question, whether every proof point is current, whether deployment requirements are understandable, and whether the CTA or private-offer path is clear. Route questionable items to product, security, legal, cloud alliance, or marketplace operations before updating the listing. After changes go live, track marketplace views, clicks, contact requests, private-offer requests, partner referrals, sourced opportunities, and sales feedback from marketplace-sourced conversations. Schedule a quarterly audit because marketplace categories, competitor listings, and procurement expectations change. Keep a version note in Google Docs so the team knows what changed and why.