dreis.dev — Lasernet Output Management. Jack of all IT trades. Master of Lasernet.

"We'll sort out the documents later."

I've heard this sentence in almost every project. It comes up at kickoff, usually from someone whose head is in finance or warehouse logistics at that moment. The documents become a line item, somewhere between training and data migration. And that's where they stay.

The numbers are in a book Tabellae published in 2025, based on 600 analysed projects. 75 percent of ERP projects push the go-live at least once, often because of the documents. In 8 out of 10 projects, invoice, delivery note and dunning letter only land on the table shortly before go-live. Output management should cost around 5 percent of the ERP budget. Push it to the end and you pay 15.

The expensive part isn't the form. The expensive part is that without an invoice, no revenue leaves the building, and without a correct delivery note, no goods do either. One missing field on one document ends up holding back the entire ERP investment. Sorting it out later usually means sorting it out at a higher price.

What Lasernet actually does

Lasernet takes data from your source system and turns it into documents. Source system means anything that outputs XML, JSON or ASCII. That's D365 FO, SAP, AX 2012, AS400, Infor, but just as well a print job, a file, a REST or SOAP input, or an archive system like d.3. At the other end is the destination. Printer, email, PDF, archive, SFTP or a REST API, depending on where the document needs to go. In between sits the logic that decides what it looks like and what's on it.

You could have all of that coded in the ERP instead. Several ERP vendors work with the same rule of thumb: 100 hours of customizing pull up to 700 hours of testing and maintenance behind them, because every evergreen update puts the code back on trial. A misplaced comma on the invoice turns into a developer ticket. In Lasernet, the same comma is a configuration setting, and the ERP stays untouched.

The most important rule from those 600 projects is called Output first. What has to be on the invoice decides what data the ERP has to deliver, not the other way round. That's why the documents belong at the start of the project. And because a document isn't done until it reaches the recipient, I take care of the route there too. Interface, network, printer, Active Directory, DNS. My responsibility doesn't stop at the form.

Four areas. One contact.

01Concept

Lasernet Architecture

The blueprint before anyone moves a wall. I design the system architecture for new implementations and clean up installations that have grown over years, where nobody today can tell you why what runs where. At the end you know what you've got and what it's going to cost you.

02Logic

Lasernet Development

Workflows and backend logic, from data processing to interfaces to JavaScript, REST and SOAP. Data rarely starts in Lasernet. So I hook in where it comes from, whether that's D365, SAP, AX 2012, AS400, Infor or d.3.

03Forms

Lasernet Design

Forms and layouts that work and look good doing it. Your invoice is the document your customer reads most often. It deserves better than the standard template with the logo slightly off.

04Ops

Containers & Infrastructure

Lasernet is moving into containers, and I've been living there for a while. Docker, Compose, Swarm, cloud or on-prem. My troubleshooting doesn't stop at the GUI. It goes down to where the server meets the network.

Two ways to start.

Scoping Day

One day before your ERP project starts planning. After that, the documents are in the budget.

In 8 out of 10 ERP projects, the documents only show up on the agenda shortly before go-live. I won't send you a questionnaire, I get access to the system that prints today, and I look. We count the variants per document, look at what's coming your way (new countries, e-invoicing mandates, a rebrand), and by the end I estimate what the whole thing costs and how many design workshops you really need.

Document inventory pulled from your current system, not from a list
Variant matrix per document, what exists and what for
Findings report: what's built today and what should move to the new system
Cost estimate including the number of design workshops required
A Project Scope Document, CFO-ready, every number with a source

€1,280Fixed. Remote, 8 hours. On-site: €160/h.

Book the Scoping Day

Remediation Analysis

For installations that have grown over years. Afterwards you know what you have. And which parts anyone still uses.

An installation that has grown over years comes in layers: a workflow from 2014, a second one from 2019 sitting next to it, an exit since the last upgrade that nobody can place anymore. If you want to clean up, you first have to know what's there, and that's not in any documentation, it's in the instance. So I look there before anyone plans a remediation.

Inventory from the instance, not from the documentation written in 2017
Count variants, per document
What runs, what runs into nothing, what still carries weight
The result is a finding: what stays, what goes, what it costs

By effortMulti-day. Estimate after a first look.

Request the analysis

Eight of more than sixty.

The eight projects here are picked by problem type, so you'll recognize your own.

Integration · D365 FO

Order lines from D365 become JIRA tickets, and the ticket status finds its own way back.

Nobody types a ticket status twice. The licence bill looks the same as before.

IoT Integration · Fuel logistics

An old fuel tank reports in before it runs dry.

Nobody drives out to look at a fill level anymore. The tanker rolls when the tank says so.

Automation · Canteen/catering

The canteen receipt builds itself.

Order JSON in, receipt PDF with product images out, straight to the inbox of whoever placed the order.

Automation · Manufacturing

Parts list on the right, drawing on the left, every single page.

The merge lines up at any page count, three drawings or none. The customer stopped counting pages.

Automation · Fashion retail/textiles

The order generates its own labels and drops them on the manufacturer's SFTP.

Nobody sends labels after the fact by hand anymore.

