Do all modules have to be introduced at once?

No. A project starts with three or four modules and the first stage is in use after roughly eight weeks. The rest follow once those carry.

Where do the dimensions come from, if not from the spreadsheet?

From three routes that write into the same field: a self-service portal for dealers, internal entry, and a documented REST interface with its own key per partner.

What happens to photos and videos from production?

They hang on the unit, not in a folder. The shop-floor view records per unit what happened; the same evidence later sits on the order and in the notification to the customer.

How quickly is something useful in use?

The first stage runs after about eight weeks. That is not a prototype but the part of the process used in daily operation from then on.

Who owns the data and the source code?

You do. We work with widespread, well-documented technology and hand over the source code; data and accounts are in your name.

Manufacturing ERP for window production: what measurably changes

The short answer

A manufacturing ERP for windows, doors and glass carries an order from the dealer's purchase to the label on the crate without dimensions being re-entered along the way. What separates it from a collection of email, CRM and spreadsheets is not a feature list but the disappearance of the handovers between them.

That is exactly where the expensive errors came from. A panel dimension travels from an email into the CRM, from there into a spreadsheet and from there to the floor. Every step is a chance to transpose a digit — and it surfaces once the pane is cut.

Measured, not estimated

What measurably changed

The figures below come from a production site running this system and were measured there. They are not industry averages and not a model calculation.

Dimension errors at system borders

Eliminated entirely. Dimensions and parameters run unbroken from the customer to production; manual transfer between email, CRM and spreadsheet is gone. This class of error cannot return, because the step that produced it no longer exists.

Handing an order to production

95% less time for the person responsible. The order is no longer prepared and passed on — it is released.

Answering where an order stands

90 to 95% less time. Photo and video evidence sits on the order, and the customer is notified automatically at each production stage instead of asking.

Output per office employee

At least doubled. The same staff handles more orders because re-entry and follow-up questions fall away.

The figures describe one operation, compared with its previous way of working out of email, CRM and spreadsheets. They say nothing about what a site that already works end to end would gain.

Why those errors do not come back

The difference is structural, not statistical. A dimension captured once and kept in the same system cannot be corrupted in transfer, because there is no transfer. What disappears is not a share of the errors but a whole class of them.

This holds only for errors at the seam between systems. A window measured wrongly stays a window measured wrongly — that is fixed on site, not in software.

What falls away with it

✓The email with dimensions that someone retypes into the CRM.
✓The spreadsheet that grows out of it and gets printed in the workshop.
✓The question of which version of the dimensions is the valid one.
✓The phone call asking where the order stands.
✓The hunt for the photo showing how the unit left the building.

Legal status for windows and doors: what applies, and from when

Common questions

Questions that keep coming up

Do all modules have to be introduced at once?: No. A project starts with three or four modules and the first stage is in use after roughly eight weeks. The rest follow once those carry.
Where do the dimensions come from, if not from the spreadsheet?: From three routes that write into the same field: a self-service portal for dealers, internal entry, and a documented REST interface with its own key per partner.
What happens to photos and videos from production?: They hang on the unit, not in a folder. The shop-floor view records per unit what happened; the same evidence later sits on the order and in the notification to the customer.
How quickly is something useful in use?: The first stage runs after about eight weeks. That is not a prototype but the part of the process used in daily operation from then on.
Who owns the data and the source code?: You do. We work with widespread, well-documented technology and hand over the source code; data and accounts are in your name.

Book a call

Tell us about your process

Two sentences are enough: what runs on spreadsheets, paper or shouting today. You get an assessment within 48 hours, not a brochure.

✓First call at no cost

✓Reply within 48 hours

✓Fixed price per release