Skip to content

Service 02 / 06

Consulting before the budget moves.

A decision you can rely on, from people who build and run systems like yours themselves.

01

When this fits

Four situations in which this service is the right answer.

  1. 01.1

    An offer is on the table and nobody in-house can judge whether the proposed architecture will hold.

  2. 01.2

    A running project feels wrong, but the words to say what are missing.

  3. 01.3

    The question is: standard product, custom build, or both, and in which order?

  4. 01.4

    Your team is good, but new to a technology that is about to become decisive.

02

How I work

Order and stance. The four steps themselves are under Process.

Consulting here doesn't mean slides. I read code, contracts and architecture diagrams, talk to the people who use the system every day, and write down what I see, in language that management and engineering both understand.

The result is a document of recommendations, each with the reasoning and the consequence attached. You should be able to check a recommendation rather than having to take it on trust.

I have no product to sell and no partnership with a vendor. If the best answer is "change nothing", that is the answer you get.

03

What you get

What belongs to you at the end and lives in your accounts.

  1. 03.1

    A written assessment with a clear recommendation and its alternatives

  2. 03.2

    A risk list: what can go wrong, how likely it is, and what it costs if it does

  3. 03.3

    A roadmap in steps, each of which pays off on its own

  4. 03.4

    On request, I accompany the implementation as a second opinion without taking it over

04

When I advise against it

The cases where I advise against it, told to you before the engagement.

I don't supply confirmation for a decision already taken. If you need a report that proves a result you have already chosen, you'll hear in the first conversation that we won't write it.

05

Questions

What is usually asked about this service.

01How long does an assessment take?

It depends on the size of the system. A second opinion on an offer is usually a matter of days, an architecture assessment of a grown system one of weeks. We name the order of magnitude after the first conversation.

02Do you need access to our code?

For an architecture assessment, yes; without the code it stays an opinion. Access, confidentiality and data handling are agreed in writing beforehand.

03Do you implement the recommendation as well?

If you want that, yes. But the consulting isn't designed around it. The recommendation has to hold even when another team implements it. Based in Mainz, I work remotely across Germany.

07

Let's talk.

You get an honest first assessment — including the times I tell you not to do it.

Response time
The same working day.
Privacy
No cookies. No trackers. No banner.
Location
Mainz, DeutschlandMainz
Optional.
What should come into being, and what is in the way right now? A few sentences are enough.