Answers are built from your website, documents and your tools’ data — with links to sources. Links only to real pages. If there’s no answer, the assistant says so. For a concrete example on a website, read our article “How do you turn your visitors into customers ready to sign, around the clock?”.

Your choice. If the assistant runs on your server, the data stays with you. You also decide which country stores the data and which AI models are used.

For TYPO3 13.4 and 14 we use an MCP server with a dedicated read-only user per site. WordPress, Symfony and PHP connect via API or MCP.

The visitor assistant is read-only and limited to its own site’s page tree. Hidden, unpublished and members-only content is filtered out.

A daily cap per site and per visitor, abuse protection, and all costs per site in your dashboard.

The chat window and the assistant’s answers are in French, German, English and other languages on request.

Migration means moving a website to TYPO3 from another platform, or moving an existing TYPO3 installation to a new version or infrastructure — while keeping the content and functionality intact.

MCP (Model Context Protocol) is a standard that lets an AI securely access your company's data and tools (CRM, database, internal APIs). I build custom MCP servers to connect your systems to AI assistants.

A scripted chatbot answers from predefined scenarios. An assistant trained on your knowledge base understands context, answers unexpected questions, and genuinely guides the visitor — 24/7.

It lets the AI search your documents by meaning rather than exact keyword, so it finds the relevant information even when the question is phrased differently. It's the technical foundation of an assistant that truly knows your business.

Yes — the architectures I build can rely on locally hosted models (local LLM) or on providers that meet your confidentiality requirements, without sending your data to uncontrolled third parties.

Lead qualification, answering frequent questions, document summarization, sorting and prioritizing incoming requests, integration with your existing tools (CRM, emailing, support) — every automation is custom-built around your own processes.

With an audit of your current processes to identify high-value automation targets, then a focused prototype before a full rollout — the same progressive method as for a TYPO3 or Symfony project.

An outdated version no longer receives security patches, works poorly with modern browsers, and gradually loses compatibility with extensions. An upgrade is prevention, not cosmetics.

A minor update (e.g. 12.4 → 12.5) brings patches and fixes within the same version. A major update (12 → 13) changes the core and may introduce breaking changes, requiring more thorough testing.

It depends on the starting version, the number of extensions, the volume of content, and any custom code. We provide an accurate estimate after a free audit.

Yes — migration is carried out on a separate staging environment, and the switch to production happens once everything is validated, with minimal or zero downtime.

We preserve the URL structure, set up 301 redirects wherever addresses change, and monitor indexing after launch.

Symfony fits projects that go beyond what a CMS can offer: complex business logic, specific workflows, multiple integrations. TYPO3 remains the right choice for a content-driven site; Symfony makes sense for a custom application.

Yes — TYPO3 itself is built on Symfony components (routing, dependency injection, console). I also build Symfony microservices that complement an existing TYPO3 site: APIs, dashboards, third-party integrations.

B2B portals, business platforms, applications with complex business rules, dedicated APIs, internal dashboards — any project where a general-purpose CMS becomes a constraint rather than an accelerator.

It depends on the functional scope. An MVP can be delivered in a few weeks; a full platform with multiple integrations takes several months. A precise upfront scoping makes it possible to estimate a realistic timeline.

Yes — it's actually one of its strengths. Symfony's modular architecture makes it possible to add features over time without rewriting what already exists.

Yes, on the same basis as for TYPO3: security updates, monitoring, fixes, evolutions — with the same response-time guarantees.