Full-stack · React · Next.js · TypeScript

Hire one developer
for the whole stack.

React and Next.js on the front, Node and PostgreSQL behind it, deployed and monitored — by one senior engineer instead of a front-end contractor, a back-end contractor, and a project manager translating between them. Six years, sixteen products live in production, four of them my own.

What full-stack means here

Four layers, one person accountable for all of them.

Most expensive bugs live at the seams between layers. When one engineer owns every side of the seam, they get found in an afternoon instead of in a thread between two agencies.

  • TypeScript
  • React 19
  • Next.js (App Router)
  • Node.js
  • PostgreSQL · Prisma
  • Tailwind CSS
  • WebSockets
  • Stripe · PayPal
  • Algolia
  • Docker
  • Hetzner · Dokploy
  • Vercel

The receipts

Shipped systems, each with a hard constraint.

How it runs

Fixed scope, visible progress, clean handover.

Written up properly

How three of them were actually built.

The questions

Asked before every contract.

Starting from nothing? How to build an MVP that ships covers scoping a first version before you hire anyone.

Contract or full-time?

Contract and freelance work through this page — project-based, fixed scope, remote. If you're hiring for a permanent role instead, the relocation page covers that: I'm open to full-time positions in the Netherlands and Germany.

What do you charge?

Fixed price against a written scope, quoted after a free call, rather than an hourly rate with an open meter. Any number quoted before seeing the project would be a guess, and guesses are what turn into change requests later. Smaller, well-scoped projects are quoted as a single figure; longer engagements as monthly blocks.

Front-end only, or the whole thing?

Either. Plenty of the work is a React or Next.js front end against an API someone else owns. But the reason to hire one engineer for the whole stack is that most real bugs live at the seams — between the client and the API, or the API and the database — and those are cheapest to fix when one person owns both sides.

Do you work with existing codebases?

Yes, and it's most of the work. Inheriting a codebase, finding out why it's slow or fragile, and shipping without a rewrite is a specific skill. I'll tell you honestly if a rewrite is genuinely the cheaper path — it usually isn't.

React or Next.js — which should I pick?

Next.js by default: routing, server rendering, and image and font handling are solved for you, and SEO is real work you don't have to invent. Plain React with a separate API makes sense when the app sits behind a login and search visibility is irrelevant. It's a twenty-minute conversation, not a religious question.

Where are you, and how does the time zone work?

Agadir, Morocco. That's the same clock as London most of the year and one hour behind Berlin and Amsterdam in summer, so the European working day overlaps almost entirely and the American morning is covered. I work in English, French, Arabic, and Darija. Every project on this site was delivered remotely.

Can you do the AI parts too?

That's the other half of what I do — LLM agents, RAG over your own data, and the pipelines around them, running in production on FASL and RESO Khdma. If AI is the point of the project rather than a feature of it, the main hire page covers that work directly.

How fast can you start?

Usually within a week or two, depending on what's in flight. If a project needs to start sooner than that I'll say so on the call rather than take it and stretch it.

Free call · fixed quote · no retainer

Send me the spec
and I'll send you a number.

Or send me a half-formed idea — the first call is for working out what the project actually is. I answer every email myself, within 24 hours.

Email [email protected] →