Web app and admin
The product on the web, plus the admin you run it from: users, content, payments, whatever the operation needs to see.
02 · 4–8 weeks
Product Build
Everything the MVP Sprint leaves out, built by the same engineer: mobile apps from the same codebase, more than one flow, an admin, subscriptions in the stores, and whatever model work the product needs.
Price
$10K–$25K
Included
Web + iOS + Android, one codebase
Included
Several flows, admin, AI where useful
Included
Store submission included
Platforms3
Codebase1
Skeleton liveW1
Pay on deploy50/50
How it works
Where a project lands in the $10K–$25K band depends on three things: how many platforms, how many flows, how many integrations. The scoping call settles all three and the number is fixed in writing before work starts. It does not move unless the scope does.
Week one is a running skeleton on web. Mobile follows from the same codebase with Expo and React Native, built for the stores through EAS, with RevenueCat for in-app purchases where the product sells subscriptions on a phone. An admin for you, AI features where they earn their place: chat, search over your data, extraction, generation. A demo every three to four days throughout.
50% to start, 50% on deployment. If the date agreed at scoping is missed, the second half is waived. App Store and Google Play review time does not count against the date. The date moves only if the scope changes in writing.
What you get
Four things land on your side.
iOS and Android apps
Native apps from the same codebase with Expo. Push notifications, in-app purchases through RevenueCat, submitted to both stores.
AI features where they earn their place
Chat, retrieval over your documents, extraction, classification or generation, with the model chosen per problem and swappable later.
Stores, source, 30 days of support
Store listings submitted, source and infrastructure in your accounts, a runbook, and a month of fixes after launch.
How it runs
Product Build, week by week.
Scope
Day 0: platforms, flows and integrations agreed on a call, written into a scope with a fixed price and a date. 50% invoiced.
Skeleton
Week 1: web skeleton deployed, shared backend and data model in place, mobile shell building through EAS.
Build
Weeks 2–6: flows land one at a time across web and mobile, with a live demo every 3–4 days.
Launch
The agreed date: production deploy, store submissions, monitoring, handover. The second 50% on deployment, or waived.
Questions
What people ask before they book.
- How is the price set within the band?
- Platforms, flows and integrations. Web plus one mobile platform with three or four flows sits near $10K. Web plus iOS plus Android with an admin, subscriptions and model work sits near the top. You get the exact number in writing after the scoping call, and it does not change unless the scope does.
- Do you handle App Store and Google Play submission?
- Yes. Developer accounts are yours, listings and builds are prepared and submitted by Codeks, and review feedback is handled until the apps are live. Review time itself is outside anyone's control, which is why it does not count against the date.
- Can you add AI features to my product?
- Yes, when the feature needs one: chat over your data, search, extraction, classification, generation. The model is chosen per problem and kept behind an interface so it can be swapped. If the feature does not need a model, one is not added for the label.
- What if the project doesn't deliver the expected results?
- Success is defined in the scope in week one, and you see the build every three to four days, so there is no surprise at the end. Every milestone leaves you with software that runs, and you can stop at any of them.
Start here