Guide
You don't need a requirements document. A short list makes the first conversation far more useful.
Bring the systems you use today and what frustrates you about each, the two or three things that must improve, your locations, entities and countries, and who will make decisions on your side.
If you can, bring one real example of something that went wrong recently: a late order, a stock mistake, a month end that overran. Real examples tell us more than any feature list.
Sound familiar? Tell Brad about your business, and we'll start from what you've just read.