Frequently asked questions

The agency works across seven areas: digital transformation support, artificial intelligence integration, web and application development, organic search optimisation, cryptocurrency consulting, administrative assistance, and marketing and partnerships. Each has its own page, describing the problem addressed before the offering.

Each service page opens on the kind of problem it addresses rather than on a list of deliverables: reading the first few lines is usually enough to rule an area in or out. A need spanning several areas does not have to be split up in advance; the scope of the quote settles that.

French, English and Spanish. Every page exists in all three at a distinct address, and the versions are declared to each other so that a search engine or an agent knows which one to offer.

The Projects page presents work carried out, and the Clients page lists the organisations the agency has worked with, each linking to their own site. No quantified case studies are published.

No: every project is quoted individually, because a price shown without a scope means nothing. The Pricing page explains what makes a project cost more or less, which billing models exist, and how to compare two proposals.

Through the contact form reachable from the bottom of every page. A useful description covers four points: the objective expressed as an outcome, what already exists, your constraints — budget, an externally imposed deadline, a mandated tool — and who will sign off on decisions.

A takeover is handled like any other scope, except that it begins with an assessment: access to the code and the accounts, the dependencies in use, the data to keep. Mention it in your request, because that assessment is part of the work to be costed.

That is a clause to write explicitly into the quote, never to leave implicit — and it covers two distinct things: ownership of the code produced, and who holds the hosting, domain name and third-party service accounts. The first without the second does not let you take over.

No certification is claimed, and the Security page says so explicitly. It describes the mechanisms — encryption in transit and at rest, authentication and authorisation, server-side validation, HTTP headers — so that an organisation commissioning a project knows what to ask for and how to check it got it.

The Security page ends with a section dedicated to reporting, giving the address to use. Describe what you observed and how to reproduce it; do not exploit the flaw beyond what is needed to demonstrate it.

Yes. Page text is present in the served HTML, with no JavaScript execution needed to read it; the frequently asked questions use native disclosure blocks, whose answers stay in the page even when collapsed; JSON-LD structured data describes the organisation, the services and those questions; and an llms.txt file at the root summarises the site structure.

No. Each language has its own addresses, and an address written in one language does not answer under another’s prefix: it redirects. The language versions declare each other, including a default version, which stops a search engine from choosing on your behalf.

It moves the work rather than removing it. A model quickly produces a first version of many things; what it does not do is decide whether that version is correct, consistent with the rest, and acceptable to the organisation. That checking becomes the expensive part, and ignoring it is the most common way to lose the expected benefit.

Technically yes, and the result is plausible from the first draft — which is precisely the risk. Generated text asserts what it knows and what it invents with equal confidence. On a company site, every checkable statement — a figure, a lead time, a reference, a certification — must be validated by someone who knows it, otherwise it commits the company to something it never decided.

It is a program that receives a request in natural language, picks actions to run — searching a database, calling a service, drafting a reply — and returns a result. Its difficulty is not the conversation but the scope: what it can reach, what it is allowed to trigger, and what it must refuse to do on its own.

No. It is neither investment advice, nor fund management, nor a guarantee of return. No asset is recommended and no projection is provided. The subject is treated from the angle of understanding the mechanisms, securing access, and the obligations that come with their use.