Your data lives in many systems. Nobody can reach it professionally.
Voice is the most prominent occasion. We connect your data so that people, workflows and AI can work with it.
What the studies say
What it costs you today.
-
1.8 h
per employee, every workday
lost searching across systems.
McKinsey / IDC
-
76%
of German companies
struggle with data silos and poor data quality.
Bitkom 2025
-
54%
of employees
use AI tools without IT approval — shadow AI.
Bitkom Shadow AI 2025
Start now. Waiting for the vendors to solve this is not a strategy.
Where money slips through your fingers, every day.
Master-data duplicates, critical orders, expiring qualifications, email-to-quote, BOM sync, audit docs, order progress — concrete frictions. Click through, see what bites you.
Workshop terms find the right master record.
‚Spindle hoist', not ‚workpiece 4711'.
Example
Which spindle hoists did we manufacture for the railway last month?
The shop floor talks about ‚spindle hoist' or ‚roller compactor'. The material short text reads ‚workpiece 4711'. Whoever doesn't know the official term searches in vain, creates a new entry, generates duplicates. Sparetech finds 7 % duplicates among major customers with multiple sites — caused by exactly this (2023).
Critical orders, before they're too late.
Supplier slips by two weeks, you find out on Thursday.
Example
Which orders are critical this week?
The plant manager keeps a side spreadsheet next to the ERP, calls suppliers every Thursday. Catch it in time and you save the order. Miss it and you pay a penalty.
Qualifications don't expire unnoticed anymore.
Welder cert expires on the 15th, three CL4 orders open.
Example
Which qualifications expire in the next 90 days?
Welder certificates, inspector licences, auditor appointments. Today: a spreadsheet in the QM folder, someone tracks it on the side. When one expires, a railway order stalls because nobody on staff is cleared for CL4 welding.
From an email to a quote.
Inquiry comes in, three days later there's a draft.
Example
Here's the email from Müller. What have we done for them before?
Sales checks the ERP, looks for old offers, asks engineering, builds a PDF. Three days for a standard inquiry.
BOM changes, ERP knows.
Engineering changes a BOM, purchasing orders the old part.
Example
Which BOMs have changed this week?
Engineering changes a BOM in SolidWorks. The ERP doesn't know. Purchasing orders the wrong part. Nobody notices until assembly.
Audit doc is a print button, not an Excel battle.
Material batch, welder qualification, test certificate. Today folders plus Excel.
Example
Compile the doc for order 230815, everything the railway wants to see in the audit.
For every welded part you have to prove material batch per DIN EN 10204, welder qualification and test certificate without gaps. Today folders and Excel. Stress at every audit.
Order progress, without walking into the shop.
‚Is order 230815 on schedule?' — answer sits in three different places.
Example
Is order 230815 on schedule?
Machine status sits on the controller. ERP backflush comes in at end of shift. Operators report in passing. Whoever wants to know walks into the shop, asks three people, collects notes.
Who we are
- Building and organisational development. Both ourselves, with the same people.
- We tell you what's what. Even and especially when it means we're not your partner.
- We build what stays. Also without us.
Michael Schiller and team.
Software and organisational development from one source.
Where do you want to start?
Three depths, depending on how far you want to go in.
Position Audit
One day. One A3 sheet. Honest recommendation.
The problem
You know it's stuck. You don't know exactly where. Consulting workshops produce slides, not answers. Software vendors want to sell directly without understanding.
Our approach
One day on-site. You show us three real processes. We listen. By evening you get an A3 sheet with your five most expensive ERP frictions, three concrete voice-ready proposals and an honest recommendation. Build, buy, or do nothing.
What you have afterwards
An A3 recommendation
- › Your five most expensive ERP frictions, in your language
- › Three concrete voice-ready proposals with rough effort estimates
- › Honest recommendation. Build, buy, or do nothing.
Clarity on what brings money next
- › Which load actually costs hours, which only feels that way?
- › Where is custom build worth it, where does a standard tool suffice?
- › Where is the problem not software, but process?
What doesn't happen
- › No follow-up pitch, no dependency
- › No consulting workshops with PDF at the end
- › No rentals, no licenses
One Process Voice-Ready
One process. Six weeks. Fixed price.
The problem
One process in your ERP eats time daily. Order entry in twelve minutes with three screen switches. Purchase request with Excel intermediate step. Contact creation after a call by hand. Standard tools can't do this, they don't fit your sequence.
Our approach
We build the voice interface for exactly this one process. Six weeks, fixed scope. You speak, your system acts. On your server, switch-off-able, no platform license.
What you have afterwards
What it looks like, order entry in abas
- › Before twelve minutes, three screen switches, typos
- › Now one sentence, one click to release
- › Your terms, your sequence, your exceptions
Or reviewing purchase suggestions
- › Before Excel export, manual reconciliation, back into ERP
- › Now you ask ‚which orders are critical' and get an answer with audit trail
- › Your vendor special rules versioned
What doesn't happen
- › No platform rollout, no weeks of training
- › No change project on top, one thing, clean
- › No lock-in, runs on your server
Control Layer Pilot
Three processes plus AI control layer. Eight weeks. Fixed price.
The problem
Multiple processes need the same building blocks. Identity protection for sensitive data. Audit trail for compliance. Versioned workflows for ISO-9001. Building three single processes one after another is more expensive than the shared layer.
Our approach
Three processes voice-ready, built jointly on a lean control layer. PII tokenization before the LLM, audit trail structurally built in, building blocks versioned like code. Eight weeks, fixed scope. Lock-in-free, your servers.
What you have afterwards
Three voice-ready processes
- › You choose them after position audit or first conversation
- › For example order entry, purchase and EN-15085 documentation
- › All on one shared layer, no overgrowth
Built-in PII protection and audit trail
- › Personal data leaves the house tokenized
- › Every process is replay-able and ISO-9001-ready
- › Skills versioned like code, not in Excel sheets
What doesn't happen
- › No per-user-per-month license, pieces instead of rentals
- › No cloud platform that holds your data
- › Even if you fire us tomorrow, everything keeps running
Honestly
What we do, what we don't.
We build software, not toys. Your workflows become code that still runs in five years, because it isn't made of prompts.
If you need ready-made search across SharePoint and the like, Glean or Microsoft Copilot are the faster path. If you want your ERP, CAD and machines to talk to each other, talk to us.
What it looks like technically
Connects everything you already run.
We build the control layer between your platforms and your systems. Auth, security, audit trail and versioned building blocks are built in. What exists stays where it is. We connect it bidirectionally, step by step.
LLM platforms
Langdock · meinGPT · Omnifact · Microsoft Copilot Studio · Open WebUI · AnythingLLM · Claude Code · n8n / workflows
Where your skills, agents, custom GPTs live
SCHILLER control layer
- › Auth & identity
- › PII & security
- › Audit trail
- › Workflows & tools
- › Notification system
- › Custom processes
Systems & data
ERP · CRM · DMS · Wiki / RAG · CAD / PDM · Machines / OPC-UA · Databases · Email · MDM / Master-data AI · Custom build
The control layer is the place where your systems come together. It governs who is allowed to see what, what never leaves the house, which step needs which approval, what goes into the audit log. Your vendors build their islands. The bridges between them live here, in your vocabulary and your rules.