Webdex
Contact us

About

Julien Frisquet: twenty years in software, AI-augmented engineering leadership, and hands-on delivery backed by a network of trusted collaborators.

Julien Frisquet is an engineering leader with more than twenty years in software. He leads an AI research and development function across three distributed teams of around twenty engineers, turning ideas into validated prototypes. He introduced the AI-augmented engineering practices those teams use — LLM agent harnesses, MCP servers, agentic workflows and shared tooling configuration — and every AI-assisted change still passes a human review gate. Delivery is materially faster without that review becoming optional.

Webdex is the consultancy he runs. Julien leads the work and remains the main point of contact, from the first conversation through handover. The work is deliberately practical: hands-on delivery inside the client’s repository and team, from architecture to production and the operations that follow a release — code, pipeline, runbook and the decisions that keep a system maintainable once live.

When a project needs more hands, or expertise outside his own, he brings in trusted collaborators from a network of engineers, data and AI specialists, designers and domain experts. They work to the same standards and review gates, with Julien still the person you talk to. Julien works with clients and teams in English and French.

A wider network

Webdex is deliberately small: Julien plus a network of people he trusts, assembled around the problem.

  • One lead, one point of contact. Julien scopes the work, leads delivery and stays your main point of contact. Specialists join the work; they do not replace the person you are talking to.
  • Specialists when the work needs them. A larger build may need several engineers; a migration may need a database or platform specialist; a product may need design or domain expertise. Those people are brought in for the work they are best placed to do.
  • The same standards apply. Collaborators work inside the same repository, review process, definition of done and handover discipline. The engagement does not become a hand-off to a different team.
  • Agreed before it starts. Who is involved, what they own and how the team is shaped are agreed with you before work starts. If the work is best delivered by Julien alone, it stays that way.

What Julien works on

Selected work on public products

Products Julien has helped build and run:

  • Wolfram|Alpha — led its evolution: modern CI/CD, a React and Spring Boot modernisation, moving delivery from flat files and Java WARs on VMs to Docker on self-hosted Kubernetes. Release cycles went from months to about five minutes.
  • Wolfram Cloud — maintained the monolith, built the React file manager, and prototyped services such as Google Drive integrations.
  • Passport (Euromonitor International) — a data ingestion and delivery platform at around a million operations an hour, engineered to a five-nines-plus availability target and run without a defect for 18 consecutive months. Led three teams of 25 engineers — hands-on at the start, later focused on architecture, system design and mentoring tech leads.
  • QuickBooks UK (Intuit) — PSD2 and Open Banking integrations with ASPSPs across EMEA. Sole engineer on a migration moving 300+ financial institutions, including configuration and eIDAS certificates: 100% success in the UK and 98% in France, three weeks ahead of the Brexit deadline.
  • Transformers Universe and RuneScape — online game services: billing and third-party integrations on RuneScape, plus tooling and services for Transformers Universe.
  • Warhammer Online — European player-support operations: team leadership, QA of support tooling, and a multi-game knowledge base.

Background

Julien has delivered device-health monitoring for stadium loudspeaker systems that must broadcast evacuation alerts, and led the transformation and optimisation of an AI-powered engine serving around ten million users a month.

How engagements run

  • One point of contact throughout, with trusted collaborators brought in when the work needs them.
  • Work in short increments, with something reviewable every week.
  • Decisions written down rather than remembered.
  • A standing channel with the team, so updates do not need a meeting.
  • A handover that leaves nothing locking the client in.

The engagement models, cadence and definition of done are set out under how an engagement runs.

Elsewhere