The Founder's Checklist Before Hiring an App Studio

Before you wire a deposit or sign a contract, stop. The average custom iOS app costs between $15,000 and $120,000 depending on complexity — and that budget disappears fast with the wrong partner. This hiring app development studio checklist gives you ten concrete questions to work through before committing a dollar, covering the things most founders only think to ask after they have been burned: shipped portfolio, App Store track record, and what actually happens after launch day.

The typical founder spends a discovery call talking about their idea while the studio nods and prepares a polished proposal. What rarely gets examined: whether the studio has shipped anything at this complexity level, what their maintenance track record looks like, and who owns the code when the project ends. The questions below surface all of it.

---

The 10-question checklist

1. Can you send me direct App Store links — not screenshots?

This is the first filter. A studio that has genuinely shipped products can send you links to live, downloadable apps with real user ratings and version histories. Download two or three. Use them for five minutes. Check the last update date and read the reviews — a version history with recent updates tells you the studio maintains relationships beyond launch day.

At Fera Tech we have 12+ apps live on the App Store — including our own: Launchcast, a premium space launch tracker, and Clove AI, an AI-powered kitchen assistant. We build our own products because we believe in shipping, not just pitching. Browse our work to see what shipped software looks like.

What a weak answer looks like: “Most of our work is under NDA.” Some confidentiality is legitimate. But if every project is unavailable with no public evidence, that is a signal — not a policy.

---

2. What is your App Store track record on submissions and ratings?

Any studio can ship an app once. Maintaining clean first-round approvals, strong ratings, and no policy removals across multiple products requires a consistent internal process. Ask for the average star rating across their portfolio, whether any apps have been removed from the store, and how they typically perform on first-round review. A studio that deflects on these questions probably does not have numbers it is proud of.

---

3. Have you shipped an app at my complexity level?

Experience in an adjacent category is not the same as direct domain experience. Ask for examples at your complexity tier:

Complexity tier	Timeline	Budget range
Simple MVP (auth, basic features)	2–4 months	$5,000–$15,000
Standard app (payments, backend)	4–7 months	$15,000–$45,000
Complex app (AI, real-time data)	7–12+ months	$45,000–$120,000+

If your project is in the complex tier, you want a studio that has already navigated that territory — not one learning on your budget.

---

4. What does post-launch support include — and is it in writing?

The App Store is not static. Apple ships a new iOS version every September, device dimensions change, and third-party services deprecate endpoints. An app that works today can have broken behavior within 12 months without maintenance.

Ask for the exact scope in writing:

Support item	What to clarify
Bug fixes after go-live	How long covered? Bug vs. new work?
iOS compatibility updates	Included or billed separately?
App Store rejection handling	Who responds, in what timeframe?
Ongoing feature development	Retainer option, and at what rate?

“We will take care of you” is not a support term. If it is not in the contract, it does not exist.

---

5. Who will actually build my app — and will they stay on the project?

Some studios win work with senior partners in the room, then hand off to junior developers or overseas subcontractors the client never meets. Ask directly: are the developers in-house or contracted, can you meet the lead developer before signing, and will those specific people remain on the project from kickoff to launch?

This is not about geography — distributed talent can be excellent. It is about transparency and continuity. A team that fragments mid-project costs weeks in handoff time and context loss.

---

6. How do you handle scope changes mid-project?

Requirements change in every app project. A studio without a formal change-control process will either absorb additions silently (and cut corners), or surprise you with unplanned charges mid-sprint. Ask what happens when a new feature request arrives after development starts, how additions are priced, and whether they can walk you through a real example. “We handle it case by case” means they figure it out under pressure — and you pay for the friction.

---

7. Who owns the code when the project ends?

In most jurisdictions, a contractor retains copyright over code unless the contract explicitly transfers ownership. You need “full IP transfer” or “work made for hire” — not “license to use.” This covers iOS source code, backend services, design files, and third-party configurations. If a studio uses “license” where you expected “ownership,” ask why. See our services page for how we handle IP transfer.

---

8. Can you provide references from recent clients?

References are the most underused tool in vendor evaluation. Ask for two or three contacts from comparable projects in the past 18 months — not a flagship case study from three years ago. Ask each reference: did the project ship on time and on budget, how did the studio handle problems, and would you hire them again? A confident studio offers references without being asked.

---

9. What is your pricing model, and what drives costs up?

Fixed-price works when requirements are clear; time-and-materials is flexible but requires visibility; milestone-based balances risk on both sides. Hourly rates in 2026: agencies $150–$250/hr, boutique studios $60–$120/hr, freelancers $20–$60/hr. Ask what commonly causes overruns — third-party API complexity, unclear design direction, and late feature additions are the usual culprits. A specific answer means the studio has navigated those problems before.

---

10. What does your communication and reporting process look like?

Miscommunication causes a disproportionate share of failed projects. Ask how often you will receive written updates, what project tool both sides will use, and who your named contact is for decisions. A studio that cannot describe its communication process has not standardised one — and you will pay for the coordination overhead.

---

Strong vs. weak answers at a glance

Question	Strong answer	Weak answer
Live App Store links	Sends links immediately	”Most work is under NDA”
App ratings	Shares portfolio average	Cherry-picks one example
Post-launch support	Specific terms in the contract	”We will take care of you”
Who builds the app	Names specific people	”Our experienced team”
IP ownership	”Full IP transfer on final payment"	"You will have a license to use it”
References	Offers 2–3 contacts proactively	Hesitates or redirects to testimonials

---

Common questions

How many studios should I evaluate before deciding? Three to five is a practical range. Enough to compare approaches and pricing without spending a month in discovery calls. Require detailed written proposals from at least two finalists — including a milestone-by-milestone breakdown — before committing.

Should I always choose the studio with the most App Store experience? Raw volume matters less than category depth. A studio with twenty simple utility apps is not automatically better than one with six complex AI-integrated products if your project is AI-driven. Match the studio’s depth to your product’s demands.

What if a studio deflects on some of these questions? How a studio handles your questions before you sign previews how it handles problems after. Deflecting on IP, references, or team structure during the pitch is not a good sign. Transparency should be easy when there is nothing to hide.

---

Run this checklist in your next studio call and you will surface the answers that matter before the budget is committed.

If you want direct answers to every question on this list, get in touch. We are happy to walk through your project, share App Store links to our own products, and connect you with past clients. You can also explore our work, review our services, or read more on the Fera Tech blog.