Sales & Revenue Prompts to Build or Create Something

You are a customer success operations manager designing a customer health scoring model. Business context: [DESCRIBE: Product type (SaaS/platform/services), key usage signals available, customer data available in CRM (support tickets/NPS/usage logs/contract data), team size for CS coverage] Design the health score model: 1. Metric selection — 4–6 measurable signals that predict retention and growth (usage frequency / feature adoption / support ticket volume / NPS / stakeholder engagement / contract utilization) 2. Weighting — assign weight to each metric based on predictive value for churn (usage typically 40–50% of score) 3. Scoring scale — define what Green/Yellow/Red means for each metric and overall 4. Update frequency — how often does the score refresh? (real-time / daily / weekly) 5. Action triggers — what score or score change triggers a CS action? What is that action? Output: Health score design document. Metric definitions. Weighting table. Green/Yellow/Red thresholds. Action trigger rules.

You are a customer success manager building an expansion revenue playbook. Business context: [DESCRIBE: Product/platform, expansion types available (seats/modules/usage/services), typical expansion triggers, current expansion process (defined or ad hoc), who owns expansion (CS/sales/both)] Build the playbook: 1. Expansion triggers — specific customer signals that indicate readiness: usage hitting limits / new team onboarded / new use case discussed / renewal with growth 2. Expansion qualification — criteria for a genuine expansion opportunity vs. a wish 3. Conversation approach — how to raise expansion in the context of customer value, not our quota 4. Handoff decision — at what point does CS own the expansion vs. hand to sales? 5. Objection handling — top 3 expansion objections and how to address them Output: Expansion playbook. Trigger list. Qualification criteria. Conversation guide. Handoff rules.

You are a customer success operations manager designing lifecycle communications. Context: [DESCRIBE: Product type, customer segments, key lifecycle moments (onboarding / first value / adoption milestone / renewal / expansion), current automated communications in place, any gaps in coverage] Design the lifecycle communication plan: 1. Onboarding sequence (Days 1–30): welcome / setup completion nudge / first-use guidance / check-in 2. Adoption phase (Days 31–90): feature discovery / best practice tips / peer benchmark / 60-day check-in 3. Value realization (Day 90): value summary / ROI snapshot / request for feedback 4. Ongoing engagement: monthly product updates / quarterly business review invitation / renewal prep 5. Expansion triggers: usage-limit notifications / new feature relevant to their use case / peer success story For each communication: channel (email/in-app/call) / owner (automated/CSM/exec) / goal. Output: Lifecycle communication map. Owner and channel per touchpoint. Gaps in current coverage. Recommended additions.

You are a sales operations manager documenting CRM configuration requirements for an implementation or redesign. Business context: [DESCRIBE: Company stage, sales motion (inbound/outbound/PLG), deal types, team size, key processes to support (lead management/pipeline/forecasting/customer success), integration requirements] Document requirements across: 1. Sales process — stages, entry/exit criteria, required fields per stage, opportunity types 2. Lead management — lead sources, routing rules, MQL definition, lead-to-opportunity conversion 3. Account hierarchy — parent/child accounts, territory assignment, account ownership rules 4. Reporting needs — dashboards and reports leadership needs; data they must capture to produce them 5. Integration requirements — systems CRM must connect to (marketing automation / ERP / support / billing) Output: CRM requirements document. Organized by object and process. Ready for CRM admin or implementation partner to configure against.

You are a product marketing manager creating a competitive battle card for a key competitor. Competitive data: [DESCRIBE: Competitor name, their target market and positioning, their key features and strengths, known weaknesses, typical deal sizes, how they sell (direct/partner/PLG), typical objections they raise about us, our key differentiation] Build the battle card: 1. Competitor overview — who they are, who they target, how they position (1 paragraph) 2. Where they beat us — honest assessment; don't dismiss what customers see value in 3. Where we beat them — our genuine advantages for the specific use case 4. Traps to set — questions to ask that highlight competitor weaknesses without naming them 5. Objection responses — their top attacks on us and how to respond credibly 6. Proof points — customer stories or data points specific to competitive wins against this vendor Output: Battle card. One page. Designed for a rep to read in 5 minutes before a competitive call.

You are a channel manager building a joint business plan with a strategic partner. Context: [DESCRIBE: Partner name, their market, their customer base, your joint target market, current state of the relationship (new/established), any prior joint revenue, planned joint activities] Build the business plan: 1. Revenue targets — joint pipeline and ARR targets for the next 12 months; broken down by quarter 2. Target market — specific customer segments, geographies, or industries to pursue jointly 3. Go-to-market activities — co-marketing, joint events, referral motions, solution bundling 4. Enablement commitments — training, certifications, sales support we will provide 5. Success metrics — how we will measure and review the partnership quarterly Output: Joint business plan document. Revenue targets. Quarterly review cadence. Mutual commitments from both sides.

