Agree the scope.Then build.

You work with me from the first conversation through handover. I scope it, design it, build it, and hand it over.

Discover

Deliverable: A clear brief

I start from who it is for and what has to work on day one. That picture can change. I check in along the way so the work stays close to what you want.

Agree

Deliverable: Scope, price, and date

Before any code, you see the screens, what is included, what can wait, the price, and the date. That is so you can decide with the facts in front of you. If the scope changes later, the price and the date are updated with it.

Build

Deliverable: Something you can use each week

Design and code move together. Every week you open the product and say what to change. That feedback shows up in the product you open the next week.

Hand over

Deliverable: The code, the accounts, the keys

You get the code with its full history, every account in your name, and a recorded walkthrough of how it runs and how to change it. If you want me to stay on for maintenance, that is a separate fee.

Working together

Clear on the price and when I can start.

Web application, from: $2,000
Mobile app, from: $2,500
A first version can take anywhere between: 1 to 6 months
Projects at a time: Two

These are starting prices for a small first version on one platform. I agree the scope and the price before any code. A second platform, payments, several kinds of user, AI features, or store submission each move the price up, and a larger job costs more.

Build it yourself, or have it built

If a tool can build it, use the tool.

Tools like Rork (phone apps) and Lovable (web apps) are good, and for many people they are the right place to start. They turn a description into a working app. The real question is how much of the work you want to do yourself.

Using a tool yourself

Cost: A monthly plan, from about $20. Every request spends credits, fixes included, so the bill follows how much you change. Plan for more than one month.
Time: You write the requests, test every screen, fix what breaks, and set up the Apple and Google accounts and the store review. Rork's own guide says 30 to 60 days of evenings.
The code: What the tool writes runs. How well it holds up as the product grows is a separate question, and someone may need to read it later.
Suits you if: You have the time and the patience, the idea is simple, and you are happy to learn as you go.

Having me build it

Cost: From $2,000 for a web application, from $2,500 for a mobile app. About a month and up.
What you do: Tell me what it should do and look at the product each week. I do the scope, the design, the build, the accounts, and the store submission.
What you keep: The code with its history, every account in your name, and a walkthrough of how it runs.
Suits you if: You would rather spend your time on the business than on the app.

Most people could do it themselves with enough time. Most would rather not.

Fit

A few projects at a time, so each one ships.

Good fit

01People running a business who can make the decision.
02One product built properly, with room to grow it after the first version.
03People who want to own what they paid for, code included.

At handover

You leave witheverything.

01The code with its full history.
02Every account in your name: hosting, builds, stores, keys.
03The scope and task board that produced it.
04A recorded walkthrough of how it runs and how to change it.
05The option to stay on for maintenance, at a separate fee.

Work with me