Work · 9 case studies

Proof files

Real projects, delivered directly or inside a partner’s teams for its end clients. Each case study gives the key points in thirty seconds, then the story, the proof and the limits.

Filter case studies
Santécie2024-2026AI · Project that integrates AI or trains teams to use itIn production

Automating after-sales returns to manufacturers, with a trace of every request

Santécie’s after-sales return files are routed to the right manufacturer forms and filled automatically, with an audit trail for every request.

Stake
Every after-sales return must reach the manufacturer on that manufacturer’s own form; copying files across by hand took time and invited costly mistakes.
Impact
Data entry becomes configuration: at least 500 hours avoided per 10,000 requests, and a failed request is replayed without redoing the batch.
Through a partner
  • NestJS
  • Prisma
  • Pinia
  • TypeScript
Read the case study

Reading guide

How to read a case study

Every case study fits in five lines, from the stake to the limits; the narrative develops each one. The limits are part of the proof.

  1. Stake

    What was at stake for the client, in one sentence.

  2. Mechanism

    How the system produces that change.

  3. Proof

    What demonstrates it: measurements, usage, material available on request.

  4. Impact

    What it brings to the business, in time, risk or quality.

  5. Limits

    What is not demonstrated, or still needs work.

Let’s talk about what AI could change for you

A 30-minute discovery call, by video and with no commitment, to talk about your project, your constraints and the best next step.

contact@mc-stud.io