Product development
NabuLingo
An AI translation platform in development: widget, mobile app and integrations. Its structure demonstrates work across several connected interfaces.
View project
Services / Automation & Integrations
Duplicate entries, spreadsheets passed between two programs, messages that someone forwards by hand: we connect your software and take over repetitive work. We start with one workflow and establish which parts can be supported reliably.

For teams that repeatedly handle similar information and currently hold the workflow together by hand: details move from an email into a spreadsheet and from there into a second program. A suitable workflow has clear inputs, a recognisable output and someone who can judge its quality.
An integration (API) is the connection through which two programs exchange data. Whether your programs can be connected depends on what they offer. We check that at the start.
We mean workflows on a screen, not machinery or industrial equipment. We work online.
AI can make sense when a workflow has to process language or unstructured documents, for example when sorting enquiries or preparing text. For fixed rules, conventional automation can be clearer. Choosing between them is part of the initial review.
AI outputs can be wrong. Which results a person has to check or approve is set for the particular workflow, before any consequential action is carried out.
Illustrative scenario explaining the service
One workflow is a sensible first step. Not everything can be sensibly automated – we tell you before it costs money. We agree scope and costs in advance (see “What does it cost?”).
We try one document type first. Data sources, permitted services, approvals and ongoing usage costs form part of that pilot’s scope. This is an illustrative project, not a client reference.
For a single workflow there is the Tool Sprint, which can also cover an automation from input to system. It costs EUR 7,900 net and takes 15 working days.
We make a written offer for several workflows or ongoing development after a conversation.
What it costs depends on how many programs are involved, whether they offer an interface and how many checks and approval steps the workflow needs.
Demos with sample data, not client projects.
It depends on the objective, starting point and agreed scope. Deliverables, required input and fees are described before commissioning. A limited first step can help resolve open questions.
An outline of the project and existing public examples are enough to begin. Any required system access is agreed later with appropriate permissions. Please do not send passwords in the first email.
Yes, after reviewing the affected area. This includes its structure, permissions, documentation and dependencies. The appropriate scope of a change can then be defined.
Tell EVA – right now, no appointment, no waiting. She clarifies your goal and scope with you. Before a suitable enquiry is forwarded to us, you review and confirm its summary.
Prefer email: hello@obholz.solutions
Opens your email app with a prepared enquiry.