You are going to be shown a good demo. The draft will be excellent, the interface will be clean, and the person running it will know exactly which example to use. None of that is dishonest, and none of it tells you what you need to know.
These are the nine questions we would ask, in the order we would ask them. They are the same questions we had to answer when we built the desk, and several of them have answers that are inconvenient for us too.
About what it reads
- What did it read before it wrote this? The whole deal, or the message on screen. If the answer is the message, everything downstream is a guess dressed as an answer.
- What happens to a scanned PDF? If it is stored rather than parsed, the requirements inside it do not exist for the system, and the record only looks complete.
- When an amendment arrives, what changes? A notification is not capture. Ask whether the requirement lines update, whether affected quotes are re-checked, and whether the enforced deadline moves.
About what it claims
- Show me a compliance claim with its evidence. You want the supplier's exact words next to the requirement line. If you are shown a summary, the claim cannot be checked by anyone who was not there.
- How do you distinguish not compliant from not mentioned? These are opposite situations. A system that renders both as a gap, or worse as compliant, is hiding the risk you most need to see.
- What is your score a score of? If a number appears anywhere in the interface, ask what it measures and what it gates. A number with no threshold and no consequence is decoration.
About what it sends
- Where is the approval rule implemented? If someone calls the API directly, does it still apply. If the answer is a property of the web application, it is a rendering decision rather than a control.
- Which safety rules can an administrator switch off? The revealing answer is all of them. That means there are no guarantees, only defaults, and defaults are what a busy quarter changes.
- What does it do the day after a deadline? Ask what the code does, not what should happen. Every path that can produce a send has to know the tender closed.
The pattern in the answers
You are listening for whether the answer is architectural or cosmetic. Cosmetic answers describe what the user sees. Architectural answers describe where a decision is made and what happens when the interface is not involved.
The second kind is harder to give and much harder to fake, because it commits the vendor to something specific about how the system is built.
| You hear | It probably means |
|---|---|
| The user is always in control | Someone can click approve. Nothing is enforced. |
| It is fully configurable | There are no guarantees, only defaults. |
| The AI has 95 percent accuracy | A number from a benchmark that is not your tenders. |
| Below the threshold it will not send, on any path | A claim you can test, and one they cannot walk back. |
The last row is what a real answer sounds like.
And one question for yourselves
Before any of the nine: what do you currently lose, and to what. If nobody can say, the honest first step is not buying software. It is finding out whether your losses are coming from price, from compliance gaps, from threads that went quiet, or from bids you never submitted.
Those have entirely different fixes, and only some of them are a tooling problem. A vendor who does not ask you this before quoting you is selling, not solving.
Where we land
We built Celestix AI to answer those nine in the architectural way, because the alternative was a system nobody senior would sign off on. Drafts written from the complete record. Verbatim proof against every requirement line. A grade that gates sending, enforced where the sending happens. Quotes and proposals that wait for a person, and a submission path that asks for your password because it cannot be recalled.
That is also why we will not claim it runs without you. It runs the correspondence, which is most of the volume and almost none of the judgement, and it brings you the decisions with the evidence attached.