Answer the method question without saying “I’ll check”.
The technical evaluation decides the deal. The buyer goes deep, and the answer comes from your own docs, not a guess.
The evaluation call is a viva. What they asked last time, and what you promised.
Where the last call ended
The method, the format, the limit they pushed on.
What you said you would send
The paper, the benchmark, the sample dataset.
What to get to
What has to be covered before they run their own test.
The person who decides is rarely the person testing. The scientist, the lab lead, IT and procurement.
Who runs the evaluation
The bench scientist who will actually try it.
Who signs it off
The lab or department lead, and whether they have been on a call.
Who blocks it
IT and procurement, and what they have asked before.
The technical promises, written down. So nothing is answered twice.
What you promised
Every file, figure and follow-up, with who owes it.
What they asked that went unanswered
Listed, so it is on the next agenda.
Carried into the next call
The open question comes back with the call it came from.
What it reads, in scientific software
What reps ask before the technical evaluation.
Can it answer a deep method question?
It answers from your own docs and earlier calls, and names the source. If your material does not cover it, it stays quiet.
Do I have to read the answer out?
No. It shows what to cover, and you say it your own way.
Does it work on a technical call with several people?
Yes. It listens on your computer and shows only on your screen.
What happens to what we promised?
It is written into the note with an owner and a date.