Jan Wagner · software for real-world operations

Lists, paper slips and verbal handovers become one system.

I build software for businesses where spreadsheets, paper and verbal handovers have reached their limit. In production, the warehouse, the lab and the office. Every posting, every correction and every handover stays traceable.

14 years in industry · own products · Germany

The same processes exist in

  • Glass
  • Building materials
  • Ceramics
  • Chemicals
  • Paints and coatings
  • Plastics
  • Food
  • Metal
  • Paper
  • Logistics
  • Lab
  • Administration

Industries

Choose your field.

I come from the glass industry, where I have my own products. The building blocks behind them carry over wherever material, shifts and approvals meet.

Typical situations

When a conversation makes sense.

Spreadsheets between shifts and teams

Order, stock and log sit in separate files. Values get retyped, and in the end every list has its own version of events.

The figure does not add up

In the morning the stock does not match consumption. Nobody can say when the difference appeared.

Changes without a trace

A recipe, a price or a specification was changed. Which version applied when, and why, is not written down anywhere.

An application that has grown

Your business application has run for years, but hardly anyone dares touch the code. Every change takes a long time.

Building blocks

What is the same in almost every business.

Industries differ in vocabulary. Underneath are the same basic questions. These building blocks already run in W-Make Batch and are adapted to your process.

01

Post instead of overwrite

Corrections are cancellations, reversals or reconciliations. The original transaction stays visible.

Runs in W-Make Batch
02

Versions with validity

Recipes and master data have versions. Whatever is posted keeps the version that applied at the time.

Runs in W-Make Batch
03

Stock with records

Receipt, withdrawal, inventory count and open items. Every figure leads to its transaction.

Runs in W-Make Batch
04

Shift book and handover

Faults, maintenance, tasks and photos in one timeline. Open items go explicitly to the next shift.

Runs in W-Make Batch
05

Roles and permissions

Who may see, change and approve what is checked on the server.

Runs in W-Make Batch
06

Reports and integration

Print and PDF, CSV export for SAP, REST API for machine data, German and English.

Runs in W-Make Batch

Services

How I can help.

01

Process analysis

We walk through a process that is causing you problems, ideally on site in production. You come away with an overview of where data gets lost or maintained twice, and a recommendation on what to tackle first.

Arrange a call
02

Product and backend

I build new business applications or bring existing ones back to a maintainable state. Typical topics are postings with cancellation and reversal, versioned master data, calculations tied to a recipe version, and repeatable day closes.

Arrange a call
03

Custom applications

Forms, mail attachments and a spreadsheet become one application in which a case can be followed from start to finish. That can be a web app or an application for Android, Windows or Linux, depending on where the work happens. Examples include document filing, administration and approvals.

Arrange a call
04

Working in your team

I join your development team where business and engineering struggle to meet: integrations, grown code, and architecture decisions that become expensive to change after go-live. I work within the architecture you already have.

Arrange a call

The proof

Built for the glass industry: W-Make Batch.

The shift overview on batch.w-make.com: the current late shift, the target and the next planned batch.
The shift overview on batch.w-make.com: the current late shift, the target and the next planned batch.

For running production · reference version

01

W-Make Batch · Vanilla

The complete version. Postings, stock and shift handover share one data model.

Batch management for container-glass production, designed for furnaces pulling 150 to 600 t/d: from batch sheet through silo and batch log to the daily log, with the shift book as the everyday workplace.

  1. 01

    Recipe

    Composition, version, temperature and cost stay linked to later consumption.

  2. 02

    Batch sheet

    The order to the scale, generated directly from the valid recipe version.

  3. 03

    Silo

    Consumption is deducted from stock automatically.

  4. 04

    Batch log

    What was weighed stays assigned to batch and recipe version.

  5. 05

    Log

    The day close records what the next shift will find.

Demo access on request.

See W-Make Batch

The running application is at batch.w-make.com. The instance is password-protected; temporary access is available on request.

Request access →

Day to day

Software that takes work off people.

Business software is often opened only because it has to be. I build it to take work off the people at the workplace. Then data gets entered in full, and the reports are right.

Immediate feedback

A posting shows straight away what it does: new stock, key figures, cost. Deviations show up while there is still time to act.

The status at a glance

Key figures and open tasks show where the day stands and what is still missing before handover.

Everything in one place

Version, consumption and cost sit together. There is no need to gather them from several lists.

How and where the software runs →

How it works

How a project runs.

01

First call

30 minutes, free of charge. You describe the process, and I tell you plainly whether and how I can help.

02

Process review

I look at the process, on site where possible. Your existing lists and forms are the most important source.

03

Scope and quote

You get in writing what will be built, in what order, and what it costs.

04

Build and operate

The application is built in verifiable steps. After that I run it for you, or your IT takes over.

Updates

What changed in W-Make Batch.

Recent changes to the application, straight from the update feed. Entries appear in the language they were written in.

W-Make Batch

Buchungsintegrität geprüft: Überläufe bleiben sichtbar statt unterzugehen

Umfangreiches Audit der Buchungslogik über LKW-Wareneingang, Stück- und Scherbenlager, Siloabzug, Stornos und Tagesabschluss. Was früher beim Abgleich still verworfen wurde, wird jetzt als offener Posten im Bestand ausgewiesen. Stornos erzeugen echte Gegenbuchungen.

View →
W-Make Batch

Schichtbuch überarbeitet: eine Bedienlinie statt acht Leisten

Die Schichtbuch-Seite von W-Make Batch ist auf eine Orientierungszeile, vier Kennzahlen und Filter mit Zählern umgebaut. Der fachliche Inhalt bleibt: Erfassen, Störungen, Wartung, Meldungen, Aufgaben, Fotos und Schichtübergabe sind unverändert erreichbar.

View →

Development log

What is happening in the code right now.

The latest commits from the product repositories — public, straight from Gitea. Activity without claims.

175 commits in the last 30 days

All repositories →

First call · 30 minutes · free

Tell me where your process gets stuck.

A few sentences about the process are enough: what runs in lists or side calculations today, and who works with it. Within two working days you get a reply and a clear view of whether I am the right person for it.

Arrange a call