Partner Guidance

Proof of Value

A proof of value is the safest way for a customer to see whether a Greentic-powered digital worker can improve a real business process. Instead of trying to automate everything at once, the partner and customer choose one journey, test it with realistic examples and agree what success should look like.

The goal is not to build a full production system immediately. The goal is to prove whether the journey is useful, controlled and valuable enough to take further.

Definition

What is a proof of value?

A Greentic proof of value is a focused engagement that shows how one manual or confusing process could become a guided digital worker journey.

Would this improve the user experience?

Would it reduce repetitive work?

Would it collect better information?

Would it improve handover to people?

Would the business trust the level of AI control?

Is this worth developing into a pilot or deployment?

A proof of value should create confidence, not complexity.

Timing

When to propose a proof of value

After a strong demo

The customer understands the idea and wants to see how it could apply to their own process.

When the customer has a clear pain

There is a repeated process where users get stuck, information is missing or staff waste time chasing details.

When AI interest is high but trust is low

The customer is interested in AI, but needs evidence that it can be controlled inside business operations.

When integration is not ready yet

The customer may not be ready for full system integration, but can still validate the journey using realistic sample data.

When stakeholders need evidence

A proof of value gives business leaders something concrete to review before approving a wider project.

When the partner sees repeatable potential

The first process could become a reusable solution for other departments, customers or industries.

Scope

What makes a good scope?

A good proof-of-value scope has:

One business process
One main user journey
One primary user group
A clear business owner
Realistic sample scenarios
Clear success criteria
A visible before-and-after comparison
At least one point where the business remains in control
At least one human handover or escalation example
A clear recommendation at the end

If the proof of value needs every system, every exception and every user group included from day one, the scope is too broad.

Boundaries

What to include — and what to leave out

Include

•One focused process
•Realistic sample data
•A clear guided user journey
•Key questions and choices
•A business control or approval moment
•A human escalation or handover example
•Basic success measures
•Stakeholder feedback
•Recommendation for next steps

Leave out for now

•Every process variation
•Every production integration
•Full enterprise rollout
•Complex exception handling
•Replacing all human judgement
•Large-scale data migration
•Advanced reporting
•Long implementation scope
•Anything that distracts from proving the first journey

The proof of value should be strong enough to prove the direction, but small enough to complete without becoming a full transformation project.

Delivery

Proof-of-value delivery flow

Select → Scope → Design → Build Demo → Validate → Report → Decide

Select

Choose the process that has the right mix of pain, visibility and achievability.

Activities

•Identify candidate processes
•Score them against business pain and demo clarity
•Pick one journey
•Confirm the business owner

Output

Selected proof-of-value use case.

Scope

Agree exactly what will be shown, tested and measured.

Activities

•Define included user journey
•Define excluded areas
•Agree sample scenarios
•Agree success criteria
•Confirm stakeholder review group

Output

Clear proof-of-value scope.

Design

Design the improved guided journey.

Activities

•Map the current manual journey
•Identify where users get stuck
•Define questions, choices and summaries
•Define approval or control points
•Define human handover

Output

Target guided digital worker journey.

Build demo

Create the proof-of-value experience using realistic examples.

Activities

•Build the guided journey
•Add realistic sample data
•Prepare before-and-after story
•Prepare presenter notes
•Prepare test scenarios

Output

Working proof-of-value demonstration.

Validate

Test the journey with stakeholders and realistic examples.

Activities

•Run selected scenarios
•Capture feedback
•Check whether the journey is clearer
•Check whether information collection improves
•Check whether handover is useful
•Review AI control and business confidence

Output

Validated findings and improvement points.

Report

Summarise what was proven and what remains to be decided.

Activities

•Document outcomes
•Compare against success criteria
•Capture stakeholder feedback
•Highlight risks and assumptions
•Recommend next steps

Output

Proof-of-value summary report.

Decide

Agree whether to progress to pilot, deployment, wider discovery or no further action.

Activities

•Review business value
•Confirm production requirements
•Agree next scope
•Identify expansion opportunities
•Decide commercial next step

Output

Customer decision and next-step plan.

Measurement

Example success criteria

Success criteria should be agreed before the proof of value starts. They should focus on business improvement, not just whether the demo works.

User experience

Can the user understand what to do next more easily than in the current process?

Example measure

Stakeholder review confirms the guided journey is clearer than the current approach.

Information quality

Does the digital worker collect the right information before work is handed to a person or team?

Example measure

Test scenarios show fewer missing details compared with the current process.

Manual effort

Does the journey reduce repetitive questions, chasing or handovers?

Example measure

Stakeholders identify specific manual steps that could be reduced or removed.

Control and trust

Does the business feel comfortable with where AI is used and where human control remains?

Example measure

Business owner approves the control, approval and escalation points.

Handover quality

When escalation happens, does the person receive useful context?

Example measure

