Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · iOS sprint
Your iOS app, designed, built and on the App Store in 30 days.
Not a prototype and not a Figma file — a real app on a real device, in TestFlight by week three and submitted to Apple by day 30. One fixed price, agreed before anything starts.
Quick answer
An iOS app can be designed, built and submitted to the App Store in 30 days for a fixed $2,500, as long as the scope is one job the app does well. That month covers design, build, TestFlight testing and submission. Apple's review adds one to three days on top.
The plan
Day one to day 30, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–3
Scope lock
We agree exactly what the app does and, more importantly, what it does not do in v1. This is the meeting that decides whether 30 days is realistic.
- 2
Days 4–12
Design
Every screen designed and reviewed — flows, empty states, errors. You see real screens in the first week, not a moodboard.
- 3
Days 13–24
Build
The app gets built and wired to real data. A TestFlight build lands with you around day 21 so you are testing while I am still building.
- 4
Days 25–28
Polish and test
Device testing, performance, the fifty small things that separate a real app from a demo. Your feedback from TestFlight gets folded in.
- 5
Days 29–30
Submit
App Store listing finished and the build submitted to Apple. I handle review questions if they come back with any.
What $2,500 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Founders validating an idea with real users, not a waitlist
Businesses whose customers keep asking if there is an app
Teams who need something in front of investors this quarter
The honest part
When 30 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Apps that need a large backend built from scratch — that is its own project, and I will scope it separately rather than pretend it fits.
Anything depending on heavy 3D, real-time video processing or games. Thirty days is not enough and I would be setting us both up to fail.
Products where you do not yet know what the app is for. We scope that first, as a small paid piece of work, then start the clock.
Questions
Before you book
Yes, when the scope is one clear job the app does well. The 30 days covers design, build, TestFlight and submission. What makes it possible is deciding in the first three days what v1 does not include — apps overrun because scope grows, not because building is slow.
Other sprints
30 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.