The audit starts with a short conversation, not an invoice.
The call is short, free and shallow on purpose. It works out whether this is a problem I can actually solve, and whether the €450 audit is worth doing at all. Nothing needs preparing beforehand, and rough notes are fine.
The short version of the audit.
The audit runs across the servers, the site, the data and the automations between them. It ends in a written document rather than a meeting. You know the €450 before any of it starts, and it does not move once the work is under way.
From this message to a fixed price.
The audit works out what is wrong and what putting it right would take. What follows is a build or a retainer, depending on what the audit finds and what you can spend, and sometimes it is neither. If I cannot help, I would rather say so in twenty-five minutes than after you have paid for an audit.
I reply the same working day, including to the ones I turn down.
The fee credits in full against a build or a retainer, whichever one follows.
Half to start, the balance on deployment or the agreed milestone. Every quote and every invoice is in euros, never by the hour.
Twenty-five minutes, then you decide.
Pick a time that suits you, and the confirmation carries a Google Meet link. You get a straight answer on whether the audit is worth doing, including the case where the answer is that it is not. If it is worth doing, the scope and the fee come to you in writing before any work starts.
Send a message.
If you already know you want the audit, the calendar further up this page is the faster way in.
Questions this usually comes down to
Something not answered here?
Ask your questionPrefer to talk? The calendar is at the foot of this page.