One person responsible for your tourist office's digital side, a few days a month.

Directors of small tourist offices and comparable public bodies with no IT department, who depend on a supplier for their website, their accounts and their tools. The contact is the director or their deputy, not an IT department. Other organisations may read this page and call; it is written for these directors.

A package has a scope, a duration and a price fixed before it starts. It answers one specific question and ends with a deliverable and the procedures to keep it alive. The fractional digital direction is a monthly engagement, three months minimum: a few days a month to keep the website, the accounts, the suppliers and the digital decisions of an organisation with no dedicated lead running. In both cases, the price is written in the note that follows the first call.

I deliver the measurement, the text of the statement and the plan; your organisation publishes them under its own name, like everything that appears on its website. What I sign is the measurement report the statement rests on. In an organisation of this kind, this question held up a statement for months; it is settled in one line in the note.

An attestation is not a grade. The auditor measures your home page with a public tool and sends you the result; do it before they do. What I provide: the measurement before and after, same tool, same protocol, attached to the attestation. Without a measurement attached, I do not sign an attestation.

It is common, and it is the first risk. The first month of an engagement is used to establish who holds what and to bring each account back into your organisation's name, with the register. Nothing stops during the transfer. At the end of any engagement, the accounts are yours; that is the rule here, including when the supplier is me.

For an organisation under an ongoing engagement, the team has an address and a reporting procedure, and the fix is part of the month. For others, say so in the subject line of your message. Same-day answer during business hours, a twenty-minute call to qualify the failure, then a fixed price for a first intervention with a capped scope, sent in writing before any work, with what is covered, the validity date and the VAT treatment. The fix is made and documented. Anything beyond that first intervention goes through the usual written note, which also says what caused the failure and how to keep it from happening again.

Yes, for most routine requests: a news item, a listing, an events calendar, a newsletter. What is usually missing is the written procedure, the permissions that go with it, and a place where a mistake breaks nothing. In an organisation of this kind, the team says in so many words that it is afraid of messing things up; nobody has given it permission. Every engagement ends with the procedures for each role.

Because the website depends on extensions and settings nobody follows, and an automatic update overwrites one of them. A simple website depends on fewer things; that is the first remedy. When the existing website stays, a verified backup before each update and a test environment are part of routine administration.

Every subscription is taken out in your organisation's name and paid by it. When that is not the case, the register flags it and the transfer is scheduled, with the date on which the invoice changes name. No tool is bought in your name without a written decision from you.

A public body pays through its treasury, with a delay, and closes its accounts at year end. The written note is therefore followed by a purchase order from your organisation before work starts, and invoices are issued at the pace and in the form your treasury requires. This protects both sides and avoids payment reminders.

The tool is set up in a few days. A public body's payment collection circuit, on the other hand, is decided with your accountant and your supervising authority, and it determines everything else: refunds, payouts to partners, the till, terms of sale. That is where I start, and it is what is missing when refunds are done by hand and the till does not balance.

That is what it is for. In practice, it takes access nobody has asked for, an import that runs every day and a person who checks in the morning. The diagnostic maps what exists and what is missing; the import itself is priced separately in the note.

I work exclusively with Claude (Anthropic) for automation, documentation and corpus preparation. No client data is passed to an AI tool without prior written agreement on what is passed and why. The rules of use I propose to clients are the ones I apply myself.

Remotely, from Varna in Bulgaria, by video call and in writing, for clients in France and across Europe. On-site work is decided case by case.