deal-desk-approvallisted

# Deal Desk Approval Design who may approve what on non-standard deals - discounts, custom terms, risky structures - and deliver it as a spec: an approval matrix across five concession levers, a prohibited-terms class, exception intake with SLA clocks and escalation, and precedent control. This skill covers deal-desk approvals only: general business-process approvals (expense, procurement, HR, engineering change) are out of scope - say so and stop when asked for them. Deal-desk thresholds are not standardized: every number in circulation comes from practitioner blogs and consultancies, several from content farms. The skill's core discipline is therefore provenance: label where each threshold comes from, and derive the real ones from the user's own deal data, not from an imported "industry" number. ## Ground Rules - Tag every numeric threshold with its provenance. Never present a vendor heuristic as an industry constant. - Published practitioner source - Single vendor blog (illustrative only) - Derived from the user's own deal data - Never state these circulating numbers as fact. Each is repeated across content without attribution. Omit them, or name them as circulating and unverified: - "75% gross-margin floor" - "1 deal-desk FTE per $40M ARR" - "35% mid-market / 70% enterprise deal-desk hit rates" - Stripe-attributed "4.2x churn at 30%+ discount" - Gartner-attributed "90% of B2B purchases AI-intermediated by 2028" - "The customer asked for it" is not a ju