The actual scope depends on your data, interfaces and rules. We select a suitable starting point with you and test it against real cases.
Business value
Not just faster. Better prepared.
The comparison starts with your current process. We measure the improvement including the work that remains for review and exceptions.
Less manual work
Reduce searching, retyping and assembling records.
Active handling time per case
Less waiting
Get complete information to the right person sooner.
Time from intake to outcome
Less rework
Find missing information and conflicts before handoff.
Corrections and follow-ups
More usable capacity
Process more qualified cases with the same team.
Outputs after human review
Released capacity is not automatically a cash saving. A business case also includes integration, model operation, maintenance and the review effort that remains.
Integration, not replacement
Your applications remain the place of work.
We assess existing interfaces, data quality and permissions. An initial pilot can use a limited, read-only export. Targeted system actions can follow later.
ERP & inventory
Orders, stock, items, prices and accounting records.
CRM & service
Customer context, quotations, tickets and actionable responses.
Email & collaboration
Messages, attachments and authorized shared workspaces.
DMS & files
Document versions, PDFs, spreadsheets and scanned records.
Databases & specialist systems
Structured data, existing APIs and agreed file exchange.
Legacy applications
Custom adapters or reviewed handoffs where standard interfaces are unavailable.
System versions, licenses and available interfaces determine the integration. Support for a specific system is assessed before implementation.
Expand with control
The right level of automation. Not the highest.
01
Read & check
Connect information and highlight discrepancies. No changes to the system of record yet.
02
Prepare & approve
Present drafts with supporting evidence. Authorized people approve the next action.
03
Execute within limits
Run suitable standard cases within validated rules. Exceptions stop or escalate.
Fixed rules stay fixed. Calculations, limits and permissions are checked deterministically where possible. AI helps where unstructured information and context need to be interpreted.
From pilot to everyday use
A useful workflow also needs reliable operations.
Clear ownership
Define process ownership, operational responsibility and escalation routes. Accountability extends beyond a successful demo.
Traceable actions
Record data state, model version, output, approval and system changes as appropriate. Deliberately limit retention and access.
Failure handling and recovery
Account for timeouts, partial failures and duplicate execution. Resume from a confirmed state rather than silently repeating actions.
Quality and cost
Agree test cases, quality thresholds, cost per case and usage limits. Change models only after comparison and renewed validation.
Documentation and training
Hand over clear guidance on data flows, operation, limitations and review tasks. Prepare domain and operations teams for their agreed roles.
An agreed service scope
Define monitoring, maintenance, updates and response times separately for production use. A pilot is not an operations contract.
Deployment follows your requirements.
Local models without external model APIs are an option. Local, private or hybrid: Data flows, quality and operating effort drive the choice—not a blanket cloud promise.
Local
Models and processing within your own environment.
Private
Dedicated environment with agreed access boundaries.
Hybrid
Purposeful separation of processing by data class.
Start with an Agent Pilot
Which workflow takes too much of your team’s time?
We define a suitable process, assess data and interfaces, and agree measurable success criteria. Still choosing a process? An optional workflow assessment helps you select one. If the task is clear, we can start directly with the pilot.
Typical scope: 4–6 weeks · €20,000–40,000 excluding VAT · depending on scope and integration
No. We first check whether a rule, an interface or existing software is sufficient. We use AI where it makes sense for the process. During the pilot, value assumptions are assessed against handling time, rework and recurring costs.
Do we need to replace our software?+
The pilot builds on your existing systems where possible. We assess feasible, cost-effective integration before starting. A clearly scoped data export can be sufficient for an initial test.
What can an agent decide on its own?+
Only what the agreed workflow and permissions allow. Critical changes, payments or external commitments require the designated approvals. Uncertainty is escalated to the responsible person.
How is sensitive data handled?+
Data scope, access, storage locations and retention rules are defined for the specific use case. A local model can avoid external model calls; privacy and security also require appropriate technical and organisational measures.
What happens after the pilot?+
You receive a tested prototype, an evaluation and a recommendation. If further use is justified, rollout, support, recurring costs and service levels are agreed separately. The pilot is not an all-inclusive production operations contract.
Not ready yet?
Once a month: better decisions under uncertainty.
Lars Heppert’s newsletter, written in German: one idea, one case study, one chart and a personal note.