Print Engineering · Logistics

Over 100 Wi-Fi label printers across 20+ sites, printer switching by barcode scan.

No ERP ticket, no IT trip to the site, no touching Lasernet.

Automation · Producer

Manuals of 200 to 1000 pages come off the print line overnight.

During the day it's free for the rest of the company, and the employee is back doing his actual job.

Document Security · Services

Reports go out PGP-encrypted over FTP, and nobody encrypts by hand.

Nothing readable travels the line anymore. Anyone listening sees cipher.

What sticks after the project.

Four voices, uncut, with name and company. They talk about response time and about how we dealt with each other, because in the end both are what makes the difference.

Maximilian BadenMakara Sports · Owner

Wir sind begeistert. Wir haben eine schnelle, einfache und moderne Lösung erhalten. Alles wurde sehr verständlich erklärt und unsere Prozesse wurden langfristig vereinfacht und verbessert! Auf Support-Anfragen kam die Lösung noch am selben Tag.

Morten Lund-ThomsenBAADER Food Systems · Head of IT

Stephan unterstützt BAADER seit 2014 beim Ausbau und der Entwicklung unseres SAP/Lasernet-Output-Managements. Er hat profundes Lasernet-Wissen und liefert stets stabile und zuverlässige Lösungen. Wir sind mit der Zusammenarbeit sehr zufrieden.

Kevin BewernickUniferm GmbH & Co. KG · Head of First Level Support

Dank dreis.dev sind wir bei der Anpassung von Formularen mit der Lasernet-Software flexibler und agiler. dreis.dev übertrifft unsere Erwartungen regelmäßig und liefert Lösungen mit hoher Qualität und Professionalität. Ich empfehle dreis.dev von Herzen.

Helen Klasetengo. Smart Freelancing · Key Account Manager

Mit Stephans Hilfe betreuen wir meine Kunden im Bereich Output Management, und das zur vollsten Zufriedenheit! Der Kunde will ihn gar nicht mehr hergeben. Stephan ist professionell, menschlich und offen.

I'm Stephan, from Hamburg.

Over 60 projects · 27 clients
More than 10 ERP migrations
Support, again and again, for 27 clients

I've been doing Lasernet since 2010. I trained as an IT specialist in systems integration. That meant five years of looking after Windows and Linux servers, and Lasernet started alongside. I still run my own servers today, network, firewall, updates and backups included. So I know what an expired certificate or a patch does to a service before the first call comes in.

Since then it's added up to over 60 projects for 27 clients, more than ten of them full ERP migrations. A big part of my work is support. Not the projects, the day-to-day afterwards. And that's exactly where the surrounding knowledge pays off: I usually see quickly where it's stuck, and whether it's Lasernet at all. Often it isn't. I help anyway, or at least I deliver the proof that the problem is somewhere else. I've been a service provider my whole working life. When people come back afterwards, I take that as a good sign.

I've been self-employed since 2022/23. On the side at first, full-time since 1 January 2025. Since October 2026 it all runs as dreis.dev-ELOPMENT GmbH. For you, that means purchasing and contracts get easier. For the work, it means nothing. That stays as it was.

I have ADHD. In practice that means: I'm into someone else's problem fast. I switch between clients, systems and ticket queues without a run-up. That's not a footnote, it's the reason second and third level come from one person here. When something breaks below the GUI, I stay on it where others hand off. How working together actually runs is in the operating manual: How to work with me.

FAQ

Do I even need Lasernet? D365 FO ships with standard reports.

Depends on how many variants you have. In standard D365, every change per country, language or channel is developer work. In Lasernet, the same change is configuration. The more variants, the faster it pays off. One site and three forms? Probably not. If Lasernet won't do anything for you, I'll say so at the Scoping Day.

Our installation has grown over the years. Nobody dares touch it anymore.

Seen it before. That's what the Remediation Analysis is for: I take inventory straight from your live instance, not from the docs someone wrote in 2017. Multi-day, billed by effort. Afterwards you know what you have. And which parts anyone still uses.

We run SAP. Does that work?

Yes. SAP, AX 2012, AS400, Infor, I've connected all of them. The source can be anything that outputs XML, JSON or ASCII. As a print job, as a file, via REST or SOAP. And if the source system doesn't deliver clean data, I look at why.

Do you do e-invoicing too?

Yes, that runs through Lasernet. The formats differ by country. I take your data and build the document in whichever format applies.

Can I get the licences from you as well?

Yes. I'm the first freelance reseller partner of the Lasernet Group. Lasernet and LAC come from me, and so does the configuration. One less vendor to deal with.

How do we start?

With the Scoping Day. EUR 1,280 fixed, remote, 8 hours on your system. Afterwards you know what you have. And I know your installation, in case we go further.

We're on fire right now. There's no budget for a Scoping Day.

Write anyway. Getting my head into unfamiliar systems fast is exactly what I do. Emergencies we sort out directly, no form.

Tell me what's going on.

A few sentences are enough: which system, what's stuck, by when. We'll sort out the rest on a call. If it's on fire right now, write here anyway and put "Emergency" in the first line.

stephan@dreis.dev