OODA Loop

Full Markdown demo

# OODA: 72-Hour Competitor Price Response

## Input Summary
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Classic Case Context
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Skill Used
- OODA Loop
- Move through observe, orient, decide, and act under uncertainty.
- Best for: Competitive response, incidents, sales moves, and fast experiments.
- Can generate: Observations, orientation, action options, and next feedback loop.

## Situation Judgment
A competitor suddenly cut price by 30%, and sales is receiving requests to match.

## Executive Summary
Do not immediately match the price. Use a 72-hour OODA loop to determine whether this is a promotion, repositioning, or a price war, then choose price protection, value packaging, or targeted discounting.

## Framework Analysis
| Stage | Key question | Output |
| --- | --- | --- |
| Observe | Which customers ask for a match? What are the terms? | Deal list, evidence |
| Orient | Do customers care about price, security, or contract risk? | Segment view |
| Decide | Which customers get value packaging vs discount? | Response policy |
| Act | Sales script and five deal tests | 24-hour feedback |

## Reusable Diagram
This is a Markdown-only output. Switch to diagram or PDF-ready output to generate Mermaid.

## Recommendation
Offer a time-limited value package for high-intent renewal accounts, test targeted discounts for price-sensitive smaller accounts, and keep public pricing intact to protect the anchor.

## Risks And Unknowns
- Matching too quickly trains customers to wait for discounts.
- If the competitor also reduced scope, direct price matching misreads the move.

## Next Actions
1. Collect competitor terms and affected deal list within 6 hours.
2. Interview 5 affected opportunities within 24 hours.
3. Publish a sales response playbook within 48 hours.

Full Markdown demo

# OODA: 72-Hour Competitor Price Response

## Input Summary
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Classic Case Context
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Skill Used
- OODA Loop
- Move through observe, orient, decide, and act under uncertainty.
- Best for: Competitive response, incidents, sales moves, and fast experiments.
- Can generate: Observations, orientation, action options, and next feedback loop.

## Situation Judgment
A competitor suddenly cut price by 30%, and sales is receiving requests to match.

## Executive Summary
Do not immediately match the price. Use a 72-hour OODA loop to determine whether this is a promotion, repositioning, or a price war, then choose price protection, value packaging, or targeted discounting.

## Framework Analysis
| Stage | Key question | Output |
| --- | --- | --- |
| Observe | Which customers ask for a match? What are the terms? | Deal list, evidence |
| Orient | Do customers care about price, security, or contract risk? | Segment view |
| Decide | Which customers get value packaging vs discount? | Response policy |
| Act | Sales script and five deal tests | 24-hour feedback |

## Reusable Diagram
```mermaid
timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop
```

## Recommendation
Offer a time-limited value package for high-intent renewal accounts, test targeted discounts for price-sensitive smaller accounts, and keep public pricing intact to protect the anchor.

## Risks And Unknowns
- Matching too quickly trains customers to wait for discounts.
- If the competitor also reduced scope, direct price matching misreads the move.

## Next Actions
1. Collect competitor terms and affected deal list within 6 hours.
2. Interview 5 affected opportunities within 24 hours.
3. Publish a sales response playbook within 48 hours.

Mermaid demo

timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop

Full Markdown demo

# OODA: 72-Hour Competitor Price Response

## Input Summary
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Classic Case Context
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Skill Used
- OODA Loop
- Move through observe, orient, decide, and act under uncertainty.
- Best for: Competitive response, incidents, sales moves, and fast experiments.
- Can generate: Observations, orientation, action options, and next feedback loop.

## Situation Judgment
A competitor suddenly cut price by 30%, and sales is receiving requests to match.

## Executive Summary
Do not immediately match the price. Use a 72-hour OODA loop to determine whether this is a promotion, repositioning, or a price war, then choose price protection, value packaging, or targeted discounting.

## Framework Analysis
| Stage | Key question | Output |
| --- | --- | --- |
| Observe | Which customers ask for a match? What are the terms? | Deal list, evidence |
| Orient | Do customers care about price, security, or contract risk? | Segment view |
| Decide | Which customers get value packaging vs discount? | Response policy |
| Act | Sales script and five deal tests | 24-hour feedback |

