Case studies

Four projects I have built and supported.

Every project taught me something. Here’s what I built and why it mattered.

4 of 4 case files

  • Fintech & Real Estate

    80%

    fewer production bugs, approximate estimate

    Gridky

    40,000 properties, 12 tax regimes, banking-grade security. When the machine has to be reliable before it can be smart.

  • Architecture & Scale

    9 years

    of continuous organic growth

    PubliSpeak

    From a proof of concept to a microservices SaaS platform, without losing a client or interrupting service. A gradual migration organised around business domains.

  • AI & Innovation

    85%

    compliance with the strictest accessibility standards

    PDF Accessible

    Market solutions promised automation and stalled at 30% compliance. We reached 85% by deciding, document by document, what needed algorithms, symbolic AI or LLM Vision.

  • Platform & Product

    3,000+

    audits completed for 200+ clients

    IpedisConnect™

    Hundreds of companies steering their accessibility strategy from a single platform. The management platform adopted by the leading digital accessibility organisations.

Summary results.

Discuss a similar problem

One study, several situations.

Each row is a situation; a dot marks the study that sheds light on it.

  1. Architecture & tech debt
    • PubliSpeak
    • Gridky
  2. Tech team & organization
    • PubliSpeak
    • Gridky
  3. Delivery & quality
    • Gridky
    • PubliSpeak
  4. Roadmap & tradeoffs
    • Gridky
    • IpedisConnect™
  5. Reliability & security
    • Gridky
    • PubliSpeak
  6. Tech governance
    • Gridky
    • PubliSpeak
  7. Internal tools & data
    • IpedisConnect™
  8. Applied AI
    • IpedisConnect™
    • PDF Accessible

The experience behind these projects.

It started at IPEDIS. Over nearly 11 years, I built multiple products from scratch: PubliSpeak, a paper-document digitization platform trusted by Air Liquide, L’Oréal, Publicis and Groupe Premium; PDF Accessible; and IpedisConnect™. I grew from lead developer to CTO, scaling the product team from 5 to 25 people.

The turning point came when I moved from lead developer to CTO. I knew how to defend a coding choice. I had to learn to defend a decision with people who talk about revenue, risk and growth. An architecture can be elegant and solve nothing for the business. Understanding that changed how I work.

Yanis Ghidouche

Explore my background

Facing a similar challenge?

If one of these contexts looks like yours, we can dig in together. No need to wait until everything is figured out; that’s usually when an outside view helps most.

30minutesLet’s talk