About AutoMates

Build the useful thing, prove that it helped, and leave people in control.

AutoMates is led by Sebastian Pforr and brings together the process, commercial, and technical perspectives needed for an automation engagement. The work is international in outlook, while the delivery remains grounded in the actual people, systems, and risks of one business process.

What this means in practice

Outcome-aligned

The commercial model keeps the conversation close to measurable savings rather than a growing stack of billable technology.

International by default

English is the canonical working language for the public site and international engagements; German remains an available localized entry point.

Specific over theatrical

AutoMates prefers a clear scope, documented evidence, named responsibility, and honest limitation over vague transformation claims.

How we work

The blend changes with the problem.

Process and commercial context

A workable automation begins with the business reason for changing a process: where time is lost, where quality drops, what the risk is, who owns the result, and how the improvement will be measured.

Technical delivery

Architecture, orchestration, models, integrations, data handling, control logic, testing, and operations are selected to fit the real environment instead of forcing a client into a predefined platform.

Accountable handover

The output must be understandable after go-live. That means documentation, ownership, access responsibilities, support boundaries, and a clear definition of what has been validated.

The human side of automation

Give your people more freedom and focus.

Most businesses are not short of valuable work. They are short of the time and attention needed to do it well. The people closest to a process usually understand its exceptions, risks, and frustrations better than anyone else. Treating their knowledge as part of the solution leads to better automation—and to change that teams can support rather than fear.

The AutoMates principle

Our automation projects are not designed around eliminating roles. They are designed to return capacity to the people the business already depends on.

  1. 01

    Start with the people doing the work

    We listen to people handling the process and involve them early. They know where time is lost, where judgment matters, and where an apparently simple workflow becomes complicated in practice.

  2. 02

    Make the purpose clear before the change arrives

    When people understand how the change gives them more time for meaningful work, resistance usually becomes participation.

  3. 03

    Let AI support decisions—not own them

    AI can organise information, identify patterns, and help people evaluate their options. But important decisions and their consequences should remain visible, explainable, and ultimately owned by a person.

The commercial position

A gain-share model needs transparency to be credible.

Start with discovery

The paid discovery phase turns assumptions into a documented current-state baseline and recommendation. It is deliberately useful even where a build does not follow.

Agree the savings logic

The 25% Year 1 gain-share is based on an agreed calculation before implementation. The model distinguishes forecasted savings from what is later observed.

Avoid dependency by default

The project defines what is handed over, who operates the workflow, and what optional ongoing support covers. Long-term help should be a choice, not a technical trap.

Common questions

Answers before the call.

Clear answers to the practical questions that usually come up before a first conversation.

Where is AutoMates based?

AutoMates is legally based in Augsburg, Germany. The company is built to work internationally, with English as the canonical website language and German as a secondary localized entry point.

Who leads AutoMates?

AutoMates is led by Sebastian Pforr. The legal company details and direct contact route are available on the Contact and Imprint pages.

Does AutoMates sell one platform?

No. The approach is tool-agnostic: architecture follows the process, client environment, controls, and operating requirements.

AutoMates

A credible conversation starts with one real process.

If there is a workflow your team is carrying manually, bring it to a fit call. We will be direct about whether it deserves the next step.