Done-for-you iOS builds

Distribution is now the moat.So why are you spending a single second on the product?

Your app idea, built and submitted to the App Store in two weeks. I build the product and wire up your tracking — you spend those two weeks getting users.

Built by someone who runs a live AI subscription app — 180 active subscriptions and $4,149 collected in the last 28 days.

Price

$6,500

To start today

$3,250 deposit

50% now, 50% on delivery. Android adds $1,000. Full tier pricing below — nothing hidden at checkout.

DM me on X

@SeoulJosephK — tell me the app idea in one line.

RevenueCat dashboard showing 180 active subscriptions, $1,964 monthly recurring revenue, and $4,149 revenue over the last 28 days

180

Active subs

$4,149

Rev, 28 days

$1,964

MRR

Live RevenueCat data from my own app.

01What you get

Your funnel, end to end.

From the screenshot they tap to the feature that keeps them. Every stage below is a place users leak — and every one of them is something I build.

00 You run ads

Growth Build

The tracking that makes your ad spend measurable

You run the campaigns. I wire up the part that tells you whether they worked: Meta pixel, AppsFlyer attribution, and install and subscribe events verified firing before launch. Spend on day one and know what it bought you, instead of guessing for a month.

01 They tap

App Store screenshots + description

Your listing is the ad. Screenshots designed and the description written to convert the people who tap through. This is the first place people leave, and it happens before your app ever opens.

02 They open it

Complete onboarding flow

Every screen from first launch to activated user. Not a login box — the actual sequence that gets someone to the moment your app is useful.

03 You see where they quit

Onboarding analytics

Events on every onboarding step, so you can see the exact screen people quit on. Without it you learn that conversion is bad, but never which screen is doing the damage.

04 They pay

RevenueCat paywall

Subscriptions live and charging, with real-time price testing built in. Change $9.99 to $14.99 from a dashboard without shipping an update or waiting on review.

05 They stay

Your AI feature, plus profile + settings

The thing your app is actually for, wired to a real model provider and working on real input. Plus account, subscription management, restore purchases, and delete account — the screens Apple looks for.

All of it built, submitted, and deployed for you

Build upload, privacy declarations, App Store submission, and any review responses handled end to end. You do not touch App Store Connect unless you want to.

Ask and I will wire up RevenueCat + Meta Ads MCP

Connect both accounts to your AI assistant so you can ask "what did I spend per subscriber last week?" and get the real answer, pulled live from RevenueCat and Meta Ads. No dashboards, no CSV exports. Tell me at kickoff and it gets set up with the rest of the build.

One core feature, fully built. Additional features scoped as V2.

This is the boundary that makes two weeks possible. We pick the one thing at kickoff and it gets built properly instead of three things getting built halfway.

02Pricing

Two options. One add-on.

Pick one — it carries down to checkout.

All tiers: 50% deposit now, 50% on delivery.

DM me on X

Selected: The Build — $3,250 deposit

03The two weeks

What happens, day by day.

Fourteen days, accounted for. If you ever wonder what is happening with your build, this page is the answer.

  1. 1
    Day 160 minutes

    Kickoff call

    We lock the scope in writing: every screen, the one core feature, your subscription prices. You leave with a written spec. The two-week clock starts when this call ends.

  2. 2
    Days 2–4Build

    Onboarding flow + app skeleton

    Navigation, design system, and the full onboarding sequence. First TestFlight build in your hands by day 4 — you watch this get built, you do not wait in the dark.

  3. 3
    Days 5–9Build

    Your core feature

    The longest stretch, spent on the one thing your app exists to do. Written progress update every second day. No status meetings.

  4. 4
    Days 10–11Build

    Paywall, profile, settings

    RevenueCat wired to live products, prices testable from the dashboard, purchase and restore flows tested on a real device. Growth Build: Meta Ads and AppsFlyer get wired up here — final verification and handover follow submission, on the add-on timeline in section 05.

  5. 5
    Day 12Your turn

    Revision round

    You go through the build and send everything you want changed, in one batch. Fixes land inside the two weeks. This is the round included in the price.

  6. 6
    Days 13–14Ship

    App Store submission

    Screenshots, listing, privacy answers, final build uploaded and submitted to Apple. This is the deadline the guarantee is measured against.

One thing I cannot control: Apple's review queue. Review and release time sit outside the two-week build clock — the clock stops at submitted. Review is typically 24–48 hours, but Apple sets that pace, not me, so I will not promise it.

