How I work

What to expect if we start.

No promises you cannot check. Six principles, and what is included every time.

01

I think one step ahead

Half the changes you will ask for in a month are predictable today. I build room for them into the structure up front — a few days now instead of a few weeks later.

Two Glasses by the Bed
02

If the direction looks wrong, I will say so

You describe the task as you see it. My job is to work out which problem you are actually solving, and to say so if the chosen path is not the right one. Even when staying quiet and building to spec would be easier and more profitable for me.

03

Enterprise standard without enterprise weight

18 years inside banking and insurance systems, where "it usually works" does not count as an answer. The same discipline — without the bureaucracy, the committees, or three months before anything starts.

04

Structure is meaning

A well-built system reads like a well-written sentence: you can see what sits where, and why it sits there. This is not aesthetics for its own sake. It is what lets you change the system in a year instead of rewriting it.

05

I write as if someone else will continue

Clear names, decisions explained, no tricks only the author understands. In a year that protects you first — even if the person going back into the code turns out to be me again.

06

Automation works without you

A system that needs you to remember it is not automation, it is another chore. Set it up once, and from there it runs on its own.

What is included every time

A reply within two business days

By arrangement, within one.

60 days of warranty

Any bug found after delivery is fixed at no charge. That is not extra work — it is something I missed.

The price is set before we start

It depends on the project. And if the scope changes, we talk about it before I build it, not on the invoice.

Support after delivery

Hourly, or as a block of hours — a block costs considerably less.