Josef
Founder & Engineer
Josef has worked in engineering for ten years and has spent the last three building agents.
You work directly with him. No account layer and no hand-off to a separate delivery team.
We build and operate AI agents that handle clearly defined work in your existing processes. They use your systems and remain under your control.1
30 minutes. We clarify the task, systems and approval boundaries. No preparation required.
Before anything goes outside, a person decides.
Both understand language and can call tools. Erben Systems production standards distinguish an agent by a defined process, bounded access and named human accountability.
| Feature | Chat assistant | Production agent |
|---|---|---|
| Understands language and context Takes questions and formulates answers. | yes | yes |
| Uses your documents Derives answers from your own documents. | yes | yes |
| Calls tools A chat assistant can connect to systems today too. | yes | yes |
| Starts from an event or schedule Starts on an event or a schedule. | yes | |
| Fixed mandate, not a conversation A defined process with a clear end. | yes | |
| Configured, narrow permissions Access belongs to the mandate, not the person. | yes | |
| Approvals at fixed points A person decides before every external step. | yes | |
| Step-by-step log A trace of which tools were called. | yes | |
| Evaluation and operations Test cases, monitoring and maintenance in production. | yes |
Takes questions and formulates answers.
Derives answers from your own documents.
A chat assistant can connect to systems today too.
Everything on the left, plus:
Starts on an event or a schedule.
A defined process with a clear end.
Access belongs to the mandate, not the person.
A person decides before every external step.
A trace of which tools were called.
Test cases, monitoring and maintenance in production.
We define the task, the systems the agent needs and where a person must decide.
Feasibility · Task · Systems and data · Roadmap
We build the agent, connect it to your systems and bring it into your team's daily work.
Architecture · Integrations · Approvals · Launch
We continuously check whether the agent is still doing the right thing: evaluate runs against test cases, control permissions and handle errors cleanly.
Logs · Evaluations · Permissions · Recovery · Cost
We define your first agent's task, its access and the points where you decide.
We build an agent with a clear task and integrate it into your workflows.
Evaluation, monitoring and maintenance in production.
The prototype works, but it is not ready for production. We assess what is missing.
We integrate specialist agents or develop directly in your stack.
We integrate the right specialists into a system where each agent takes on a clearly bounded task.
Directly in your stack, when an additional framework is not a fit.
We work the way we build for clients: people decide, and agents take on fixed tasks.3
Founder & Engineer
Josef has worked in engineering for ten years and has spent the last three building agents.
You work directly with him. No account layer and no hand-off to a separate delivery team.
Visuals & Storytelling
Magdalena turns complex subjects into clear visuals and an understandable story.
She shapes the visual expression and brings content and form together.
Ava supports research, early visual concepts, and project preparation and coordination.
Adam handles infrastructure and DevOps.
Good candidates are recurring, clearly described tasks with an output a person can review quickly.
In a workshop, we bound the task, inputs, systems, permissions, output and human approval points.
You receive a documented task boundary, required access, review points, risks and an actionable next step.
No. Autonomy follows the task and its risk. External actions can be tied to explicit human approvals.
We use limited access to only the tools and data required for the specific task.
For every deployment, we jointly name an accountable person who reviews outputs and decides on approvals and changes.
At Erben Systems, production-ready means defined test cases, limited permissions, traceable runs, error handling, approvals and clear operating ownership. It is not a guarantee of error-free output.
AgentOps covers run evaluation, controls, error analysis, maintenance and agreed changes.
Yes. An Agent Review examines task scope, permissions, test cases, logs, approvals, errors and recovery, then provides a prioritised assessment.
Have an idea? We assess whether an agent is a good fit. No idea yet? We start with the tasks that consume the most time today.
30 minutes. We clarify the task, systems and approval boundaries. No preparation required.