One named contact for your workflows
We map how work actually flows through mid-sized companies, find media breaks and duplicate data entry, and streamline them with IT. Analysis before tooling, delivery in small steps, documentation included. Based in Söhlde near Hildesheim, working across Lower Saxony and nationwide via remote support.
1
Named contact per project
DE
Server location for operations and data
24 h
Reply on business days (project experience)
6
Core sectors in the Mittelstand (project experience)
We are based at Glockruthenallee 16 in 31185 Söhlde, in the Hildesheim district, and we work for mid-sized companies: trades, manufacturing, service providers, wholesale, logistics and administration. Our job is unspectacular and still pays off — we look at how orders, documents, appointments and data move through your company today, and rebuild the points where people retype, search or chase information by phone. A process analysis always comes first, never a tool.
One contact through every project phase
How we work
Most enquiries reach us with a solution already in mind: new software, an interface, an automation. We take that idea seriously, but we test it against the actual workflow first. Very often the mapping shows that part of the problem is organisational and needs less technology than expected, while somewhere else an unremarkable duplicate entry quietly costs working time every single day. That order — understand first, build second — is the real core of how we work.
We work with what is already in the building. A grown industry application, an inventory system, time recording and several spreadsheets are not mistakes; they are the starting point. Before we talk about replacing anything, we check whether the systems can be connected: through an interface, through a file exchange or through a lean intermediate layer. As a rule that is cheaper, faster and far less disruptive for your staff than switching systems. What that looks like in practice is set out under process automation and interfaces.
One named contact
From the first mapping session to ongoing support you speak to the same person. No ticket queue where the context has to be re-explained at every handover, and no rotating project leads who need to learn your operation from scratch.
Analysis before tooling
First the as-is mapping, then the decision about means. We write down where data is captured twice, where the media breaks sit and how often a step occurs per day. Without that basis, any effort estimate is guesswork.
Small steps, not a mega-project
We cut work so that one part is live and showing an effect within a few weeks. Large single-shot changeovers tie up your team for months and are hard to correct once requirements move.
Documentation is included
Every automation and every interface is described: trigger, data fields, error cases, responsibilities. Process documentation is part of the work, not an add-on quoted separately.
Operations and data in Germany
What we operate runs on servers in Germany. Data processing agreements, retention periods and access rights are settled before the start and put in writing, so your privacy records match what actually runs.
Plain language, no jargon
We write reports that management can read without translation. Technical detail belongs in the appendix, the decision belongs up front — with effort, benefit and open questions side by side.
Why analysis comes before the tool
An automation is only as good as the workflow it reproduces. Automate a messy process and you get the same process faster and at higher volume — errors included. That is why we start with a stocktake inside the company: we talk to the people who run the workflow every day, look at the documents and screens they use, and note where a case stalls because a piece of information is missing.
That mapping produces a report with prioritised measures. Prioritised means each measure carries a rough effort class and an estimate of how often the affected step occurs. This lets you decide what gets built first and what deliberately waits, before a single line of code exists. In most companies we complete the stocktake within two to three weeks (project experience), depending on how many departments are involved.
The analysis result is yours
Delivery in small steps
Initial call
A phone or video call of around 30 minutes. We clarify what the issue is, which systems are involved and whether working together makes sense. If we are not the right fit, we say so at this point.
As-is mapping, on site or remote
We follow the workflow where it happens: in the office, the workshop, the warehouse or the back office. Observation beats description, because real work almost always differs from the documented version.
Report and prioritisation
You receive the analysis with media breaks, duplicate entries and a sequence for delivery. On that basis we cost each measure individually as a fixed price, instead of estimating one large budget.
First measure live
We build the first measure and put it into real operation — deliberately small, so you see the effect before further funds are committed. After that you decide whether and how to continue.
Extension and operations
Further measures follow at the same rhythm. Support runs alongside: monitoring the handovers, adjusting after system updates and one contact for incidents, so nobody in the company is left alone with a transfer that has stopped.
A phone or video call of around 30 minutes. We clarify what the issue is, which systems are involved and whether working together makes sense. If we are not the right fit, we say so at this point.
We follow the workflow where it happens: in the office, the workshop, the warehouse or the back office. Observation beats description, because real work almost always differs from the documented version.
You receive the analysis with media breaks, duplicate entries and a sequence for delivery. On that basis we cost each measure individually as a fixed price, instead of estimating one large budget.
We build the first measure and put it into real operation — deliberately small, so you see the effect before further funds are committed. After that you decide whether and how to continue.
Further measures follow at the same rhythm. Support runs alongside: monitoring the handovers, adjusting after system updates and one contact for incidents, so nobody in the company is left alone with a transfer that has stopped.
A contact who knows your operation
Process work depends on somebody holding the whole picture. Whoever knows why one department keeps a second list also understands why an apparently obvious automation will not work there. That is why the contact person stays the same throughout — including during support after delivery. You reach us on +49 5123 9579000 or in writing; enquiries on business days are usually answered within 24 hours (project experience).
Documentation is part of the work, not a surcharge
An automation without a description is a black box. When the person who set it up moves on, relief turns into risk. So we document every handover between two systems in a way that can be understood and checked without us.
- Which data moves when, in which direction and on which trigger
- Which fields are mapped and how deviations are handled
- What happens during an incident, who is informed, how it is caught up
- Who is responsible internally and which access credentials are on file
- Which checks run automatically and how you recognise the normal state
| Section | Recorded | State |
|---|---|---|
| Data path | Invoices, hourly, one direction, trigger: status approved | checked |
| Field mapping | 26 fields; deviations go to the error list instead of the target system | checked |
| Incident | Notification to accounts, catch-up on the next run | checked |
| Responsibility | Accounts department; access details and expiry dates on file | annually |
| Normal state | Totals reconciled per run, alert above a one-document deviation | checked |
Operations, data and traceability
Whatever we operate runs on servers in Germany. For companies handling staff records, customer data or order documents that is not a side note but a precondition for their own privacy documentation. Before the start we settle which data an interface genuinely needs and deliberately transfer no more than that — the German Federal Office for Information Security (BSI) recommends exactly this restriction to what is professionally necessary in its baseline protection guidance. Traceability belongs with it: automated handovers log what was transferred and what was not, so a case that gets stuck shows up in the log rather than when a customer calls. The same principle applies to replacing old systems — we migrate in stages with a way back, instead of switching over one weekend. Details are under legacy replacement.
Based in Söhlde, working across Lower Saxony
Söhlde sits between Hildesheim, Salzgitter and Peine. From here Hanover, Brunswick, Wolfenbüttel, Hameln, Göttingen and Celle are within easy reach, and that radius is exactly where the part of our work happens that has to happen in person: the as-is mapping. For a workshop, a warehouse or a mail room, no video call replaces walking the floor. The places we visit regularly are listed under regions. Everything else can be handled reliably from a distance: coordination runs by video call, delivery and support by remote access through secured credentials you can revoke at any time. That is why we also look after companies outside Lower Saxony, nationwide — for the first mapping session we still travel out once.
How our approach differs
Three common routes to streamlining workflows in mid-sized companies — and where each one tends to stall.
Analysis first, then delivery
- Included: As-is mapping on site before any tooling decision
- Included: Fixed price per measure after the analysis
- Included: First measure live before further funds are committed
- Included: Documentation and support planned in from the start
Buy the software first
- Not included: The feature set dictates the workflow instead of the other way round
- Not included: Existing systems stay alongside as islands
- Not included: Duplicate entry moves rather than disappears
- Not included: Rollout and training effort only becomes visible late
Handle it internally on the side
- Not included: Knowledge sits with individuals without cover
- Not included: The project competes permanently with daily business
- Not included: Home-grown handovers usually run without logging
- Not included: When systems change, there is no time to follow up
A start with a clear result
- Stocktake of your workflows in the company, on site or remote
- Report covering media breaks, duplicate entry and effort classes
- Prioritised measures with a sequence for delivery
- The report stays yours, even without a follow-up order
Delivery per automation or interface from 4,900 € net plus VAT, as a fixed price after the analysis. Ongoing support from 190 € net plus VAT per month.
Prices as of September 2026. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.
What we deliberately do not do
- No automation without mapping the workflow first — not even when it would be quick.
- No savings figures promised before we have measured how often a step actually occurs.
- No system changeover over a weekend without a way back to the previous state.
- No solution that only we can operate: credentials, rights and descriptions stay with you.
- No corporate programmes with committee structures — our setup fits companies where decisions are short.
If you want to see which areas we work in and what typical projects look like, that is set out in our services overview and under references. Specific client projects are discussed in person, because workflows and figures from live operations do not belong on a website.