Frequently asked questions
The questions I hear most often, answered one by one. If yours isn't here, ask the chat or write to me from the contact page.
You mention GTM Engineer: what is it, and is it your job title?
It is not my title, it is a way of working I practise. I am an entrepreneur, a salesperson by nature and an engineer by method, and I use AI and automation to turn service excellence into systems. A GTM Engineer (Go-To-Market Engineer) designs and installs the systems that move a prospect through to a sale, then a client through to loyalty: a first reply within minutes, qualification, appointment booking, follow-ups, case tracking, handover to the salesperson. For a company, it changes where revenue leaks unnoticed: the request left waiting, the quote never chased, the appointment nobody attended. Those leaks become visible, measured, then handled by a system instead of resting on the team's memory.
Will you replace my salespeople?
No. The salesperson keeps the relationship, the negotiation and the decision. The system takes what gets lost for lack of time: the first reply, the follow-ups, the appointment booking, the case tracking. The salesperson receives the gathered context and a proposed next action; they decide. Every sensitive decision keeps a human owner and an explicit escalation path.
AI consultant, automation agency or you: what's the difference?
The AI consultant starts from the technology and recommends. The automation agency sells hours and workflows on demand. I start from the customer journey and the pipeline: which journey loses requests, where and how many. I build the system, install it in your tools, then operate and measure it. What can't be measured isn't promised.
Do you work with individuals?
No. I work with B2B companies and premium, relationship-intensive businesses: dealerships, firms, brands where the quality of client handling makes the sale.
Which sectors do you cover?
My initial territory: acquisition, sales and client relationships in businesses where advice and appointments decide the sale. My method is horizontal; the entry point is always one precise journey, never a whole sector.
Do you have clients already?
I started recently. I'm currently working on several projects, either under construction or being deployed. Results and names are published on this site only once systems are delivered, and only with the agreement of the partners involved.
In the meantime, what I can show is verifiable: the systems I've built and operate myself every day, and this website, which is itself a demonstration of the product.
What exactly are we buying?
A system bounded to one journey in your pipeline, neither hours nor a subscription to yet another tool. It always has the same skeleton: a trigger event, a source of truth, visible state, a human owner, a next action, a clean escalation path and a measurement. Installed inside your existing tools, measured, then operated.
What is an "AI execution system"?
The name I give the category: an operational layer between your existing tools and human work. It follows a case end to end and triggers the right action at the right time, with the necessary context and explicit human control. What sets it apart from a chatbot on a website or yet another dashboard is what it does: act, follow up, escalate.
Couldn't we just build this ourselves?
Part of it, yes. An assistant wired to an inbox, a no-code scenario put together internally: that can be done in-house, and it helps.
The difference shows up when volume rises and the awkward cases arrive: the request with two intents, the one outside your scope, the one that looks like a request but isn't. You then need a guardrail able to say "I don't know" and hand back control, a trace of what happened, and a measurement. Without those it isn't a system: it's a demo that works until the day it doesn't, with nobody noticing.
What does it cost?
I don't publish prices: every system is quoted after scoping, because cost depends on the journey addressed, integration complexity, volume and the level of service expected.
What is fixed is the structure: a paid Baseline & Blueprint ending in a firm quote, then a pilot at fixed price and fixed scope. No open-ended billing without a bounded result. The number is discussed in person: describe your situation and I'll answer precisely.
How long does it take?
It depends on three things: access to data and tools, availability of the internal sponsor, and the complexity of the journey. I publish no standard timeline; I commit to a firm one, in writing, at the end of the Baseline & Blueprint, together with the quote.
Our teams won't adopt it.
That is risk number one, and it is treated as such. These systems don't ask teams to change tools or methods: they prepare the work (context gathered, request qualified, next action proposed) and leave the decision to the human.
User training is part of the pilot. And a system a team works around is a badly designed system: it shows up in the metrics, and it gets fixed.
Do we need to change our CRM / DMS / ERP?
No. The system sits between your existing tools, with minimal integrations in a first pilot. Replacing your existing software is never a prerequisite.
What happens to our data?
Systematic minimisation: only the data needed for the journey at hand is used, with a defined purpose and retention period. No sensitive data collected without justification. Human control and traceability are part of the product.
Do you work with our competitors?
Confidentiality is absolute: a client's data, rules and specifics never leave their system. Market exclusivity, on the other hand, is negotiated in the contract, depending on scope, territory and commitment.
How will we know it works?
Through the journey's direct metrics, defined before the pilot: time to first reply, contact rate, qualification, attended appointments, quotes followed up. Effects on revenue, reviews and loyalty are observed afterwards, never promised without defensible causality.
What if the pilot delivers nothing?
Scope and acceptance criteria are written before anything starts, and the pilot is designed to be stopped cleanly. That is also the point of a measured baseline: no pilot is launched without a metric that can move, and without knowing what it is compared against. If the numbers don't follow, I say so.
What if you disappear?
A delivered system belongs to the client: it runs in their tools, with their access. Everything that makes it work is documented (operating procedures, failure cases, escalations), because a system only one person's memory can operate is not deliverable. Skills transfer to internal teams is part of the Managed System when the client wants it.
Where are you based? Do you work on site?
Marseille, France. Work is mostly remote, with travel when the ground requires it: scoping, key reviews, moments that matter. Terms are set during scoping, depending on the scale of the project.
What is this website, exactly?
A demonstration of the SiteVox product: a website that answers visitors' questions from a living knowledge base. The same system can be deployed for your business, with your data.