Skip to content
Yassir Halaoui
FR
Lire en français

Services

From zero to a shipped product, in days

An MVP isn't a clickable mock-up. It's the smallest thing a stranger can find, understand, pay for and use. I build that, end to end, and I build it fast.

In short

Yassir Halaoui builds MVPs from idea to paying customers, covering product decisions, code, payments, transactional email, SEO and launch. His fastest so far is Kempt, a native macOS app with on-device AI: first commit on 13 October 2026, and a signed, notarized 1.0 with Stripe licensing and automatic updates live on 17 October 2026.

Kempt, from idea to launch
4 days
See the project
Families on RevealTogether, 40+ countries
1,000+
See the project
Products built and run alone
3

How I work

What you get

A product that works for a stranger on day one. It can be found, it explains itself, it takes payment, it sends the emails people expect, and it doesn't lose their data. Then it's handed over with the code, the accounts and the documentation in your name.

Why it's fast

Three reasons. I've shipped the same foundations several times (authentication, Stripe, email, i18n, SEO, deployment), so they're decisions now, not research. I work with AI coding agents all day, which takes out most of the typing. And I cut scope hard and early, which takes out most of the waiting.

What I won't cut

Speed never comes out of payments, data safety or the basics of being found. Kempt's first public build already had signed updates, licence keys, an undo for every file move and a privacy model with no network calls beyond an update check. Those are the parts a rewrite can't fix later.

The stack I reach for

For the web, usually Next.js, TypeScript, PostgreSQL, Stripe, Resend or Brevo, and Vercel, because that combination gets a product live fastest and holds up when it grows. Spring Boot when the domain needs strong transactions or a team will inherit the code. Swift when the product belongs on the Mac.

How we start

  1. 01

    A scope call, then a one-page brief naming the one thing the MVP has to prove.

  2. 02

    A working build on a real URL within days.

  3. 03

    Payments, email, analytics, SEO basics, then launch.

  4. 04

    Handover: code, accounts and documentation in your name.

Write to me · consultingyassir@gmail.com

Stack

Web
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
Backend
  • Spring Boot
  • FastAPI
  • Node.js
  • PostgreSQL
  • Redis
Commerce
  • Stripe
  • PayPal
  • Resend
  • Brevo
Ship
  • Vercel
  • Railway
  • GitHub Actions
  • Docker
Native
  • Swift
  • SwiftUI
  • Sparkle

Questions

How fast can you build an MVP?

It depends on the scope. Kempt, a full macOS product with payments and automatic updates, took four days from idea to launch. A web MVP with accounts, payments and email is a matter of weeks, not months, and I'll give you a date after the scope call.

How much does an MVP cost?

I quote after the scope call, either for a fixed scope or by the day. The brief written in the first days is what keeps the price honest, because it says what's in and what isn't.

Which tech stack do you use for an MVP?

Next.js, TypeScript, PostgreSQL and Stripe on Vercel for most web products. Spring Boot when the domain is transactional or a Java team will take it over. Swift for a native Mac app.

Do you design the product as well?

Yes, the interface and the copy. I designed, built and still run RevealTogether, TheQuizMaster and Kempt.

Can you build a native Mac app?

Yes. Kempt is a native macOS app in Swift and SwiftUI that uses Apple's on-device model, ships notarized with Sparkle updates, and sells through Stripe.

Who owns the code?

You do, along with the domain, the Stripe account and every other account the product runs on. I set them up in your name from the start, so there's nothing to transfer at the end.

Shipped work

Competences behind it

Field notes

Also on offer

Every competence