Software consulting for your next decision.

I review architecture, code and technical proposals for businesses in the Netherlands and Aruba. Bring the decision you need to make and the material behind it. We agree what to review, a limit on hours and the findings you need back.

Start a project

When a technical review helps.

You may be choosing a framework, deciding whether to rebuild or trying to understand a risk in an existing system.

A review gives you a written assessment and a chance to discuss the options before committing time or money.

We agree a focused scope for a single question, or a regular arrangement for ongoing work.

What you can bring here.

Architecture review

A review of your system or proposed architecture, with findings, trade-offs and recommended next steps.

Code audit

A review of maintainability, tests, dependencies and common security risks. Useful before a handover or further investment in a codebase.

Build, buy or extend

A comparison of available software and a custom build, including cost, integrations and limitations.

A second opinion on a quote

A review of a technical proposal: whether the scope addresses your needs, what the estimate covers and which questions remain open.

Hiring support

Help defining a developer role, reviewing technical experience and preparing interview questions or practical assessments.

Ongoing advice

Reserved hours for code reviews, design discussions and technical questions, agreed around your needs and my availability.

What it costs.

Billed by the hour. A focused question can start with two to ten hours, estimated before work begins. Eight billed hours cost €560; they can be scheduled across agreed sessions.

€70

per hour

Excl. VAT. Quoted for an agreed scope.

You get an estimate in hours. Billing reflects the hours used; additional work needs your agreement. An eight-hour billing unit does not imply weekday availability.

What determines the price

Whether it is a fixed-scope audit or an ongoing arrangement
How much of the codebase is in scope
Whether the output is a written report or working code

How it runs.

Step 1

The actual question

We agree the question, the information I need and what you should receive from the review.

Step 2

Read, and ask

I review the code and documentation, and discuss the system with the people who use or maintain it.

Step 3

Written findings

You receive written findings, ordered by impact, with recommended actions and the limits of the review.

Step 4

Walk through it together

We walk through the findings and discuss which actions make sense for your team.

What is and is not in it.

Included

A written report you can circulate
Findings ranked by consequence, not by label
A walkthrough session with the team
Direct answers, including the unwelcome ones
Follow-up questions after delivery

Not included

Implementing the recommendations, unless agreed separately
Formal penetration testing or certification
Managing your team or running your sprints
A report that says what you hoped it would say

Before we start.

Will you tell us the honest answer if it is not what we want to hear?

Yes. I explain my findings and the evidence behind them, including when keeping the current approach seems sensible.

Do you need access to our codebase?

For a code review, I need read access. We can agree confidentiality terms first. Some planning questions can be answered from documentation and a conversation.

Can you review work another developer or agency built?

Yes. I review the system and explain the options for continuing or changing direction, without making assumptions about the previous developer.

We do not have a technical person internally. Is that a problem?

No. I write the findings for the person making the decision and walk through any technical terms with you.

Can this turn into a build?

Potentially, depending on the scope and my availability. You can use the review with your own team or another developer.

Tell me about your project.

Tell me what you're working on. I'll tell you how I'd build it, what it would take, and whether I'm the right person for it. No obligation.