Dealership software RFP builder
Build a consistent requirements, demo and contract checklist before vendors shape the decision.
What this builder produces
A category-specific requirements and contract checklist that every provider answers in the same format. It does not score vendors or recommend one — it removes the variation that makes proposals impossible to compare.
Selections stay in your browser on this device. Nothing is transmitted, and no sign-in is required.
Make every vendor answer the same questions.
Select a category, then build a consistent discovery and contract checklist. Your selections stay on this device.
Why proposals are usually not comparable
Three providers asked the same question in three different ways will return three documents with different scopes, different assumptions about quantity and implementation, and different things silently excluded. The differences between the proposals then describe the questions rather than the products. Asking every provider for the same items, in the same order, in the same units is what turns three sales documents into one comparison — and it is the cheapest control available, because it costs nothing but sequence.
What the checklist deliberately does not do
It does not score, weight or rank providers, and it does not decide which requirements matter more — that judgement belongs to the dealership, and a tool that made it for you would be substituting its priorities for yours. It also cannot verify an answer: a provider can complete every line and still be wrong, which is why the checklist asks for answers in writing and the demo script tests them.
Nothing here is transmitted, stored or seen
Your selections stay in this browser on this device. There is no account, no form submission and no server-side record of what you chose — this directory has no database and collects nothing about the people who read it. That is a deliberate design choice rather than a feature: a tool that quietly turned a procurement plan into a sales lead would be worth less than no tool. Clearing this browser’s storage clears the work, so export or copy anything you want to keep.
Bring the completed checklist into the contract
The most common loss in a software purchase is between selection and signature: capabilities demonstrated in an evaluation do not appear on the order form, and the order form is the document that governs. Attach the completed checklist to the agreement, or restate the material answers as terms. A provider that will confirm something in a meeting and not in a contract has told you which answer was real.
Send the same list to every provider
1. Send the completed checklist to every candidate before the first demo, so they arrive prepared to demonstrate rather than present.
2. Require the commercial answers in a fixed format — modules, quantities, implementation, integration, usage, term, renewal mechanic, increase cap and exit cost — or the proposals will not be comparable.
3. Score during each demo, not afterwards. Recollection favours the most recent presenter.
4. Keep the completed checklist. It is the record of what was promised during selection.
It does not rank providers, score vendors, infer compatibility with your systems, or establish price. It organises your own requirements so that the answers you collect are comparable.