- The current price list file
- The rules are built on your real prices, so the file must be the one the team quotes from today. A messy file is fine if one person can say which column is live. Without it, we build on guesses and the test quotes will not match.
- Quotes the team found hard
- Pick a handful of past quotes that took long to assemble or came back with errors. They become the test set the build is checked against. If none are available, the rules are written from memory and the first live quotes carry the risk.
- One owner of discount limits
- Someone with authority must decide what each role may offer and what needs a second signature. We record and build those limits but do not set them. Without a named owner, the approval matrix stays blank and every exception stops at your desk.
- Access to the CRM and order entry
- The quote must connect to the systems that hold the customer and the order. Read access to see the fields is enough to start, and a test area is better. Without it, the connection map stays on paper and the quote is re-typed by hand.
- A decision on spreadsheet or tool
- Whether to build in a spreadsheet or a CPQ tool depends on budget and who will maintain it. You need to say which cost and upkeep you can accept. If undecided, the build waits at the route decision step.