The document that comes before the URS — and usually gets skipped

The Customer Requirements Document captures what a customer is actually trying to achieve — and what they're willing to pay for — before anyone starts specifying a solution. It comes before the URS or PRD, and it's the step most commonly skipped in the rush toward technical specification. This checklist works through customer discovery conversations systematically: probing the "why" behind stated requirements, documenting exact customer language, and distinguishing who has real budget authority from who's just offering opinions.