Evidence / First process
One process.
A well-founded decision.
Test a real process, measure the quality of the output, and decide on the conditions for moving to production. Your team defines the expected outcome and keeps the decision.
What is delivered
Four deliverables.
Explicit criteria.
The scope is agreed before kickoff. The review covers what your team can actually evaluate.
- 01
Scoping sheet
Process, data, scope, responsibilities, and success criteria agreed before execution.
Your business lead approves the scope and the expected outcome.
- 02
Configured workflow
An agent workflow tailored to the selected process, with its steps and human review points.
The workflow is evaluated on the agreed set of case files.
- 03
Reviewable results
Business deliverables, their available sources, and the control elements provided for in the scope.
Your team can review the output and flag discrepancies.
- 04
Decision review
Results against the criteria, limitations encountered, corrections needed, and conditions for production rollout.
The review ends in a decision: continue, adjust, or stop.
Measure to decide
Value is verified on your own process.
The baseline and the expected thresholds are defined together. Results are assessed on the selected set of case files.
- Processing time
- Compare with the current method on the same set of case files, including human review time.
- Deliverable quality
- Assess expected elements, omissions, and corrections against a business scoring grid defined during scoping.
- Output verification
- Check the available sources, the approval rules, and how discrepancies are handled within the agreed scope.
- Operating conditions
- Identify the access, usage costs, responsibilities, and integrations needed for production.
Who is involved, and when?
- 01
Scope
KOREV + business lead
Define the process, the usable data, and the success criteria.
Milestone: Scope and proposal accepted
- 02
Prepare
KOREV + technical contact
Prepare access, the chosen environment, and the evaluation set.
Milestone: Data and access ready
- 03
Evaluate
KOREV + reference users
Run the workflow, review the results, and log discrepancies.
Milestone: Results checked against the criteria
- 04
Decide
Project owner
Examine the value observed and the conditions for moving to production.
Milestone: Decision to roll out, adjust, or stop
What your team needs to provide
- Business lead
- Describe the process, provide examples, and take part in reviewing the results.
- Technical contact
- Confirm access, data constraints, and deployment conditions.
- Decision-maker
- Approve the scope and budget, then decide on next steps based on the review.
Budget and commitment
On quote after scoping
The proposal separates the delivery of the pilot, any infrastructure or model costs, and the conditions for moving to production.
What determines the budget
- The number of process steps and the degree of agent customization.
- Corpus quality, volumes, and data preparation.
- Integrations and the deployment model: dedicated cloud, hybrid, or on-premises.
- Controls, evaluation criteria, and user support.
A schedule tied to specific milestones
The proposal sets the dates for preparation, evaluation, and delivery of results based on available data, access, and your reference users' availability.
A written scope
The contractual scope specifies the selected deliverables, included integrations, and any additional work. A multi-site deployment, a full regulatory audit, or production rollout is scoped separately.
Prepare the decision with your teamFRBefore you start
Which process do you want to evaluate?
An example case file, the expected outcome, and your main constraints are enough to begin scoping.
Still need to identify your first use case? Start with Pulse.