Approach · Phase 2

Proof of value: measure first, then decide.

A limited part of the process runs on voluro Nexus with your systems in a test environment. It is measured against KPIs we agree with you before the start. The proof of value has a fixed price and typically takes 4–6 weeks. Then you decide: go or no-go.

What the proof of value covers

  • Limited scope

    A clearly defined part of the process, such as orders from one sales channel through to the sales order in the ERP, with rules for approvals and exceptions.

  • Your systems in a test environment

    Nexus works with test or sandbox systems, for example SAP, Salesforce and Microsoft. A relay service in your network only opens outbound connections.

  • KPIs agreed upfront

    Such as the share of cases without manual touches, correction rate or cycle time. We set metrics and target values together.

  • Fixed price, typically 4–6 weeks

    Scope, duration and price are set out in the proposal after the process check.

Go/no-go criteria

We agree the criteria before the start. Typical examples; the target values depend on your process:

CriterionWhat is measuredGo if …
Automation rateShare of test cases that run through without manual touchesthe agreed target is met
QualityError and correction rate in the target systemit stays below the agreed threshold
Cycle timeTime from receipt to action in the target systemit drops measurably compared with today
ControlHandling of cases with an approval or blocking ruleevery such case was handled as agreed
OperationsPrerequisites for security, operations and approvalsno open points prevent production

If the criteria aren’t met, it’s a no-go. You still get the measurements and our assessment.

How the proof of value runs

  1. Fix scope and KPIs

    Confirm the part of the process, systems, approval rules and metrics from the process check.

  2. Connect systems

    Nexus turns existing interfaces, for example in SAP and Salesforce, into controlled agent tools. You don’t rework your landscape for it.

  3. Adapt the solution

    Map the business process pack onto your systems and define what runs automatically, what needs approval and what is blocked.

  4. Test with real cases

    Run typical transactions through the test environment, standard cases and exceptions alike.

  5. Go/no-go

    Evaluate the result against the criteria. You decide whether the process goes into production.

After a go: the path to go-live

After a go, we prepare production. What was built in the proof of value is carried over, not rebuilt. On top come the security, operations and approval concept, separate DEV, TEST and PROD environments, and monitoring. The process goes live once production readiness is signed off.

Before go-live

  • Security concept: identities, roles, data flows
  • Operations concept: ownership, incidents, updates
  • Approval concept: who approves what above which threshold
  • Monitoring with the same KPIs as in the proof of value

Typical systems in the proof of value

Examples from our core expertise. We connect other systems through APIs, events and MCP, assessed case by case.

  • SAP

    • SAP S/4HANA
    • SAP ECC
    • SAP BTP
  • Salesforce

    • Sales Cloud
    • Service Cloud
  • Microsoft

    • Microsoft 365
    • Teams
    • Outlook
    • Entra ID
  • Other systems

    • ERP and CRM from other vendors
    • In-house applications
    • APIs, events, MCP

Questions about the proof of value

How is a proof of value different from a pilot?

The agent works with your systems and executes process steps instead of just answering questions. The criteria are fixed beforehand, and what you build is the basis for production.

Why a test environment?

It lets the agent create real transactions, such as sales orders in the ERP, without touching live operations. Systems and customizing still match your landscape.

What does the proof of value cost?

It comes at a fixed price, which we quote after the process check once process, systems and scope are clear.

What do you need from us?

Access to test or sandbox systems, a process owner as the business contact and someone from IT for the connections.

Next in the approach

Start with one process.

30 minutes · free · with a senior architect. You get a verbal initial assessment and concrete next steps.