Question 1

How long does a sprint take, and what is the scope?

Accepted Answer

Sprints run 3 to 5 days, fully remote, with a fixed scope agreed before we start. A sprint delivers the agreed build and its documentation, not a slide deck. An audit takes 1 to 2 days and delivers written findings and an implementation plan.

Question 2

What is included in a sprint?

Accepted Answer

I design the architecture and implement it myself: automation, API integrations, LLM-based steps and code agents where they fit. I test what I ship and I document how to run it. I do not take over your duties as data controller. Sensitive external actions always require human approval first.

Question 3

Which tools and CRMs do you work with?

Accepted Answer

I can build a CRM integration for HubSpot, and for Pipedrive or Salesforce if the project needs it. I build one integration per tool, not a generic connector. Automation can run on n8n, with the usual email and calendar APIs.

Question 4

How do you handle personal data and GDPR?

Accepted Answer

On a client project I process only the data the task needs. Where that data already lives in your tools, it stays there. I name any processor before I use it. I prefer EU hosting when the tool allows that choice. This is not a promise that every vendor is hosted in the EU.

Question 5

What happens after the delivery?

Accepted Answer

You own the code and the workflows I write for the engagement; what I did not write (the n8n platform, third-party libraries) stays under its own license. I can run a follow-up sprint if you want to extend the work.

Question 6

Which languages do you work in?

Accepted Answer

I work in French, English and German, and my sales background covers the French and German markets. Deliverables and this site are in English; day-to-day communication can happen in any of the three languages.

Legal Notice

Publisher

Director of the publication

Hosting