Add-ons run on their own clock. These 14 days are the iOS build. Meta Ads + AppsFlyer handover and Android submission each carry their own guaranteed date — both are in section 05.

DM me on X

$3,250 deposit · nothing due to message

04Why this is not an agency

You already know how the other version goes.

Six weeks of discovery, a Slack channel with nine people in it, and an invoice that grows. Here is what replaces each part of that.

No endless meetings.

One 60-minute kickoff call. After that, written updates every second day and a TestFlight build you can open yourself. If you want to watch progress, you tap an icon — you do not schedule a call.

No scope creep.

Scope is frozen at the kickoff call and written down. New ideas on day 6 do not get built — they get logged for V2. That refusal is the only reason a two-week deadline can be real.

No $20K retainers.

One fixed price, half now, half on delivery. No monthly minimum, no hourly billing, no discovery phase you pay for. When the app is submitted, the engagement is finished and you owe nothing further.

No account managers.

The person who writes your code is the person you message. There is no layer between you and the build, which is why there is nothing to schedule.

05The guarantee

Submitted to the App Store in two weeks, or your deposit back.

Fourteen days from the end of your kickoff call, your iOS app is submitted to Apple. If it is not, your deposit is refunded in full and you owe nothing. You keep every build produced up to that point.

What is guaranteed

  • iOS submission to the App Store within 14 days of kickoff.
  • One round of revisions, inside the two weeks.
  • Every deliverable listed in section 01.
  • A written scope, agreed at kickoff, unchanged after.
  • Full deposit refunded, same day, if I miss the date.

What is not guaranteed

  • Results. No revenue, downloads, ranking, or retention promise — anyone promising those is guessing.
  • Apple's approval or review speed. I guarantee submission, not their verdict.
  • The clock if you go quiet. It pauses while I am waiting on you for assets, accounts, or day-12 revisions.
  • Scope added after kickoff. New ideas become V2, not a missed deadline.

Add-on timelines

The 14-day clock covers your iOS build. Add-ons run on their own stated timeline, locked in writing at kickoff:

  • Growth Build (Meta Ads + AppsFlyer)

    iOS still submits within 14 days. Attribution and pixel setup are verified and handed over within 2 business days of submission.

  • Android

    Submitted to Google Play within 4 days of your iOS submission. Same app, same scope, second store.

Every add-on date is written into your scope on day one. If I miss a date I put in writing, the same deposit-back guarantee applies to it.

And if it turns out I cannot build your idea in two weeks: I tell you on the kickoff call and refund your deposit in full, same day. You are never stuck holding a scope that does not fit the deadline you paid for.

DM me on X

Nothing charged to message. Scope decided on the call.

06Every other question

The things you would ask before hiring anyone.

Answered here, in writing, so the call can be about your app instead of my process.

What if my idea is too big to build in two weeks?

Then I tell you on the kickoff call and refund your deposit in full, same day. That is the whole answer. You are not buying a negotiation — if what you want cannot be built properly in the time, I would rather return the money than ship you something broken on day 14. Most ideas fit once we cut to one core feature. Some do not.

What am I actually agreeing to?

The deliverables on this page, at the price on this page, submitted to the App Store within two weeks of the kickoff call. Your deposit is your agreement to a frozen scope — that gets written down on the kickoff call and neither of us moves it after. Booking the call costs nothing, but be clear on the order: the deposit is taken at the start of that call, and we scope your build after. If what we then write down cannot be built in two weeks, I say so on the same call and refund you in full that day.

Who owns the app? Do I get the source code?

You own the app and everything your business runs on: the App Store listing, the Apple Developer account, the RevenueCat account, your API keys, your users, and the product itself. All of it is in your name from day one — nothing about your business depends on my goodwill. What is not included by default is the source repository. I maintain the codebase, which is what lets me fix and extend it fast. Full source transfer is available as a paid add-on — ask at kickoff and I will quote it. If you want the repo in your hands from the start, tell me before you pay, because it changes the price.

Do I need an Apple Developer account?

Yes, and it needs to be yours, not mine — $99/year, paid directly to Apple. Your app should live under your company name. If you do not have one, we set it up together on the kickoff call. Note that Apple can take a few days to verify a new organization account, so start it early if you can.

What if Apple rejects the app?

