Transparency and handover
Work with me, and you are never held hostage
Most developers and agencies win by making you depend on them. I win the opposite way. Everything I build for you lives in one place, is documented to the line, and can be handed to your own team or another agency cleanly, at a moment’s notice. That is not a risk to me. It is the whole point.
The promise
No lock-in, ever
Lock-in is how the industry keeps you paying. I wrote the opposite into the contracts.
You own it
On completion the intellectual property, source code, credentials and documentation are yours. No hostage taking, no ransom at the end.
Continuity if I disappear
If I ever become unable to work, you get an irrevocable, free licence plus access to the repositories, docs and credentials. You are never locked out, even in the worst case.
Clean exit
Because everything is documented and reproducible, moving to an in-house team or another agency is quick and calm, not a hostage negotiation.
One accountable person, and a plan for when you outgrow that
I play a central role in every project and I take responsibility for it: the architecture decisions, the code, the numbers, the results. There is no account manager between you and the person doing the work, and I do not disappear the moment a better offer turns up.
Central, not a middleman
You talk to the person who builds it, runs it and answers for it. Decisions get made in the meeting, not relayed to someone else afterwards.
I stay
No vanishing act when something shinier comes along. The continuity clause covers the worst case; my word and my track record cover the rest.
Built to hand over as you grow
Once you have grown considerably and the workload gets massive, parts of my role move in house. Your team takes the day to day, I take the challenge that matters at that stage of the growth cycle. That is the setup working as designed, not a breakup.
From a feature request to on-time delivery, without chasing anyone
You or your project manager raise a feature request in the portal. It comes to me for an honest estimate. Then the AI places it at the right point in the plan so every milestone and deliverable still lands on time. You watch it happen, you do not chase it.
You raise a request
Feature #204: bulk member export, with the goal and acceptance criteria.
It comes to me
An honest estimate: 8 hours. No padding, logged to the project.
AI schedules it
Slotted at the optimal point, so the release and milestones still hold.
Delivered on time
Built test first (TDD and BDD), so it ships clean. Tested and accepted.
Everything in one place, nothing lost
One calm home
A private client portal, not a folder graveyard. Contracts, documents, decisions, releases and your email history, all in one place.
- Every contract and annex, numbered and versioned
- Full correspondence archived per project
- Your environments, invoices and sub-processors listed
Real cost transparency
You always know what you are paying for and why. No padded retainers, no mystery line items.
- Published hourly rates, the same for everyone
- Every decision and change request logged and priced
- A clear line between a bug I fix free and a feature you asked for
Documented to the line
Not "we have some docs". Every feature mapped to the exact files, classes and methods, plus architecture notes, tests and release notes.
- Feature to code map, so any developer can take over
- Automated tests as living documentation (TDD and BDD)
- Release notes and a per-repository warranty
Evidence at the press of a button
When an auditor, insurer or your own board asks, you do not scramble. One click produces the lot.
- Immutable audit log of who did what and when
- Documents, decisions, releases and email trail
- Offboarding record and a signed deletion certificate
Documentation your next team can start from on day one
The AI helps me keep the documentation genuinely complete: written prose for the manual, plus every behaviour pinned down by TDD and BDD tests, plus a full map from feature to code. If another team ever takes over, they are productive from day one, not month three.
A new developer is productive from day one.
- FeatureConsent ledger export for auditors
- FixCheckout total rounding on multi-item carts
- DocsUpdated architecture diagram and ROPA
Compliant wherever your customers are
Here is the part most agencies get wrong: the law that applies follows where your customers live, not where I live. So I do not just wave "GDPR" at you. I align the way your data is handled to the regime that actually governs it, wherever your users are.
| Where your users are | The regulator | The law |
|---|---|---|
| Germany | BfDI and the state authority (Landesdatenschutzbehörde) | GDPR / DSGVO, BDSG |
| Austria | Datenschutzbehörde (DSB) | GDPR / DSGVO, DSG |
| Switzerland | FDPIC (EDÖB) | revFADP (revDSG) |
| United Kingdom | ICO | UK GDPR, Data Protection Act 2018 |
| Ireland | Data Protection Commission (DPC) | GDPR, DPA 2018 |
| EU (any member state) | The national DPA, coordinated by the EDPB | GDPR |
| United States (federal) | FTC, and sector regulators (HHS OCR, and others) | Sectoral: HIPAA, GLBA, COPPA |
| United States (states) | California CPPA and Attorney General, plus other state AGs | CCPA / CPRA, VCDPA, CPA and more |
| Canada | OPC, and Quebec’s CAI | PIPEDA, Quebec Law 25 |
| Australia | OAIC | Privacy Act 1988, APPs |
| New Zealand | Privacy Commissioner | Privacy Act 2020 |
| South Africa | Information Regulator | POPIA |
| Singapore | PDPC | PDPA |
I align my processes to the standard each of these regulators expects. I do not claim to be certified or approved by them, because you do not need theatre, you need it done properly.
The difference
The honest contrast
This is what "working cleaner than a big agency" actually means.
The usual agency
Working with me
Boring for the right reasons
No drama, no lock-in, no surprises. Just clean work you could hand to anyone tomorrow, and the paperwork to prove it. If that sounds like the standard you have been looking for, let’s talk.
Start a conversation