Process Packs · Business solutions

Process Packs: business solutions for recurring processes.

A Process Pack describes a business process in business terms: triggers, checks, actions, approvals and KPIs. The pack itself stays the same; the connection to your systems is mapped per customer: SAP, Salesforce, Microsoft or others via APIs, events and MCP.

  • SAP
  • Salesforce
  • Microsoft
Book a process checkThe four packs

A few deep packs instead of hundreds of templates.

We only build packs for processes we know down to the edge cases. Each pack covers a clearly scoped flow, from the trigger to the documented action in the target system.

Four packs for typical bottlenecks in B2B operations.

Order processing is our signature example. The other three sit before, beside and after it.

  • Video demo

    Order processing

    From the won opportunity to the sales order in the ERP. Standard cases run automatically, special cases go to approval.

  • Demo on request

    Quoting & pricing

    Quotes with pricing and availability from the ERP, discounts according to your rules.

  • Video demo

    Service resolution

    From the service case via equipment, warranty and deliveries to a resolution or a service order.

  • Demo on request

    Delivery exceptions

    Detect shortages, price deviations and delivery blocks, propose resolutions and execute them after approval.

The four packs compared.

For every pack we describe the same things: the problem, the trigger, what the agent does, when a person steps in, how you measure the benefit and which systems we show it in.

PackProblemTriggerWhat the agent doesWhen a person steps inMetricExample systems
Order processingWon orders are keyed into the ERP by hand; errors surface only during entry.Opportunity won in the CRMChecks customer, pricing, availability and credit limit, creates the sales order and reports number and status back.Special discount, non-standard payment terms, order value above your limit, blocksShare of orders without manual intervention, cycle time to the orderSalesforce, SAP S/4HANA or ECC, Microsoft 365
Quoting & pricingSales waits for prices, delivery dates and discount approvals.Quote request on the opportunityGets pricing and availability from the ERP, checks discounts against your rules and creates the quote.Discount above the limit, non-standard payment termsTime from request to quote sentSalesforce (including CPQ), SAP, Microsoft 365
Service resolutionService teams gather device, warranty and delivery data from several systems.New service caseClassifies the case, checks equipment, warranty and deliveries, proposes a resolution and creates service orders.Goodwill, credit notes, replies outside defined case typesHandling time per case, share of cases without queries to other teamsSalesforce Service Cloud, SAP, Microsoft 365
Delivery exceptionsShortages, price deviations and delivery blocks surface when the customer asks.Exception in the ERP or check of open ordersAssesses the customer impact, proposes a partial delivery or re-allocation and executes it after approval.Extra costs, date changes, priority customersTime from detection to resolutionSAP, Salesforce, Microsoft 365

Status: order processing and service resolution as video demos, quoting & pricing and delivery exceptions as demos on request. The example systems are what we demo the packs with. They are not a prerequisite.

What’s inside a Process Pack?

A pack brings the business logic. To run it in your company, your team and ours adapt it to your systems, rules and approvals.

  • Agent workflow

    The flow with triggers, checks and hand-offs. Rule-based where rules are enough, AI where context is needed.

  • Capabilities & agent tools

    The business capabilities the process needs, mapped to the interfaces of your systems.

  • Policies

    Rules for when the agent acts on its own, when it asks for approval and when it stops.

  • Approval patterns

    Who approves what, with which context, for example right in Teams or Outlook.

  • Exception handling

    Missing data, blocks and deviations are detected and routed to the right person.

  • Monitoring

    You can always see what the agent did: inputs, decisions, actions and outcome.

  • Evaluation

    Test cases for standard and special cases that run before every release.

  • KPIs

    Metrics such as share without manual intervention, cycle time and exception rate, defined up front and measured continuously.

Signature use case: order-to-cash

One process. Several systems. One continuous flow.

The breaks rarely happen inside Salesforce or SAP. They happen in the process between them. Pick a process and see where agents take over and where people approve.

  1. Buying signal (CRM · Salesforce)
  2. Sales Agent (voluro Nexus)
  3. Opportunity (CRM · Salesforce)
  4. Quote Agent (voluro Nexus)
  5. Price & availability (ERP · SAP S/4HANA)
  6. Approval (voluro Nexus)
  7. Order Agent (voluro Nexus)
  8. SAP order (ERP · SAP S/4HANA)
  9. Invoice (ERP · SAP S/4HANA)
  • AI agent
  • Salesforce
  • SAP
  • Human approval
  • Trigger

