RequestChange
Version 0.2
Living whitepaper

Four services. One research question.

Request Change connects product design, engineering and AI. We study how this can enable secure handovers between customer and supplier agents.

Working statusThis is a working hypothesis. We test it against real product and specialist processes.
Portfolio today

We work at four points in product creation.

These four services form the foundation of the whitepaper.

Product design & engineering

01

Concept, package, 3D and visualization.

AI accelerates variants. Geometry and feasibility remain binding.

AI process automation

02

Enquiries, drawings, feasibility, calculation and documents.

Agents prepare specialist work. People approve critical steps.

Configurators & digital products

03

Product logic, variants, 3D and structured handovers.

Rules become executable. Complexity becomes machine-readable.

AI enablement & agentic setups

04

Roles, tools, permissions, operations and training.

Teams use agents with intent. Accountability stays clear.

Next step

The process does not end at the company boundary.

Today, enquiries, drawings and changes move between companies by email or PDF. In future, agents can prepare and check these handovers.

  1. 01

    Request

    The customer agent hands over requirements, sources and product context.

  2. 02

    Check

    The supplier agent checks mandate, product rules and missing details.

  3. 03

    Clarify

    Open points return to the customer in structured form.

  4. 04

    Approve

    People decide on price, timing and exceptions.

  5. 05

    Handover

    Result, source, version and responsibility are recorded.

Framework

This needs six clear rules.

A technical connection is not enough. Every handover needs a fixed frame.

  1. 01

    Identity

    Who acts for which company?

  2. 02

    Mandate

    What may the agent check, execute or commit to?

  3. 03

    Semantics

    Which terms and product rules apply?

  4. 04

    Data

    Which information may leave the company?

  5. 05

    Evidence

    Which source and version support the result?

  6. 06

    Escalation

    When must a person decide?

Work programme

What Request Change builds from this.

  1. 01Shared data models for request, variant, tolerance and change.
  2. 02Interfaces between configurators, drawings, calculations and agents.
  3. 03Verifiable handovers with source, version, status and approval.
  4. 04On-premise and hybrid architectures for sensitive data.
Collaboration

We are looking for real handovers between customers and suppliers.

No demo without a process. Product rules, documents and clear approvals matter.