I handle the rejection and resubmit, included, no extra charge. Be clear on what the guarantee covers though: it covers submission within two weeks, not Apple's approval. Apple's review queue and their decisions are not something I or anyone else can promise on a timeline.

I am not technical. What do you actually need from me?

Show up to the kickoff call knowing what your app does in one sentence and what the one core feature is. Then: your Apple Developer account, your logo if you have one, and a batch of revision notes on day 12. That is it. You do not need to write a spec, understand the stack, or make technical decisions.

What counts as one core feature?

One user-facing job the app does end to end. An AI chat that answers questions in your niche. A workout logger with progress history. A habit tracker with streaks and reminders. What it is not: a chat feature AND a social feed AND a marketplace. If you are describing three things, we pick one at kickoff and the other two become V2.

What about backend, API, and AI costs — who pays those after launch?

You do, from day one and every month after. The accounts are opened in your name, the keys are yours, and the bills go to your card — I never resell you infrastructure or mark it up. For a typical AI app that means an OpenAI or Anthropic key, a Supabase project, and RevenueCat (free until you pass $2,500/mo in tracked revenue). At launch volume, expect roughly $20 to $100/month total. Now the part that actually bites founders: AI inference cost scales with usage, so every active user costs you money whether or not they ever subscribe. A free user who hammers your feature is a bill. That is exactly why the paywall ships before launch instead of after, and why price testing is wired in — you need margin per user, not just downloads. On the kickoff call I will show you the per-user cost math for your specific feature before you spend a dollar, so you can price above it.

Can I change the design if I hate it?

Design direction is locked at kickoff — you bring reference apps you like, we agree on the look before a line of code is written. Day 12 is your revision round for everything you want changed. What day 12 is not is a redesign: if you decide in week two that you want a completely different visual direction, that is V2 work.

When is the second half due?

On delivery — when the app is submitted to the App Store. Not before. If I miss the two-week deadline, you do not owe the balance and your deposit comes back.

What happens after launch?

You own a live app with a working subscription behind it, and this engagement is finished. Anything further — a second feature, changes once you see real user data — gets scoped and quoted separately at that point. There is no ongoing commitment attached to this purchase and nothing auto-renews.

Why should I believe the two-week number?

Because the scope is small enough to be honest about, and because I run this exact setup myself — a live AI subscription app with 180 active subscriptions that collected $4,149 in the last 28 days. The onboarding, the RevenueCat paywall, the analytics, the App Store submission: those are not research projects for me, they are the parts I have already built and debugged. The two weeks go into your feature, not into me learning subscriptions.

07Checkout

Start the build.

The Build
$6,500
Total project
$6,500
Balance on delivery
$3,250
Deposit
$3,250

Paid at the start of the kickoff call, once we have talked. Nothing is charged to message.

DM me on X

@SeoulJosephK · no card, no calendar, just a message

$3,250 deposit, $3,250 on delivery. Messaging costs nothing. If it looks like a fit we set up the kickoff call, and the deposit is taken at the start of that call, before we scope your build.

The deposit is your agreement to a frozen scope. We write that scope down together on the kickoff call — every screen and the one core feature — and it does not change for the two weeks. Anything new becomes V2. Your two weeks start when that call ends.

The clock pauses whenever I am waiting on you. Assets, account access, and your day-12 revision notes are your side of this. Two weeks assumes you reply within one business day — go quiet for three days and the deadline moves by three days.

The 14-day guarantee covers iOS submission. Growth Build and Android add-ons carry their own written dates, listed in the guarantee above.

If the scope cannot be built in two weeks, I say so on the kickoff call and refund your deposit in full. If I miss the two-week submission date, your deposit comes back and you owe nothing.

Paying the deposit means you agree to the Terms of Service and Refund Policy. Payments are processed by Paddle, the merchant of record.

What happens after you message

  1. 1

    You DM me on X at @SeoulJosephK.

    One line on what the app does is enough to start. Costs nothing, commits you to nothing, and I will tell you straight if it is not a fit for a two-week build.

  2. 2

    We do the kickoff call.

    60 minutes. The deposit is taken at the start, then we lock the scope in writing and your two weeks begin the moment the call ends. If your idea cannot be built in two weeks, I say so on that same call and refund you in full that day.

  3. 3

    Fourteen days later, you are submitted.

    With a TestFlight build in your hands long before that.

The Build

$3,250 deposit

DM me