How I work

The whole method, with nothing left vague.

This is the same sequence on every project, whether it is a SaaS platform or a one-page site. Bigger products spend longer in each stage. None of them skip one.

Stage 1How longA single conversation, usually about thirty minutes.

You tell me the idea

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.

You bring

The idea in your own words, who you think it is for, and roughly what you can spend. Nothing written, nothing prepared.

I handle

I run the conversation and ask the questions you would not know to ask. I separate the goal from the feature list, name the assumptions we are betting on, and flag anything that already looks expensive or risky.

What you have at the end

A written idea brief: the goal, the user, the assumptions, and what success means.

Stage 2How longUsually a few days to a week.

You see the market gaps

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.

You bring

Any competitor names you already know, and anything you have heard from people who would use this. A few links is enough.

I handle

I map the competitors feature by feature and price by price. I collect real user complaints as evidence, not opinion. I separate a gap you can win from a gap that exists for a good reason.

What you have at the end

A market and competitor report, with the gaps ranked and the evidence linked.

Stage 3How longUsually a week or two.

You see the real screens

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.

You bring

An hour to click through the screens, and honest reactions. Say what feels wrong even if you cannot say why.

I handle

I cut the idea down to the smallest version that still works. I design the screens, the flows and the data behind them. Every feature that survives has to earn its cost.

What you have at the end

A clickable prototype of the main screens, plus the agreed feature list.

Stage 4How longUsually a few days.

You approve the plan

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.

You bring

A decision on what matters most to launch with, and approval of the first phase before it starts.

I handle

I choose the stack, the data model and the hosting, and write down why. Each phase is planned against the same four things in order: speed, efficiency, security, cost. Then I scope and price each one.

What you have at the end

A phase plan: scope, price and result for each phase, in writing.

Stage 5How longThe longest stage. Weeks to months, depending on scope.

You watch it being built

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.

You bring

About an hour a week to look at the latest version, and answers when I ask about your business.

I handle

I write the code, the database and the tests. Access control is checked on the server, not just hidden in the interface. Payments, email and background jobs are wired to real accounts you own.

What you have at the end

A working product on a live link, updated every week, with the code in a repository you own.

Stage 6How longLaunch takes days. Staying afterwards is ongoing.

You launch, and I stay

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.

You bring

The domain and the business details for payments, and whatever you hear from your first users.

I handle

I handle deployment, domain, email delivery, backups and error monitoring. I watch the first days closely and fix what breaks. Accounts and code are transferred to your name, not held in mine.

What you have at the end

The live product on your domain, with accounts, code and a short handover guide.

How I work

The unglamorous parts

How does the first conversation actually go?

About thirty minutes, in English, French or Arabic, on WhatsApp or a call, whichever you prefer. You describe the idea. I ask questions until I can describe it back to you correctly. There is nothing to prepare.

What do you decide, and what do I decide?

You decide what the product should do and who it is for. I decide how it is built. When a technical choice changes what you can offer or what it costs, it stops being my decision alone and I bring it to you with the trade-off written out.

What happens when the scope changes?

It usually does, and that is fine. A change gets scoped and priced like anything else before it starts. Nothing gets quietly absorbed and nothing gets quietly dropped.

What if we disagree?

I will tell you when I think you are wrong, and why, once. Then it is your product and your call. I have talked founders out of features and out of launch dates; that is part of what you are paying for.

What if the project stops?

You keep everything that exists at that point. The work is deployed and handed over as it stands, not held back.

Next step

This is how it would go for you, too.

Every project runs through these six stages. The first one is a conversation, and it costs you nothing but half an hour.

Start at stage one