How working together goes

What I can build for you, what happens week by week, and the answers to the questions people ask me most.

Tell me about your projectBook a free call

What I actually build

I do not choose projects by the tools involved. Tell me what you want to exist, and I will tell you the shortest honest way to get there. If your project needs a designer, a tester, or a server specialist, I bring in people I have worked with before — and you still deal with one person.

The first real version of your product

Also called: SaaS MVP, minimum viable product

From an idea you have already thought through, to something real customers can use — in about 6 to 8 weeks. Phone app, website, admin screen, and the server behind it.

Best for: You know what you want and you need it working, without hiring a whole team.

See the packages

A phone app

Also called: iOS and Android mobile app, Flutter development

One app that works on both iPhone and Android, built once instead of twice. Works without internet where it needs to, and feels as fast as any other app on the phone.

Best for: You need to be on people's phones without paying to build the same app twice.

Tell me about it

Making it handle more people

Also called: backend modernization, scaling, performance optimization

Taking something that works for a hundred users and making it work for a hundred thousand — faster, cheaper to run, and with alarms that tell you about problems before your customers do.

Best for: You already have customers, and growth is starting to break things.

Tell me about it

Adding AI to what you already have

Also called: GenAI features, LLM integration, RAG, chatbot

A real AI feature inside your product — answering questions from your own documents, summarising, sorting, or chatting with customers. Built with controls on what it costs, how fast it answers, and how often it is right.

Best for: You want AI that actually works in your product, not a demo that impresses once.

Tell me about it

A website that does real work

Also called: web platform, full-stack web application

Not a brochure — a website people log into and get things done in, with a proper database behind it. Built so it can be maintained for years, by me or by anyone after me.

Best for: Marketplaces, business tools, internal systems — anything past a marketing page.

Tell me about it

Rescuing a project that went wrong

Also called: project rescue, technical audit, legacy takeover

An honest look at what has been built so far, and a straight answer about where it stands. Then a plan to finish it. I can do the work, or hand the plan to your own team.

Best for: Your project is late, over budget, breaking in front of customers, or your developer left.

Tell me about it
How we work

What you can buy

Four ways to work together. Each one says what you receive and roughly how long it takes, so you know what you are buying before we talk.

Scoping Week

Start here · 1 week

Also called: discovery sprint, technical scoping

A small paid first step, so neither of us has to guess. You explain the idea. I come back with a written plan: what gets built, what it does, in what order, how long each part takes, and what each part costs.

  • A written plan you can hand to any developer — not only me
  • A list of every screen and feature, in order of importance
  • A timeline broken into stages, with a price for each stage
  • The main risks, and what I would do about them

If you decide to build with me afterwards, this fee comes off the first stage. If you walk away, the plan is still yours to keep.

Then, the build itself

Three sizes. Pick the one that matches where the product is.

First Working Version

6–8 weeks

Also called: MVP, minimum viable product, v1 launch

The first real version of your product — one that actual customers can use, not a demo. Phone app, website, and the server behind them.

  • A phone app on the App Store and Google Play, or a website — or both
  • The server and database that run it
  • An admin screen so you can manage things yourself
  • It running live, for real users, not on my computer

You know what you want to build and you need it working and in front of people.

Fix or Finish What You Have

2–4 weeks to assess, then agreed per stage

Also called: project rescue, technical audit, handover, legacy takeover

Someone already started your product and it is late, broken, or slow — or the developer left. I read the existing work, tell you honestly what state it is in, and give you a plan to finish it.

  • An honest written assessment of what exists and what it is worth keeping
  • A clear answer on repair versus rebuild, with the reasoning
  • A plan to finish it, priced by stage
  • I can do the work, or hand the plan to your own team

You have already paid for something that is not working, and you need to know where you stand.

Make It Handle More Users

Agreed per stage

Also called: scaling, performance optimization, backend modernization, cloud migration

Your product works, but it is getting slow, expensive, or falling over as more people use it. I find what is causing it and fix it.

  • A measured report of what is actually slow — not guesses
  • The fixes, applied and measured again afterwards
  • Lower running costs where the waste is in the setup
  • Monitoring, so you find out before your customers do

You already have customers and growth is starting to hurt.

How I price

I do not put one number on this page, because a fair price depends on what you actually need — and I would rather tell you the truth after looking than a number before. Here is exactly how it works.

  • We agree the work in stages. Each stage has its own fixed price, agreed before that stage starts.
  • You never get an open-ended bill. If a stage grows, we agree the change first.
  • You pay per stage, not everything upfront.
  • The code and the rights are yours from the first day, in your own account — not held by me.
  • The Scoping Week above is the cheapest way to find out what your project really costs.

What happens, step by step

1

You write to me

One or two lines about what you want. Use the form or email. I reply within 24 hours on working days.

2

We talk

30 minutes. You explain, I ask questions, and I tell you what I think the risks are. No sales pitch.

3

I send a plan

Within 2 to 3 days: what gets built, in what order, how long it takes, and the price of each stage in writing.

4

I build it

You see working progress every week. Short updates in between. The code sits in your own account from day one.

5

It goes live

Published and running for real users, with written instructions and a plan for what comes next.

When I am not the right choice

  • You change what you want every week. I price work in stages, and a stage has to be decided before it starts.
  • You want one final price for everything before anyone has looked at it properly. I price each stage, not the whole project unseen.
  • You are looking for the cheapest option. I am not the cheapest and I will not pretend to be.

Questions people ask me

Who owns the code when it is finished?

You do. The code, the designs, and the files are all yours once the final stage is paid. I keep no rights to any of it, and it lives in your own account from the first day — not mine.

Will you sign an agreement to keep my idea private?

Yes. I am happy to sign a confidentiality agreement (an NDA) before you tell me the details. Send me yours, or I can send you a standard one.

What do you build things with?

Phone apps: Flutter, so one app covers both iPhone and Android. Servers: Spring Boot or .NET. Database: PostgreSQL. Websites: Next.js and React. AI features: Spring AI and modern LLM patterns including RAG. I choose per project and I will not push technology you do not need.

Where are you, and do our working hours overlap?

I am in Egypt (GMT+2, GMT+3 in summer). That gives a full working-day overlap with Europe, the Middle East, and most of Asia, and mornings with the US East Coast. I am flexible for important calls.

How often will I hear from you?

A call every week where I show you what is working so far, plus short written updates in between on whichever app you already use — WhatsApp, Slack, Telegram, email. I answer messages within 24 hours on working days.

What happens after it launches?

You can keep me on a small monthly arrangement for fixing problems, small additions, and keeping the servers healthy. We discuss it near the end, and it is optional.

Are you available right now?

I take one or two projects at a time so that each one gets proper attention. Book a free call and I will tell you honestly when I could start.

What if I only need one part — just the app, or just the server?

That is completely fine. A lot of my work is a single piece: only the phone app, only the server, only the AI feature, or only a review of what you already have.

What if I want to stop in the middle?

You can. Work is agreed in stages. Once a stage is paid and delivered, you can walk away with everything built so far and the rights to it. There is no long contract locking you in.

I am not technical. Is that a problem?

No, and you should not have to become technical to buy software. I will explain everything in normal words, and if I ever use a term you do not know, ask me and I will rephrase it. You are not expected to know what any of it means.

Tell me what you want to build.

Send a few lines — what it is, roughly what you can spend, and when you need it. I will tell you honestly whether I can help and what I think the sensible next step is.

Tell me about your project

Or book a free 30-minute call directly.