Requirements gathering on ERP projects gets treated as a business-analyst chore that happens before the interesting work starts. It isn't. It's the phase that determines how many custom modules you end up maintaining for the next six years, and most of the questions that matter are questions only someone who has read the Odoo source would think to ask.
This is the checklist I'd want filled in before I opened an editor. It is deliberately not a list of departments to interview.
1. Map the client's nouns to models before anything else
Every business has five or six words that appear in every sentence they say. "Job." "Load." "Batch." "Run." "Consignment." Write those down on day one and put an Odoo model next to each.
There are three outcomes, and you need to know which one you're in before anyone estimates:
