A complete, consistent requirements list is what makes offers comparable in the first place. This tool gets you there, without a selection consultant and without a months-long pre-project.
Hardly anyone chooses an ERP more than one to three times in an entire career. Which is exactly why the start is so hard: what do we actually need, in what depth, and how will we measure the vendors' offers in the end? Get that wrong and you end up comparing apples with oranges, and you notice only once it gets expensive.
Until now there were two ways. Hire a selection consultant, or spend weeks pulling a requirements document together in-house. Both cost time and money, and both tie up exactly the people who keep the business running.
This tool takes a third way. You work out your requirements in a structured way, in dialogue with an AI assistant such as Claude, ChatGPT, Copilot or Gemini. The dialogue follows your company: you give it your website and sample documents like invoices or delivery notes, and it asks precisely where your business is distinctive.
Do you even need a requirements document?
Yes, but only as the result of a clean process survey, not as a feature wish list collected from every department. There are two kinds of requirements documents. One is a collection of feature wishes, often hundreds of lines. The other is the condensed description of how your core processes run and what a system has to carry of them. Only the second helps with the selection.
The feature wish list fakes thoroughness. It rewards the system with the most ticks, not the one with the best fit for your real work, and vendors predictably tick almost everything. A process description of your five or six value-adding workflows, by contrast, fits on a few pages. Length is not a mark of quality but rather a warning sign: it shows that nobody has condensed, weighted and prioritised.
Before a single requirement is written down, three questions belong on the table: which processes make you special, and where does your complexity arise? Which workflows have merely grown historically? What sets you apart from the competition, and what can the standard do anyway? The test after completion is: can a vendor derive from it where our project will get difficult? If not, the document describes wishes and not reality. Exactly this process survey is the core of the tool below.
What you end up with
A complete, consistent and comparable requirements list. It describes what your business needs, not which system delivers it. Instead of a silent Excel checklist, a thinking dialogue guides you, checks for gaps and contradictions, and is easier to use than any template. The result lives in your own environment. You keep writing it and weave in requirements that surface later.
How we get you there
It starts with a short exchange in which you describe your situation in a few sentences. From us you get the structured process list as a basis for completeness and a ready-made prompt proposal. Share a few documents from your business and we build your specifics straight into the prompt. The rest you do at your own pace, without chains of appointments with outside parties.
Download for free now
Fill in the short form and the process list and prompt proposal are ready for you right away. We will also send you the links by email.
Thank you. Your files are ready.
We have also emailed you the links.
