How I work

I would rather show you something than describe it.

I sit in most of soluvine's first presentations to an interested company. You hear the same shape of question again and again: people are looking for something they assume does not exist yet. Often it does exist — just not in a form that survives an actual working day. So instead of arguing about it, I build it.

01
Listen

Understand what is really being asked

A wish is rarely a requirement. I want to know what happens on the day this is missing — who waits, who types, who calls whom. That is where the real feature hides.

02
Wireframe

Sketches and mockups first

Deliberately rough and deliberately cheap. The only question a wireframe has to answer is whether we mean the same thing. Being wrong here costs an afternoon.

03
Prototype outside D365

Something you can actually click

If the topic holds up, I build a working prototype outside Dynamics — fast, and free of platform constraints. It then travels with me: whenever the subject comes up in another presentation, I can show it instead of promising it. Other companies recognise their own problem in it surprisingly often.

04
Hand over

The build belongs to the soluvine team

My part ends with a prototype that works. If a company decides to go ahead, the implementation in Dynamics 365 is done by the developers at soluvine — the people who know the platform's rules and its update cycle, and who will maintain it afterwards. I have worked with those developers since the Damgaard days — the same team, on the same platform, for three decades. They know exactly what they are doing, which is why I can hand over something already answered rather than a concept.

This is how a customer's wish turns into a function other customers can use — not through a roadmap meeting, but through something you were able to click on early enough to change your mind about.

Where I sit in this

I am the one who sees it coming, not the one who ships it. Thirty years of projects tell me which problem is about to matter; the conversations I sit in tell me what companies need right now. Out of those two I build the prototype that makes the idea arguable. Turning it into a product that survives four updates a year is craft of a different kind — that is the soluvine team's work, and it is the reason I can stay at the front end of the question.