The standingpractice.
Eight disciplines, one principal. A small directory of services for European businesses that prefer to be modernized rather than disrupted.
We treat software the way a good firm once treated letters: with patience, with craft, and with the assumption that the work will outlive the briefing.
ost of what passes for digital transformation is a posture — a deck, a vendor, a slogan. Our practice is older in temperament than in years. We read the business before we write the system. We prefer fewer dependencies, fewer meetings, and fewer surprises.
The eight services collected in this issue describe how we work. They are not a menu. They are the shapes a single, careful engagement can take — chosen after the briefing, never before it.
Every engagement begins with the technical audit. Whether you commission the report alone, or take it as the first chapter of a longer relationship, it is the same document, written with the same care.
The TechnicalAudit.
“Your code works. But is it safe? Four areas, one report — written for both the developer who will act on it and the investor who will read it.”
Standing offer · By appointmentArchitecture
How the system is organised, where the load lives, and what will fail first under growth.
Security
What an attacker would find on a Tuesday afternoon. What your insurer would find on a Wednesday.
Code Quality
Readability, test coverage, key dependencies, the bus-factor of the people who built it.
Operations
Deployment, observability, incident response, the cost of running what you have built.
A report your developer can act on.A report your investor can read.
- DURATIONFive to seven business days
- FORMATPDF report · ~30 pages · executive summary
- DELIVERYWalked through in person or by call
- FORFounders before fundraising · Investors before signing · Boards before a build
“Get clarity before you ship — or before you sign.”
Read the audit pageSeven practices.
Beyond the audit, seven standing services — taken alone, or composed into a longer engagement after the briefing.
Work withagencies.
Some projects require a careful technical hand alongside a creative or strategic team. The practice works with agencies that value a named principal — not a vendor pool — who takes responsibility for what is built and stands behind it.
Principal-led
You speak with the person doing the work. No account manager between the brief and the code.
European market fluency
Clients and agencies across DE, FR, IT, ES, PT and the UK. Familiar with the regulatory and commercial context.
Discretion as standard
Your client relationship stays yours. The practice operates as a quiet extension — no co-branding, no unsolicited contact.
How the engagement runs.
Every project moves through five stages. Slow at the start, deliberate throughout — so that the speed at the end is earned.
I
Inquiry
A short letter or call. We confirm fit, scope and timing — or recommend someone better suited.
II
Briefing
We sit with the brief in person or by call. The aim is to understand the business, not just the request.
III
Proposal
A written proposal: scope, fee, milestones, named risks. Plainly worded, signed by hand.
IV
Engagement
The work itself. Weekly notes, transparent invoicing, no surprises. You speak with the principal, not an account manager.
V
Handover
A complete record, ownership transferred, and a standing line of contact for what comes after.
Begin the
conversation.
Write a short note about the work and the timing. We reply by hand, usually within two business days.