SYSTEM

Your business runs. Even when you don't.

SERVICE · '26★ FEATURED

Requesa - system

Traditional business contact forms capture basic information but fail to qualify leads effectively. Prospects abandon lengthy forms, while businesses receive vague inquiries lacking context for meaningful follow-up. This creates a qualification bottleneck where 70% of leads require multiple back-and-forth exchanges before reaching actionable insights, leading to delayed response times and lost conversion opportunities.

Next.js 16TypeScriptSupabaseAnthropic APIStripeQStash

'26

N°02

Ecnarf - system

The site had to prove the studio's own competence — every technical choice is part of the portfolio. The brief: build a fast, editable, privacy-respecting site where the studio controls its content, captures leads, and demonstrates its own product (Requesa) — without over-engineering a portfolio site into a SaaS.

RequesaSanity CMSUpstash RedisUmami

E-COMM · '26

N°04

Joy Julius - system

The technical infrastructure reflects the same philosophy as the visual: precision, restraint, intentionality. We didn't choose tools because they were trendy—we chose them because they matched how Joy thinks about running a business. The gaze is editorial and mercantile at once. The website is a curated space, not a database. Transactions are frictionless, not theatrical. Customer data is secure and owned, not third-party-dependent. Performance matters because respect for the viewer's time is respect for the work itself.

SanityStripeSupabaseResendUmamiCloudflare R2

'26

N°03

France Ola - system

France Ola is a publication that asks more of its infrastructure than most photographer sites. It needs to hold a structured content model where every species carries its own anatomical details, every photo its location, every expedition its narrative; it needs to deliver a three-dimensional interactive atlas, a conversational assistant that searches the archive in natural language, a licensing shop that issues signed download links and PDF certificates after payment, and an editorial journal — all from a single codebase, hosted seriously, with no third-party plugin assembling the seams. Off-the-shelf website builders collapse the moment the project's ambition exceeds their templates, and stitched-together SaaS solutions tend to leak their visual register into the site they're plugged into. The problem was to find a stack where every component would respect the editorial tempo of the project all the way down to the email confirmation.

RequesaSanityCloudflare R2StripeResendAPI Claude

COMMERCIAL · '24

N°06

Edacy - System

I approached systems as invisible design. My goal was not to add tools, but to remove friction. Every system had to serve a specific purpose within the learner journey: discover a program, apply, schedule a conversation, receive updates, access content, or stay connected with the community. I viewed each integration as part of a larger experience. When done correctly, users should never notice the systems themselves — only the simplicity of the journey.

FormspreeGoogle FormsCalendlyGoogle Analytics

SERVICE · '25

N°05

Soin-reflex - system

I approached the digital ecosystem as an extension of the patient experience. Every tool was selected to reduce friction, increase trust, and make the path from discovery to appointment as seamless as possible. The objective was not to add technology, but to make technology disappear behind a simple and reassuring experience.

OneDocGoogle MapsGoogle Apps ScriptGoogle Sheets CMSElfsight Reviews

STARTING A SYSTEM PROJECT?

The invisible infrastructure that makes everything work.

Set up once, running always.