Reviewers confirm the summary and collected information would help them act faster.

Expansion potential

Could the same approach be reused for other processes or departments?

Example measure

Stakeholders identify at least two related journeys that could be explored next.

Inputs

What the customer needs to provide

A proof of value can often start with anonymised, simplified or realistic sample data. The customer does not need to provide full production access at the beginning.

Example requests
Example emails or tickets
Example forms
Example approval scenarios
Example invoices or documents
Common FAQs or policies
Current process description
Current pain points
Escalation rules
Approval rules
Example successful and failed journeys
Stakeholders for review

Use anonymised or synthetic examples where needed. The important thing is that the scenarios feel realistic to the business.

Packages

Example proof-of-value packages

Customer Service PoV

Improve one support journey from customer request to resolution or escalation.

Example scenarios

•Delivery issue
•Billing question
•Product fault
•Account change
•Complaint intake

What to prove

•Better issue identification
•Better information collection
•Better escalation summary
•Faster route to next step

HR Onboarding PoV

Guide a new employee or manager through a common onboarding journey.

Example scenarios

•First-week checklist
•Equipment request
•Policy questions
•Missing documents
•Manager onboarding tasks

What to prove

•Less repetitive HR admin
•Clearer employee journey
•Better task completion
•Better escalation to HR

IT Helpdesk PoV

Improve ticket quality and routing for common IT requests.

Example scenarios

•Password problem
•Laptop issue
•Software access request
•Connectivity issue
•New starter IT setup

What to prove

•Better diagnostics
•Fewer missing details
•Faster routing
•Better handover to IT

Invoice Approval PoV

Support invoice review, exception handling and approval preparation.

Example scenarios

•Matching invoice
•Missing purchase order
•Amount mismatch
•Duplicate invoice risk
•Approval request

What to prove

•Clearer approval context
•Faster manager review
•Better exception handling
•Reduced email chasing

Policy or Knowledge Assistant PoV

Help users find and apply internal knowledge in a guided way.

Example scenarios

•HR policy question
•IT process question
•Finance expense question
•Compliance requirement
•Internal procedure

What to prove

•Faster answers
•Better next-step guidance
•Reduced repetitive questions
•Clear escalation for uncertainty

Template

Proof-of-value template

A copy-friendly structure you can adapt for any customer engagement.

Title

[Process name] Digital Worker Proof of Value

Objective

To test whether a guided digital worker can improve [business process] by helping [target users] complete [journey] more easily, with better information collection, clearer handover and appropriate business control.

Scope — included

• [User journey] • [Target user group] • [Sample scenarios] • [Guided experience] • [Control or approval point] • [Escalation or handover example]

Scope — excluded

• [Full production integration] • [All process variations] • [Full rollout] • [Advanced reporting] • [Anything outside the first journey]

Customer inputs

• [Sample requests] • [Process description] • [Example documents] • [Approval or escalation rules] • [Stakeholder reviewers]

Success criteria

• [User journey is clearer] • [Information collected is more complete] • [Manual chasing is reduced] • [Handover is more useful] • [Business control is acceptable] • [Next-step decision can be made]

Deliverables

• Guided digital worker proof-of-value demo • Sample scenarios • Stakeholder review session • Findings summary • Recommendations for pilot or deployment • Suggested next-step scope

Timeline

A proof of value is typically scoped as a focused short engagement. The exact timeline depends on customer availability, sample data, review cycles and complexity.

Decision after PoV

Progress to pilot

Progress to production planning

Expand discovery

Test another process

Pause because value was not strong enough

Report

Final report structure

At the end of the proof of value, partners should give the customer a clear summary that supports a decision.

Executive summary

What was tested and what was learned?

Process reviewed

What current process or journey was selected?

Current pain points

What manual effort, delay, missing information or handover issues exist today?

Digital worker journey

How did the proof of value improve the journey?

Success criteria review

What criteria were met, partly met or not met?

Stakeholder feedback

What did business users, managers or reviewers say?

Risks and assumptions

What needs to be checked before pilot or deployment?

Recommended next step

What should the customer do next?

Expansion opportunities

What similar journeys could be improved later?

Pitfalls

What to avoid

Avoid vague scope

Everyone should know what is included and what is excluded.

Avoid trying to prove everything

The proof of value should prove one journey well, not ten journeys badly.

Avoid unrealistic data

Sample data should still feel recognisable to the customer.

Avoid hiding human control

Show where a person approves, reviews or takes over.

Avoid overpromising AI autonomy

Do not imply that AI will run business-critical work without boundaries.

Avoid measuring only technical completion

A working demo is not enough. The question is whether it creates business confidence.

Avoid ending without a decision

The proof of value should lead to a clear recommendation and next step.

Ready to define the first proof of value?

Choose one business process, one guided journey and one clear outcome. Prove value first, then scale.

Explore Use Cases View Demo Guidance