Work

No logo wall. Just what we have built.

Does Qanat have case studies?

Not yet, and this page says so rather than borrowing someone else’s. Qanat is a new studio. What it has is an engineer with a live B2B platform to run and shipped products behind him. Every entry below states plainly whether it was a Qanat engagement, an employer platform, or a personal product.

What you will not find here

Client logos we have no right to show
Testimonials nobody said
Metrics we cannot point at

The first real case study goes up when the first client says it can.

MyHealthyOffice

A Dubai B2B platform serving corporate clients across the UAE.

RelationshipAlexandre is CTO. This is the day job Qanat grew out of, not a Qanat engagement.

The constraint

Running engineering for a B2B platform in the UAE means living with the things this site keeps naming: procurement cycles, integrations with systems you do not control, and the gap between what a demo shows and what survives a real operating day.

What was built

Engineering leadership on a live B2B platform with paying corporate clients
The buying-side experience that shapes how Qanat scopes and quotes

Next.jsTypeScriptPostgreSQLAWS

This site

Fifty pages generated from typed content modules, on Cloudflare Workers.

RelationshipBuilt by Qanat, for Qanat. You are looking at it, which makes it the one piece of work here you can inspect yourself.

The constraint

A studio site that argues for scoping discipline has to be built with some. Every page, sitemap entry, JSON-LD graph and llms.txt line derives from one set of typed content records, so adding a project type generates its pages rather than requiring anyone to remember to.

What was built

Content-driven architecture: adding a capability generates its pages, schema and internal links
Answer-engine layer — per-page JSON-LD graph, llms.txt and llms-full.txt, crawlers allowed explicitly
Leads written to a database before the notification email, so a bounced message cannot lose an enquiry
Deployed on the Cloudflare Workers free tier, which permits commercial use where Vercel's Hobby plan does not

Next.jsTypeScriptTailwindCloudflare WorkersD1

RecipeMe

A published Android app with subscription billing.

RelationshipAlexandre's own product, built and shipped end to end.

The constraint

Store billing is where most first mobile builds quietly break. The failure modes only appear on real devices against real store accounts, which is exactly the class of work a demo never covers and a cheap quote never includes.

What was built

Native Android build and release pipeline
Google Play subscription billing, tested against real purchase failure paths

KotlinAndroidGoogle Play Billing

Want a reference on any of it? Ask on the call. Alexandre Arnaud takes it, and it is his own work being discussed.

Start here

Want the same standard on your project?

A scope call, then a written scope and one fixed price against it. 20% of that price is held back until you accept the finished build, and the scope is yours to take elsewhere either way.

Who reads it: Alexandre Arnaud, Founder & Engineer. Not a coordinator, not an inbox.
What happens: A 20-minute call to pin the outcome, then a written scope and one fixed price against it.
What it costs: Nothing to get scoped and quoted. The quote is free and the scope is yours to take elsewhere.