Decision owner
Process Excellence, Transformation, Operations, or Compliance owns the business outcome.
For Process Excellence, Enterprise Architecture, Compliance, IT, and Procurement teams with an active shortlist. Set the rules before the demos, score every supplier on the same evidence, and keep the decision trail.
Use this after you have a shortlist and a credible pilot process. Earlier in the buying journey, start with the buyer guide. Existing Geist users should use product documentation and support.
Process Excellence, Transformation, Operations, or Compliance owns the business outcome.
Enterprise Architecture, IT, Data, and Security test integration, access, operation, and exit.
Procurement and Legal validate evidence, contract assumptions, risk, and total cost.
Consultants may facilitate the process, but the buyer owns criteria, weights, and the final record.
A defensible comparison starts with your use case and ends with recorded evidence. Do not change criteria or weights because one demo looked impressive.
Name the process, owner, source material, operating constraints, and decision date.
Separate non-negotiable controls from preferences that can be scored and traded off.
Give every supplier the same scenario, inputs, questions, timebox, and scoring scale.
Keep scores, evidence, failed gates, assumptions, and the reason for the final choice.
Your entries stay in this browser. Compare up to three suppliers, export the full record as CSV, or print a decision copy.
Every supplier gets the same scenario. One bounded process keeps the comparison honest.
Compare up to three suppliers side by side. If Geist is on your list, score it under the same rules.
Names appear in the report exactly as entered.
Set how much each area counts. The weights are calculated for you and always total 100%.
A failed gate rules a supplier out, whatever its score. Mark each gate once you have evidence.
Only a gate marked Fail rules a supplier out. Unchecked gates keep the result open.
Rate the evidence, not the pitch. Add a short note where a reviewer would ask why.
Can the platform represent the work you actually need to govern?
Model the pilot process, its critical variants, exceptions, handoffs, and escalation paths.
Show owners, approvers, controls, risks, and review cadence in the process context.
Change the model, route it for review, and show the retained version and decision history.
Can your real source material enter the platform with its meaning and provenance intact?
Use the pilot documents, files, system exports, or event data rather than a prepared vendor dataset.
Show what the platform rejects, flags, or asks a human to resolve when input is incomplete.
Trace an output to its source and show how access follows roles, organisations, and data boundaries.
Can teams edit, exchange, and leave with usable process models?
Edit the discovered or imported model without rebuilding it in a separate tool.
Import and export representative BPMN 2.0, then compare semantics, layout, labels, and extensions.
Export a model and decision pack that remain useful without a continuing vendor session.
Does the platform explain findings under conditions close to your deployment?
Compare actual variants with the intended process and identify the evidence behind a finding.
Show a weak or ambiguous result and explain confidence, missing evidence, and safe failure.
Show how new data, model changes, incidents, and drift alter findings after the pilot.
Are authority, human review, and the audit trail explicit?
Distinguish read, draft, propose, approve, execute, block, and roll back for the pilot use case.
Show who can intervene, reject, correct, or stop an AI-assisted action and what context they receive.
Trace source, model version, actor, recommendation, approval, action, outcome, and correction.
Can a bounded pilot become an operable service without trapping the buyer?
Name the first process, owner, source, success measure, timeline, responsibilities, and exit criteria.
Show administration, support, change management, training, service levels, and incident handling.
Record implementation and operating costs, contract assumptions, export, deletion, and offboarding.
Ranked by weighted score, with failed gates and open items called out.
Share of the maximum evidence score in each area. Further right is stronger.
An A4 record with the ranking, both charts, the gates, every score and these next steps.
Your browser’s print window opens. Pick “Save as PDF” as the printer.
The structure follows public procurement, software assurance, AI risk, and BPMN guidance. Adapt it to your organisation and applicable law; it is not legal or procurement advice.
Set distinct criteria and weights with the people who will use and govern the service.
Treat non-negotiable supplier and software controls separately from tradeable quality scores.
Evaluate AI behavior, limits, oversight, and monitoring under conditions close to the intended use.
Test BPMN exchange against the published specification, including machine-readable structures.
The Geist team can prepare the evidence request and facilitate a workshop on one of your processes. If Geist is on the shortlist, it is scored under the same rules. You keep the evaluation file and the decision.