The questions that come first
The questions asked most before a buying conversation. The answers are method, not claims.
Do our data leave the building?
Not if they don't need to. Where data cannot leave the building we deploy on-premise; authorization, backup and monitoring are standard.
Do we have to throw away our current ERP?
No. If you have a working setup we build on it; we rebuild a system only when it is genuinely broken.
How do I trust the answer the AI gives?
Every answer cites its source; no answer is produced without a basis, and output below the threshold never reaches the user.
We're a small company — is this for us?
Yes. We work with SMEs and mid-market companies that have a working operation; we start with a small, measurable step.
How long does it take?
The diagnostic call is short, with a written response within two business days. The optional fixed-scope diagnostic takes 2–3 weeks. The first build's duration depends on the job; its scope, duration and deliverable are put in writing at the end of the diagnostic.
Where do we start?
With a free diagnostic call: we talk through one job you cannot measure, then put in writing where to start and what not to do. What follows — a fixed-scope diagnostic, or going straight to the first build — is your call.
How does pricing work?
The diagnostic call is free. The fixed-scope diagnostic and the first build are quoted at a fixed price with scope, duration and deliverable in writing at the end of the diagnostic; there is no hourly billing. At the rollout stage a monthly maintenance-and-development model is available.
We don't have clean data — can we still start?
Yes. In most companies the data sits on paper, in spreadsheets and in a few people's heads. One output of the diagnostic is the answer to “what does your data allow”; the first build is often the very tool that starts collecting it.
Can we use public support programmes such as KOSGEB?
Support programmes covering digitalisation investments exist for manufacturing SMEs, and they typically require a digital maturity assessment from an authorised advisor. Our diagnostic output lays the groundwork for preparing such an assessment. Which programme fits you, and where to go, is something we discuss in the diagnostic call; for eligibility the issuing body's current call text is what counts.
Our machines are old — no PLC, no sensors. How is data collected?
A machine connection is not required. We start with operator entry on a tablet or phone, barcodes, meter readings and records from your existing systems. Sensor investment is proposed only where the measurement plan genuinely calls for it.
What do we keep afterwards? Do we become dependent on you?
The code, the data and the documentation are yours. In an on-premise deployment the system runs on your own server. Maintenance and development are optional; every handover comes with a transfer document.
How much of our team's time does measuring a job take?
One responsible person and roughly a half-hour conversation per week. Half a day for the site walk. Training the people who enter data is part of the first build.