Ship your MVP
in a week

They are honest estimates, not a legal commitment. Most projects finish on time or earlier. Sometimes something unexpected happens, such as an unusually busy week or a problem specific to your project that nobody could have known about. Even then the delay is usually a day or two.

If I see a delay coming, I tell you right away, not on the last day, so you have time to adjust your plans. If you have a hard deadline, tell me before we start.

Waiting on third parties is not counted in those days. App store reviews, payment provider approvals and similar checks by services your project depends on are outside my control. The days next to a package cover my own work. If an Apple app review drags on, I keep handling it, but that time isn't part of the estimate.

A screen is a page a user sees, such as a sign-up page, a dashboard or a settings page. A feature is something the app does, such as sending an email, taking a payment or uploading a file. Login, sign-up and password reset are included and don't count. Before I start I list everything else, so we both know what the package covers.

Usually Next.js and React on the web, Flutter or React Native for iPhone and Android, and Node.js or Django with PostgreSQL on the back end. I pick what fits your MVP and explain the choice in the offer. If you or your team already have a preferred stack, tell me before we start.

Yes. I build with Claude Code, which is why one week and these prices are possible. I design the architecture, steer the build and test the app myself.

I only build with technologies I know well. AI is only worth using on work you understand yourself. I've worked with many of them across the whole stack, so I know what I'm doing. Claude Code handles the small details I don't need to memorize, so I can focus on what matters for your product. That is what makes these prices and timelines possible.

Yes. It's standard, readable code in your own repository, not a no-code export. The architecture is kept simple so it can grow, and you get handover notes, so a future hire or agency can pick it up without starting over.

An MVP is scoped to validate, not to handle massive scale on day one. Some parts will need more work as usage grows, and I tell you which ones.

Yes, once the order is paid in full.

Control and ownership are two different things. Control means the code, the accounts and the data are in your hands. You can give me access to your own repository and other accounts from the start, or I set everything up and hand it over when you're ready. If you don't have the accounts yet, I help you create them. I keep access only for as long as you want me to.

Ownership means the intellectual property in the code I write passes to you when the order is paid in full. For reviews, Finish my app and take-over milestones, that is before I start. For a Quick fix, it is when your card is charged. For a new app, it is when you make the final 70% payment.

Yes. We agree on the stack and conventions up front, and I can work in your repository from day one, so your co-founder sees every commit. If you already have code that needs finishing, Fix my app or a take-over is usually the better fit.

You do, directly to the provider with your own card. That can be hosting you already have, or one I help you choose and sign up for. Most new apps start on free or low-cost plans, and I tell you what each service costs.

Yes, for an iPhone or Android app. Apple charges $99 a year and Google charges $25 once. The accounts are in your name, so the app is yours, and I help you set them up.

I do, using Claude Design. That is enough for nearly every first version, so you usually don't need a professional designer at this stage. If you have wishes about the look, such as colors or a style you like, tell me at the start and I'll take them into account. If you have a Figma design from a designer, I can build from it, though for a first version that is usually more than you need.

You can, and for a demo it often works. The trouble usually shows up later, in auth, payments, data access rules and deploys. AI writes code fast, but it needs an engineer who knows what good looks like to steer it and check the result. That's the part I bring.

If you've already vibe-coded something, I can review it or fix it.

You put it in front of users and see what they do. For 7 days after delivery I fix anything that doesn't work as we agreed, free. When you know what to build next, I send you an offer for the next milestone, priced the same fixed way. There is no retainer and no lock-in.

Tell me about your idea and we'll decide together. Either we split it into a few packages done one after another, or we agree on a custom project.