Skip to Content

Services

I build the first version of your product, start to launch.

One developer from first commit to launch. A small, working first version of your product that real people can sign up for and use.

Get in touch
Illustration of a small product taking shape from a sketch to a live app on a laptop

Is this for you?

  • You have an idea and no technical co-founder, and want one person you can talk to directly.

  • You have a budget and a date, and you want a clear list of what is and isn't in version one.

  • You'd like the code to stay useful when you hire your first engineer.

  • You want to find out whether the idea works before paying for polish.

Not the right fit for a large existing product that needs a team. Taking over an existing app is closer.

What you get

  • A smaller scope than you expect

    The first call is mostly about cutting. We list what the product must prove, and anything else moves to a later list.

  • One developer, start to launch

    Design translation, front end, back end, database, sign-in and deployment. The same person makes the decisions and knows the code.

  • Plain, common tools

    TypeScript, React, Next.js, Node.js and PostgreSQL. Boring on purpose: they are easy to hire for and easy to hand on.

  • A live link early

    I deploy from the first week so you see the product grow and can react while changes are cheap.

  • AI features when they earn their place

    Chat, agents and background tasks that call a model, built into the product. See AI features and agents.

  • Handover notes

    How to run it, how to deploy it, where the secrets live and what I'd do next.

What the first two weeks look like

  1. Week 1

    Scope, outline and set-up

    Scope, a clickable outline of the main flow, the repository and hosting set up in your accounts, and the data model agreed.

  2. Week 2

    Sign-in and the first real feature

    Sign-in and the first real feature, deployed, so you can click through it on a live address. From there we ship in small steps, each one a version you can show to someone.

Relevant experience

At caisy I built features for billing and subscriptions (schema, migrations and Stripe-related work) inside a Next.js codebase. On ScriptBee I built a chat interface, a task widget and background tasks that run through Trigger.dev.

Those are the pieces most MVPs need: accounts, payments, something running in the background and a clean interface. The case study has the details.

How we work and what it costs

Small MVPs are usually best as a fixed price for a fixed scope, split into milestones you approve one by one. If the scope is still moving, a monthly arrangement is safer for both of us. I quote after one call, and the quote lists what is included and what isn't.

Describe your idea in the form below. Tell me who it is for and what version one has to prove.

Questions people ask

How long does an MVP take?

It depends on what the MVP has to prove. After one call I can usually tell you whether it is a matter of weeks or months, and which features to drop to bring it down. What an MVP costs explains what drives the size.

Do I need a designer first?

Not always. If you have designs, I build from them. If you don't, I use a clean, plain interface and keep the first version simple, so you can test the idea before paying for polish.

Who owns the code?

You do, from day one. I work in a repository and hosting accounts that you own.

What happens after launch?

Real users always find things the plan missed. You can keep me on for a set number of days a month to fix and improve it, or take the code and the notes to another developer. The code stays readable either way.

Can you build something with AI features?

Yes, in the sense of adding LLM-powered features to a product, such as a chat interface or background tasks that call a model. I have built chat and task interfaces on ScriptBee's Next.js app. I don't train models.

  • MVP cost: what changes the price

    Why MVP quotes differ so much, the eight things that change the price, and how to get a number you can trust before you start.

Other services

Let’s work together.

Tell me what you are building or what needs fixing. You can also email info@ahmed-ghazy.com or find me on LinkedIn (opens in a new tab).

I use your details to respond to your enquiry. See the Privacy Notice.