## Reusable Diagram
```mermaid
timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop
```

## Recommendation
Offer a time-limited value package for high-intent renewal accounts, test targeted discounts for price-sensitive smaller accounts, and keep public pricing intact to protect the anchor.

## Risks And Unknowns
- Matching too quickly trains customers to wait for discounts.
- If the competitor also reduced scope, direct price matching misreads the move.

## Next Actions
1. Collect competitor terms and affected deal list within 6 hours.
2. Interview 5 affected opportunities within 24 hours.
3. Publish a sales response playbook within 48 hours.

Mermaid demo

timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop

PDF-ready HTML demo

<!doctype html>
<html>
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>OODA: 72-Hour Competitor Price Response</title>
  <style>
    body { font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; margin: 48px; color: #161a1d; line-height: 1.6; background: #fbfcf8; }
    h1 { font-size: 34px; line-height: 1.1; margin: 0 0 18px; }
    h2 { font-size: 20px; margin-top: 28px; }
    pre { white-space: pre-wrap; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 18px; overflow-wrap: anywhere; }
    .meta { color: #2563eb; font-size: 12px; text-transform: uppercase; font-weight: 800; letter-spacing: .08em; }
    .sheet { max-width: 940px; margin: 0 auto; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 32px; }
    @media print { body { margin: 18px; background: #fff; } .sheet { max-width: none; border: 0; padding: 0; } }
  </style>
</head>
<body>
  <main class="sheet">
    <p class="meta">ThinkOps AI PDF-ready output</p>
    <h1>OODA: 72-Hour Competitor Price Response</h1>
    <pre># OODA: 72-Hour Competitor Price Response

## Input Summary
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Classic Case Context
Our main competitor cut enterprise pricing by 30% today, and sales has already received 5 requests to match the price. We do not know whether this is a long-term strategy or a short promotion, and we do not know whether customers care more about price or security compliance. Use the OODA loop to design the next 72 hours of observation, orientation, decision, and action.

## Skill Used
- OODA Loop
- Move through observe, orient, decide, and act under uncertainty.
- Best for: Competitive response, incidents, sales moves, and fast experiments.
- Can generate: Observations, orientation, action options, and next feedback loop.

## Situation Judgment
A competitor suddenly cut price by 30%, and sales is receiving requests to match.

## Executive Summary
Do not immediately match the price. Use a 72-hour OODA loop to determine whether this is a promotion, repositioning, or a price war, then choose price protection, value packaging, or targeted discounting.

## Framework Analysis
| Stage | Key question | Output |
| --- | --- | --- |
| Observe | Which customers ask for a match? What are the terms? | Deal list, evidence |
| Orient | Do customers care about price, security, or contract risk? | Segment view |
| Decide | Which customers get value packaging vs discount? | Response policy |
| Act | Sales script and five deal tests | 24-hour feedback |

## Reusable Diagram
```mermaid
timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop
```

## Recommendation
Offer a time-limited value package for high-intent renewal accounts, test targeted discounts for price-sensitive smaller accounts, and keep public pricing intact to protect the anchor.

## Risks And Unknowns
- Matching too quickly trains customers to wait for discounts.
- If the competitor also reduced scope, direct price matching misreads the move.

## Next Actions
1. Collect competitor terms and affected deal list within 6 hours.
2. Interview 5 affected opportunities within 24 hours.
3. Publish a sales response playbook within 48 hours.
</pre>
    <h2>Mermaid diagram source</h2><pre>timeline
  title 72-hour OODA response
  Hour 0-6 : Observe competitor terms and affected deals
  Hour 6-18 : Orient by customer segment and buying trigger
  Hour 18-30 : Decide response policy and discount boundaries
  Hour 30-48 : Act with sales scripts and five deal tests
  Hour 48-72 : Review win/loss signals and start next loop</pre>
  </main>
</body>
</html>