my approach in 3 steps

From manual work to working software

Three phases, fixed agreements, one point of contact. I build with AI as an accelerator and with fixed checks that guard the result, and every step can be rolled back on its own.

Schedule a call See the rates
~/aanpak · zsh
$ ./aanpak.sh --start
➜ Understand first
✓ Processes mapped
➜ Choose then
✓ Priorities in order
➜ Build and measure ongoing
✓ Something working every week
// no big bang, every step rolls back on its own
$
3 phases
2 clear services, the rest by agreement
1 point of contact
0 surprises afterwards
the process

From manual work to live

first

Understand

What actually happens today, by hand and in the code? I sit with it and record where the time leaks away. Processes mapped Where the time leaks away A clear price agreed up front

then

Choose

Not everything at once. We take what pays off most and carries the least risk, and that goes first. Priorities in order A technical plan you can read Your go-ahead before the build

ongoing

Build and measure

I build AI-accelerated in short rounds. Every round is tested and reviewed before you see it, and goes live alongside what is already running. If it does not work, you switch back. Something working every week Live alongside the existing A measurable difference

under the hood

Build fast, guard strictly

Writing code is rarely the bottleneck anymore. The difference is in what surrounds it: written agreements, automated checks and decisions you can read back.

01

Everything on paper

Every phase produces a document you can read: what we want to achieve, what gets built and why. You look decisions up — you never have to reconstruct them.
02

AI as the accelerator

I build with AI tooling wherever that is faster and better. That way my time goes to the choices that matter: the right solution, the right order, the quality.
03

Controls are code

House rules, tests and review criteria live in the project itself. Every change passes through them automatically: tests run, a review checks the rules, and I judge the end result.
04

After going live too

Daily health checks watch over your application. If something goes wrong, you hear it from me — not from your users.
the difference

Why this approach works

topic how it usually goes how I do it
Change Everything switched at once One process at a time, each reversible
Speed Months of building in silence AI-accelerated, something working every week
Quality Review when there is time Tests and review on every change
After going live Hope it keeps working Daily checks that raise the alarm
Contact Through an account manager Straight to the builder
rates

Two clear services

the entry point

Technical review

€6,000

Know in three weeks where your software stands, with a report and roadmap.

  • Codebase, architecture, security and processes
  • Report with priorities
  • One-page roadmap
More about the review
ongoing

Technical partnership

Fixed p/m

Ongoing work on your product and your processes, for a fixed monthly fee.

  • A fixed monthly fee, no timesheets
  • Process automation, AI where it pays off
  • Technical leadership and initiative
More about the partnership

Need something else? An MVP, interim work or a one-off project is always possible, by agreement. Send an email

free 30-minute call

Let's get acquainted

Tell me about your idea. I'll say honestly whether I can help and what the best approach is.

Schedule a call Send an email