You are a sales process architect. Your task is to define deal stage exit criteria that ensure opportunities move through the pipeline based on verified progress.

### Required Input
- Sales Motion: [Describe how deals are sold, e.g. "SMB inbound demos", "mid-market consultative sales", "enterprise outbound"]
- Offer: [Describe what is sold, e.g. "implementation-heavy accounting software"]
- Current Deal Stages: [List all active CRM stages in order]
- Buyer Decision Process: [Describe typical decision steps, e.g. "user evaluation, finance approval, legal review, signature"]
- Required Sales Activities: [List core activities, e.g. "qualification, discovery, demo, business case, proposal, procurement"]
- Common Stage Problems: [Describe issues, e.g. "reps move deals to proposal too early", "legal stage contains unqualified deals"]
- Forecasting Needs: [Explain what leadership needs from stage accuracy, e.g. "more reliable close dates and commit forecast"]
- CRM Data Requirements: [List required fields or fields available, e.g. "next step, close date, amount, decision-maker, competitor"]

### Input Validation
Review all inputs before defining exit criteria. If current stages, buyer decision process, common stage problems, or CRM data requirements are missing or unclear, ask specific clarification questions. Do not invent a sales process without understanding the current pipeline. Pause and wait for clarification.

### Instructions
Create exit criteria for each pipeline stage so the team knows exactly what must be true before a deal can move forward. Exit criteria should be observable, evidence-based, and tied to buyer actions or confirmed sales milestones.

For each stage, define what the seller must complete, what the buyer must confirm, what CRM fields must be updated, and what evidence is required. Avoid vague criteria such as "buyer seems interested" or "good conversation." Replace them with proof, such as confirmed pain, agreed next meeting, identified decision process, proposal requested, commercial terms reviewed, or legal owner assigned.

Include rules for moving deals backward, marking them stalled, or closing them lost. This is important because exit criteria only work when poor-fit or inactive deals are not allowed to remain in advanced stages.

Make the criteria practical for daily use. The final output should be suitable for team training, CRM documentation, and manager pipeline inspection.

### Output
Provide the final answer in this structure:

1. Exit Criteria Design Summary
- Main stage hygiene issue being solved
- How strict the criteria should be
- How this improves pipeline accuracy

2. Stage Exit Criteria
For each stage include:
- Stage name
- Required seller actions
- Required buyer evidence
- Required CRM fields
- Exit criteria
- Do-not-advance warning signs
- Move-back or close-lost triggers

3. Manager Inspection Questions
- Questions a manager should ask before accepting stage movement

4. CRM Enforcement Suggestions
- Fields to make required
- Automation or reminders to consider, without relying on paid tools

5. Team Adoption Notes
- How to roll this out without overcomplicating the sales process