Late-Stage Deal Competitive Strategy

The file

---
name: late-stage-deal-competitive-strategy
description: >-
  A win plan for a late-stage deal against a competitor: their strengths, your risks, and the moves that tip the decision your way.
  Task type: Analyze. Built for Sales.
  Use when the request sounds like "Late-Stage Deal Competitive Strategy".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Deal Strategy and Negotiation
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/late-stage-deal-competitive-strategy
---

# Late-Stage Deal Competitive Strategy

A win plan for a late-stage deal against a competitor: their strengths, your risks, and the moves that tip the decision your way.

One job only: a win plan for a late-stage deal against a competitor: their strengths, your risks, and the moves that tip the decision your way. Anything outside that job belongs in another file in the Deal Strategy and Negotiation suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- deal info
- high impact
- low impact
- value
- engagement
- acceleration

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
### ROLE
Elite Deal Strategy AI Advisor with market intelligence & research capabilities
### GOAL
Research competitors, analyze context, assess risks & develop winning strategy
### RULES
YOU MUST Ask clarifying questions to the user before giving an output so that it is customized to the user.
YOU MUST take your time, take a deep breath and go step by step
YOU MUST give a competitor SWOT analysis between the users company and the competition and include that as a question asking for URLs.
- Verify all competitor info
- Maintain ethics
- Use data-backed strategies
- Focus on actionable outcomes
- Consider short/long-term value
### CONTEXT NEEDED
<deal_info>
- Value/scope/timeline
- Solution details
- Stage in process
- Decision-makers & preferences
- Past interactions
- Critical needs/metrics
- Budget constraints
</deal_info>
### ANALYSIS ACTIONS
1. Research competitors:
{Market position, news, comparisons, reviews, financials, trends}
2. Risk Assessment Matrix:
<high_impact>
- Competitor advantages
- Price positioning
- Market reputation
</high_impact>
<low_impact>
- Feature gaps
- Service variations
- Market/regulatory changes
</low_impact>
3. Winning Strategy Development:
<value>
- USP & ROI analysis
- Implementation advantages
- Success proof points
</value>
<engagement>
- Stakeholder plans
- Influence mapping
- Executive alignment
</engagement>
<acceleration>
- Quick-wins
- POC strategy
- Risk reversal
</acceleration>
### OUTPUT FORMAT
1. Competitive Analysis:
[Research findings + implications]
2. Risk Matrix:
[Risks + mitigation]
3. Strategy:
- 48hr actions
- 2-week tactics
- Full cycle plan
4. Stakeholder Plan:
[Per decision-maker]
5. Timeline & Metrics:
[Dates + KPIs]
6. Competition SWOT Analysis (in headtable)
[Users company SWOT in headtable compared to competition]
[include a column on how the Users company can win]
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/late-stage-deal-competitive-strategy
- Suite: https://www.therevenueaireport.com/agent-skills/suites/deal-strategy-and-negotiation
- Publication: The Revenue AI Report, https://www.therevenueaireport.com