Community Guidelines

Submitting Prompts

The best prompts on WinDeals.ai come from the field — real scenarios, real objections, real deals. Before you submit, make sure your prompt meets the bar.

A good prompt:

• ✓Is specific to a sales scenario, stage, or persona
• ✓Uses clear variable placeholders like [TITLE], [COMPANY TYPE], [PAIN] so anyone can customize it
• ✓Produces a consistently useful output when run in any major LLM
• ✓Includes enough context that a rep can use it without explanation

Before submitting, ask yourself:

• •Would I use this in a live deal today?
• •Would a new rep understand exactly when and how to use this?
• •Does it contain any proprietary, confidential, or personally identifiable information?

What we don't accept:

• ✕Generic prompts that aren't specific to sales
• ✕Prompts containing real company names, contact details, or internal data
• ✕Duplicate or near-identical submissions to prompts already in the library
• ✕Promotional content or vendor pitches disguised as prompts

All submissions are reviewed before publishing. You'll be notified when your prompt goes live.

Commenting

Comments are where the community makes prompts better. Share what worked, what didn't, and how you've adapted a prompt for your specific context.

Good comments:

• ✓Add context — the industry, deal type, or persona you used it for
• ✓Share a specific result — what the output helped you do
• ✓Suggest improvements with a reason, not just a preference
• ✓Ask questions that help others use the prompt more effectively

Keep it professional:

• ✕No self-promotion, spam, or vendor recommendations
• ✕No sharing of prospect or customer information — even anonymised
• ✕Critique the prompt, not the person who wrote it
• ✕If something is broken or misleading, flag it — don't just downvote

Comments that don't add value will be removed. Repeat violations will result in account suspension.

Customizing Prompts

Every prompt on WinDeals.ai is a starting point. You're encouraged to adapt them to your product, your ICP, and your sales motion.

How to customize effectively:

• ✓Replace variable placeholders with specifics relevant to your context — industry, persona, deal size
• ✓Add a section if your sales process requires it — e.g. a MEDDIC qualification layer or a specific objection you commonly face
• ✓Adjust the tone or output format to match how your team communicates
• ✓Test your customized version in your preferred LLM before saving or sharing

If you're an Enablement Manager or RevOps lead:

• •Use customization to build team-standard versions of high-use prompts
• •Document the variables your team should always fill in before running a prompt
• •Save customized versions to your team library to maintain consistency across reps

What to avoid:

• ✕Removing variable placeholders and hardcoding specific company or contact data
• ✕Over-customizing to the point the prompt loses its reusability
• ✕Saving versions that contain real prospect or customer information

Sharing Prompts

Sharing a prompt — internally or publicly — extends its value beyond your own deals.

Sharing inside your team:

• ✓Use the share link to send a prompt directly to a colleague or paste into your team's Slack, CRM, or enablement platform
• ✓When sharing, add a note on when and how you use it — context makes adoption faster
• ✓Enablement leads can curate collections and share as a set for onboarding or training

Sharing publicly:

• •If a prompt has worked well for you, submit it to the community library so others benefit
• •Credit adaptations — if you've built on someone else's prompt, acknowledge it in your submission notes
• •Don't share prompts that have been customized with internal company information or proprietary methodology without permission

What you should never share:

• ✕Prompts containing real prospect names, company names, or deal details
• ✕Internal pricing, positioning, or competitive intelligence embedded in a prompt
• ✕Prompts built from proprietary frameworks owned by your employer without authorization