You are a VP of Channel building a conflict resolution protocol for channel conflicts. Context: [DESCRIBE: Types of channel conflicts you experience (partner vs. direct / partner vs. partner / geographic overlap), current lack of process or inconsistency, impact on partner relationships] Build the protocol: 1. Conflict types — define each conflict type and the policy for each 2. Deal registration protection — registered deals get partner protection for [X days] if actively progressing 3. Direct sales rules of engagement — criteria under which direct sales can engage an account a partner is working 4. Escalation process — how a conflict is raised, who decides, timeline for decision 5. Documentation — all conflict resolutions logged; reviewed quarterly for pattern and fairness Output: Channel conflict resolution protocol. Clear rules for each conflict type. Escalation flowchart. Review cadence.

You are a head of channel partnerships building the brief for recruiting a new partner type. Context: [DESCRIBE: Gap in current channel (geography/vertical/capability), ideal partner profile, what you can offer partners (margin/leads/support/technology), competitive partner programs in your market] Build the recruitment brief: 1. Ideal partner profile — size, market focus, existing customer relationships, technical capability 2. Value proposition for partners — why should they partner with us vs. a competitor or no-one? 3. Program terms — margin structure, deal registration, marketing development funds, support model 4. Qualification criteria — what must a partner demonstrate before being accepted? 5. Recruitment approach — where to find these partners; outreach strategy Output: Partner recruitment brief. ICP for partners. Value proposition. Program summary. Recruitment outreach template.

Define clear pipeline stages that align with buyer journey and sales process. [PASTE: Your sales pipeline stage definition requirements and goals here] Provides: Strategic framework, actionable recommendations, and measurement approach for sales pipeline stage definition.

Our proposals take too long and don't win enough. Create a proposal process that improves speed and quality. Include: (1) Proposal intake – when to start? What do we need? (2) Proposal team & roles – who's accountable? Review cycle? (3) Proposal structure & templates – standard sections? Company overview? Approach? (4) Quality standards – consistency, quality, proofreading? (5) Timeline & phases – how long should proposals take? (6) Post-submission – oral presentations? Follow-up? Lessons learned? Include proposal template and process timeline. Make efficiency clear.

We received an RFP from [PASTE: potential client]] for [PASTE: scope]]. Build an RFP response and capture strategy. Include: (1) Kick-off & discovery – do we understand what they need? (2) Proposal strategy – what's our competitive advantage? (3) Proposal team – who's core team? Decision maker? (4) Approach development – how will we solve their problem? (5) Pricing strategy – what are we proposing to price? (6) Oral presentation prep – what will we emphasize? Include proposal outline and presentation prep checklist. Make response strategic.

We want to build partnerships with complementary service providers to expand offerings and reach. Create a partnership strategy. Include: (1) Partner profile – what type of partners? Complementary services? (2) Partnership models – referral only? Co-selling? Joint delivery? (3) Candidate identification – who are potential partners? (4) Value proposition – what's in it for them? (5) Commercial structure – how do you split revenue? (6) Relationship management – how do you nurture partnerships? Include partnership evaluation framework and commercial terms template. Make partnerships strategic.

Create 5-email sequence targeting [PASTE: buyer title + company size]. Each email: 50-70 words. 1) Attention hook (industry insight). 2) Problem statement. 3) Social proof. 4) Clear CTA. 5) Final breakup email. Include subject line variations. Format: JSON array with subject, body, send-day timing.

Design LinkedIn strategy for [PASTE: target persona + company]. Steps: 1) Craft 3 connection request variations (value-first messaging). 2) Build 30-day nurture cadence. 3) Map content share strategy. 4) Define engagement triggers. 5) Create conversation starters. Output: week-by-week playbook with metrics (connection rate, engagement %).

[PASTE: industry vertical]. Steps: 1) List top 5 industry pain points. 2) Research competitor presence. 3) Identify regulatory/compliance angles. 4) Build 2-minute elevator pitch. 5) Create vertical-specific social proof template. Output: one-page pitch with 3 case study hooks.

Create outreach plan for [PASTE: conference/webinar name + attendee list source]. Steps: 1) Pre-event: identify attendees, build custom value prop. 2) During: live engagement triggers. 3) Post-event: 48-hour follow-up sequence. 4) Nurture cadence. 5) ROI tracking. Output: campaign calendar with email/message templates.

[PASTE: lost deal info + competitor name]. Steps: 1) Identify why they chose competitor. 2) Highlight recent product improvements. 3) Build 3-part win-back sequence. 4) Create ROI comparison. 5) Offer limited-time incentive. Output: 60-day win-back playbook.

Build referral system from [PASTE: existing customers + employee network]. Steps: 1) Design incentive structure. 2) Create referral request template. 3) Build referral tracking process. 4) Develop thank-you workflow. 5) Establish success metrics. Output: 90-day referral roadmap with conversion targets.