Pierre Facq

Pierre Facq Software architect · Staff engineer

Software architecture and AI in production, from decision to code.

New products designed, existing applications taken over, AI integrated where it helps, cloud costs under control. One person accountable, from decision to production.

Based in Mauritius (GMT+4). Remote engagements in English and French.

Published result, AE3 Cloud costs cut to roughly one fifth
Cloud cost index
Before 100
After ~20

Indexed to 100 before the takeover, with equivalent services. Amounts not disclosed.

Three areas of work

Alongside your team, to take over an application or on a defined problem, with the same person from decision to code.

Main stack. PHP / Symfony, React / TypeScript, relational databases and cloud. PHP/Symfony development

Start with an assessment

A defined starting point before a takeover, a redesign or an AI project. A review of the code, infrastructure and costs, conversations with your team, then a written report.

  • Technical risks, ranked by severity.
  • The architecture decisions to make, with their options.
  • A prioritised action plan that your team or I can implement.
Request an assessment

Four products I have been technically responsible for

AE3 · sole developer since the takeover

Taking over an abandoned product and cutting its cloud costs fivefold

Codebase takeover, maintenance, product changes and a hosting redesign, with equivalent services.

Cloud cost index
Before 100
After ~20

Indexed to 100 before the takeover, with equivalent services. Amounts not disclosed.

Read the AE3 case study

ShareAgent · CTO and co-founder since 2023

Valuing a property by voice

The agent’s dictation is transcribed, its features extracted by AI, then compared with listings for sale around the address.

ShareAgent valuation screen: price, range and euro adjustments.
Read the ShareAgent case study

Edunao / Dixeo · staff engineer since 2021

Generative AI in learning platforms

A complete course generated from a simple request, and an AI tutor for learners, with responsibility for APIs, data and operations.

dixeo.com home page with the course generation field.
Read the Dixeo case study

Independent in delivery. Clear in collaboration.

You speak directly with the person doing the work. I collaborate remotely from Mauritius, in English or French, with a communication rhythm we agree together.

Read my CV (PDF)
  1. Understand before changing

    We clarify the need, product constraints and how your team works. I get familiar with the codebase and existing environment.

  2. Work with clear priorities

    We agree on scope and useful check-ins. I develop, test and explain technical trade-offs as the work progresses.

  3. Leave a maintainable foundation

    Code, decisions and operational information stay available to your team. The outcome should be something you can keep building on.

Trust is built over time.

Feedback from my work with GRDF, published on Malt.

“Pierre Facq listened to our needs and gave us sound advice throughout the development of our tool.”
Yannick, GRDF · November 2021 · Translated from French Read the reviews on Malt

Questions before we start

What kinds of engagements do you take on?

Three formats: ongoing support for your team, an architecture assessment with or without implementation, or ownership of a defined piece of work (takeover, AI, performance). Scope and pricing are agreed around your needs.

How does remote collaboration work?

I work remotely in English and French. We agree on collaboration hours and check-ins with your team. Mauritius is UTC+4, two hours ahead of mainland France in summer and three in winter.

Who do we contract with?

Services are provided through my company Prismyq Ltd, based in Mauritius. We clarify scope, contractual arrangements and any requirements before starting.

How do we get started?

Send me a few lines about your application, what you need and any constraints. We can establish whether my experience fits, then discuss scope, timing and budget.

Let’s talk about your application

A few lines by email is enough. To make the first reply useful, include:

  • the application and its stack;
  • the problem to solve or the goal;
  • a deadline, if there is one.

WhatsApp: +230 5944 0094, messages only