Horst Fischerrestless365.com
Talk to me
My path

I did not read the history of this platform. I was in it.

Every step here changed what I could promise a customer — and what I had to warn them about. That is the experience I bring to a conversation.

The maker

Consultant at Damgaard

I learned the product where it was built. Sitting close to the people writing it teaches you which promises the software can keep.

Axapta

The years of the first rollouts

Manufacturing, wholesale, logistics. The first generation of integrations — most of them written by hand, and most of them rewritten later.

Dynamics AX

Microsoft takes over

Bigger projects, stricter audits. This is where I started seeing the same two problems in every single project.

Dynamics 365

Cloud, and a new kind of cost

Continuous updates changed the maths. Everything hand-built now has to be re-tested several times a year — quietly, forever.

Today

Solution architect at soluvine

I work as a solution architect at soluvine, and I write here in my own name. Two views of the same work: what a customer needs, and what a product can carry.

Stories from the working day

Three stories I have told countless times.

None of these are dramatic. That is exactly the point — the expensive things in an ERP project are small, daily and invisible.

Story 01 · Shop floor

The clipboard that outlived three ERP versions

A production line I visited had a clipboard hanging at the end of it. Quantities were written down by hand, carried to an office and typed into the ERP in the evening. Nobody thought of it as a problem — it was just how the day ended. The numbers in the system were always a shift behind reality, and every stock decision was made on yesterday's truth.

Where this leads: shop-floor systems reporting straight into Dynamics 365
Story 02 · Audit

The invoice nobody could find

An auditor asked for one document. It took forty minutes: a network drive, two folder conventions, a colleague on holiday. The document existed — it simply was not findable from the place people were actually working. Compliance is rarely lost in a big failure; it is lost in forty-minute searches.

Where this leads: documents captured and found inside Dynamics 365, stored in a certified archive
Story 03 · Partners

The order that arrived as a PDF, by e-mail

A wholesaler's biggest customer sent orders as PDF attachments. Somebody read them and typed them in — around eighty a week, with the occasional transposed digit that surfaced weeks later as a credit note. Everyone knew it was fragile. Nobody had a budget line called "stop typing orders".

Where this leads: partner documents exchanged as structured data instead of PDFs
From thirty years to this week

Thirty years of pattern recognition, and a head that will not go quiet.

Since the end of the pandemic, soluvine has taken on a remarkable number of new customer relationships and implementations. Sitting in that many first conversations does something to you: the same gaps keep surfacing, and out of them grow ideas and visions that will not leave me alone. Incoming invoice processing is one of them. It is not the only one.

01

What kept coming back

Different industries, different ERP versions, the same room: somebody sitting in front of a document, deciding where it belongs. The clipboard, the missing invoice, the order as a PDF — three stories, one shape. A document arrives, and a human has to translate it into the system's language.

02

What changed after the pandemic

A wave of new projects, a lot of first presentations, and companies far more willing to question their own processes than before. Every one of those conversations adds a data point. At some stage the points stop being anecdotes and start being a design — that is the moment an idea becomes worth building.

03

Where things stand

Invoice processing occupied me for months and is now being built by the development team at soluvine. And as anyone who has run a project of that size knows: while you build, new ideas and visions appear. A second topic is already on my desk — so stay with me, there will be something to report soon.

So the story does not end with a résumé. It ends at a desk where something is always half-finished — and the next thing already waiting.

Next chapterNext