FAQ
Questions a CEO asks first.
What about GDPR and our data?
Claude Team comes with data-processor terms. Before anyone gets a seat, I write down what your admins can and cannot see and what may be pasted where. If Team’s terms don’t cover what your lawyer needs, the next step is Enterprise.
Who owns the code and the workflows?
Section 10 of the handover doc, “Reusable parts: who owns what”, sets it out for your build: any generic modules I reuse, what you may do with them, and who owns the rest. The build runs in your accounts or on your server.
What happens if you’re unavailable?
My standard is the 11-section handover doc on the downloads page: an engineer who didn’t build it can deploy, run, fix and change it. A dry run by a non-builder is part of that standard; 0 of my 3 delivered docs has had it yet.
How do payment terms work?
Fixed prices in euros, net of VAT, agreed before work starts. The sprint is €2,400 and is credited towards a build signed within 30 days. A build’s payment schedule is set in its fixed-scope agreement.
Remote or on-site?
Remote by default, from Warsaw. Discovery sessions and training can be on-site; I agree that with you when I scope the work.
What does the handover include?
The 11-section doc, the code or workflows in your accounts, training for the people who run it, then a measurement at 30 and 90 days. The template is free on the downloads page.
Something else? Ask it on the call.