Skip to main content

Work & proof

Useful cases. No fake logos.

When a project can be shown, it is shown cleanly: context, constraints, deliverables.

Local web presence

Clear refresh to clarify an SMB offer

Context. A local company had a strong offer, but a site that was hard to scan and not reassuring enough on mobile.

Intervention. Content architecture, visual hierarchy, service pages, technical SEO, clear form flow and trust signals.

Impact. A more credible presence, a simpler journey and better-qualified requests.

Proof format

Customer support

AI FAQ assistant framed around real questions

Context. The team repeated the same answers often and wanted to structure knowledge without blind automation.

Intervention. Frequent question audit, knowledge base, controlled answers, privacy limits and human escalation.

Impact. Less friction in conversations and more consistent client answers.

Proof format

Ongoing support

Site + AI maintenance to keep the system useful

Context. A site that performs at launch must stay fast, accurate, secure and aligned with the business as it evolves.

Intervention. Technical monitoring, fixes, content adjustments, documentation and targeted AI improvements.

Impact. A digital presence that evolves without starting from zero every quarter.

Proof format

Confidentiality respected

Sensitive client information stays private.

Documented proof

Each public case must explain context and impact.

No invented logos

Better to be sober than pretend artificial traction.

Want to become the next public case?

We start by scoping the mandate, deliverables and expected outcomes, then decide together what can be published.