Skip to content
Ayoub
Back to services
My deepest work

SaaS Platforms

A subscription product founders can sell, from first idea to paying users.

A web product people sign up for and pay for every month. I handle the idea, the market study, the build and the launch. You stay the founder, not the project manager.

What this actually is

A SaaS product is software your customers rent instead of buy. They sign up, they log in, they pay every month, and they expect it to work every day. That last part is where most of the work lives.

The hard parts are rarely the screens. They are accounts, roles and permissions. They are billing that matches what the customer actually used. They are the failed payment on a Tuesday night. They are background jobs that must finish even when the server restarts. And they are keeping one customer's data fully separate from the next.

I build this on Next.js and TypeScript. Prisma and PostgreSQL hold the data. Stripe or Lemon Squeezy handles payments. Inngest runs the background work. Resend sends the mail the product depends on.

I start with the market study. The first version ships with the smallest set of features that can earn money.

What you get

  • A written market and competitor study, with the gaps I plan to use
  • A feature list split into phases, with the first phase marked
  • The working product, built on Next.js, TypeScript and PostgreSQL
  • Sign-up, accounts, roles and subscription billing through Stripe or Lemon Squeezy
  • An admin area where you see users, subscriptions and activity
  • The source code in your own repository, plus a deployed live version

Things in this category

  • A booking and scheduling platform for a service business
  • A dashboard where a team tracks work and reads reports
  • A membership site with paid tiers and gated content
  • An invoicing tool small businesses pay for monthly
  • A marketplace joining two sides, with payment in the middle
How this one gets built

The same six stages, said in the language of this kind of product.

You tell me the idea

A single conversation, usually about thirty minutes.

We talk until I can describe your idea back to you correctly.

We start with a conversation, in English, French or Arabic. You describe the idea in your own words. I ask questions about who it is for, what they do today, and what you want to happen. I write down what I heard and send it back for you to correct.

What you have at the endA written idea brief: the goal, the user, the assumptions, and what success means.

You see the market gaps

Usually a few days to a week.

I find out what already exists and where it leaves people stuck.

I go through the products your users already use, free and paid. I read what people complain about in reviews, forums and support threads. I look at how competitors charge. Then I write down the gaps that are real, and the ones that are not worth chasing.

What you have at the endA market and competitor report, with the gaps ranked and the evidence linked.

You see the real screens

Usually a week or two.

We decide what the product is, and you see it before it is built.

I turn the gaps into a product you can actually see. First the shape: what it does, who logs in, what each screen is for. Then clickable screens you can open on your phone. You use them, tell me what feels wrong, and I change it before any code exists.

What you have at the endA clickable prototype of the main screens, plus the agreed feature list.

You approve the plan

Usually a few days.

The build gets broken into phases, each with its own scope and price.

A big build in one piece is where projects go wrong. So I split it into phases. Each phase has its own scope, its own price and its own working result. You approve one phase before it starts. You are never asked to commit to the whole thing at once.

What you have at the endA phase plan: scope, price and result for each phase, in writing.

You watch it being built

The longest stage. Weeks to months, depending on scope.

The product gets built in order, and you see it working every week.

I build phase by phase, starting with the part that carries the most risk. Every week there is a real link you can open and use. Nothing is hidden until the end. When something takes longer than I said, you hear it from me first.

What you have at the endA working product on a live link, updated every week, with the code in a repository you own.

You launch, and I stay

Launch takes days. Staying afterwards is ongoing.

The product goes live, and I stay until it is genuinely right.

Going live is a stage, not a finish line. I move it to your domain and accounts, watch the first real users, and fix what they hit. Then I hand over what you need to run it. If you want me to keep going, I stay.

What you have at the endThe live product on your domain, with accounts, code and a short handover guide.

See all six stages in full
Built like this

Work of this kind, written as stories.

Live2025

Assessment platform

An exam platform the institute runs itself, from question bank to results.

Next.js · React · TypeScript · PostgreSQL · Prisma · Auth.js

Read the full story
LiveMy own project2025

Hiring platform

A marketplace where hiring and freelance work run on the same four steps.

Next.js · React · TypeScript · PostgreSQL · Prisma · Neon

Read the full story
LiveMy own project

Smart booking platform

Booking for beauty centres: WhatsApp at the front, a full system behind it.

Next.js · TypeScript · Prisma · Neon · Better Auth · WhatsApp Business API

Read the full story
See all work
What I build

Is this what you need?

If you are not sure which of these your idea is, that is a normal question and a good reason to talk.

Tell me about your ideaOr send a full brief instead
The rest of what I build