Standard cases run straight through. Exceptions reach the right person, with all the data needed to decide.

One business pack, different system landscapes.

Process Packs work with business capabilities such as crm.customer.read or erp.salesOrder.create rather than fixed APIs. For each customer we map these capabilities to their systems: in SAP, for example, to OData services, function imports or custom APIs; in Salesforce to custom objects, flows or Apex actions. Other systems are connected via suitable APIs, events and MCP. Whether that works in your landscape is checked case by case.

Examples of business capabilities

  • crm.opportunity.read: read the won opportunity and its line items
  • erp.customer.check: check business partner, credit limit and blocks
  • erp.salesOrder.create: create the sales order in the ERP
  • delivery_block.search: find orders with a delivery block

Maturity and prerequisites.

The four packs are fully worked-out reference solutions at the business level. We show them in our demo instance with Salesforce, SAP S/4HANA and Microsoft 365: order processing and service resolution as video demos, quoting & pricing and delivery exceptions on request.

For a pack to run in your company, it needs interfaces to the systems involved, reasonably clean master data and approval rules set by your business team. Whether these prerequisites are met is what the proof of value with your systems establishes. You then decide on production based on measured figures.

Next on our list are invoice discrepancies and clarification cases between sales, logistics and accounting. We only release a new pack once it has the same depth as the existing four. If your process doesn’t fit any of them today, talk to us. Custom packs are built on Nexus with the same guardrails.

Process Packs in SAP and Salesforce landscapes.

The packs run across systems. We know SAP and Salesforce particularly well, which is why our examples use them. Here is how the agents work in these landscapes, and the thinking behind the approach.

More use cases on Nexus.

Besides the Process Packs, Nexus also runs your own agents under the same guardrails. Three examples, each with approval and write-back to the system.

  • Checking a supplier invoice and parking it in SAP

    The AI agent extracts a supplier invoice, matches supplier, bank details, purchase order and goods receipt, submits a price deviation for approval and parks the invoice in SAP S/4HANA.

    What the video shows
    1. Invoice arrives and is extracted
    2. Supplier and bank details checked
    3. Three-way match with purchase order and goods receipt
    4. Price deviation submitted for approval
    5. Invoice parked in SAP S/4HANA (MIR4)

  • Enriching and translating product texts from SAP

    From a material’s raw ERP text, the AI agent creates short and long texts, translates them into English and French using a glossary and writes them back to SAP S/4HANA after approval.

    What the video shows
    1. Raw material text in SAP (MM03)
    2. AI creates short and long texts
    3. Translation into DE, EN and FR with a glossary
    4. Review by the approver
    5. Texts back in SAP, before and after

  • Personalizing a campaign mailing from Salesforce

    For a trade-fair follow-up, the AI agent checks consent in Salesforce, creates personalized email drafts in German and English, gets approval and updates the campaign members.

    What the video shows
    1. Trade-fair campaign in Salesforce
    2. Consent checked, contacts without consent excluded
    3. Templates in German and English with AI notice and unsubscribe link
    4. Approval
    5. Email drafts in Microsoft 365, campaign updated

Common questions about Process Packs.

How is a Process Pack different from a template?

A template is a starting point you finish yourself. A Process Pack describes the complete flow with policies, approvals, exception handling, test cases and KPIs. In the proof of value it runs against your systems in a test environment.

Will a pack fit our systems and our customizing?

That is why we separate the business logic from the connection. The pack stays the same; we map it to your fields, objects and interfaces per customer. Our deepest experience is with SAP, Salesforce and Microsoft. Other systems are connected via suitable APIs, events or MCP, after a case-by-case check.

How mature are the packs?

All four are fully worked out and run in our demo instance. How well a pack works in your landscape depends on interfaces, data quality and your rules. We measure that in the proof of value, before you decide on production.

Which pack should we start with?

The process that costs you the most manual hand-offs between systems today. Often that is order processing. In the free process check we look at your process. If a classic workflow is enough, we tell you that too.

We use Agentforce, Joule or Copilot. Do we still need Process Packs?

Native agents are strong inside their own system. A Process Pack takes over where the process crosses system boundaries, for example from the CRM opportunity to the ERP order. Nexus can bring in your existing agents. Policies and audit trail apply to the actions executed through Nexus tools.

Start with one process.

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

Book a process check Discuss a proof of value