To get an app built for you without getting burned, do five things before anyone starts: write a one-page scope, own every account in your company's name, pay by milestone instead of up front, put code ownership in the contract, and compare quotes against the same written scope. Owners who get burned rarely hired a bad developer on purpose. They skipped one of these, and the problem showed up months later.
I've seen the aftermath many times: an owner with half an app, a developer who stopped replying, and no access to the code. Every one of those stories was preventable on day one.
Key Takeaways
- The burn usually starts with a vague scope. Two developers quoting "an app like X" are quoting two different apps.
- Register the domain, hosting, app store accounts and code repository to your company, then give the developer access. Never the other way around.
- Pay in milestones you can see and test. A large deposit before anything exists gives away your only bargaining power.
- A free Honest Read from Sol gives you a written scope and a short spec any developer can quote from, before you talk to anyone.
Five Ways Owners Get Burned When They Get an App Built
| How it goes wrong | What it looks like | How to prevent it |
|---|---|---|
| Vague scope | Quotes of $9,000 and $70,000 for "the same app" | Send every developer the same one-page scope |
| Accounts in the developer's name | You can't log in to your own hosting | Create the accounts yourself, then invite them |
| Paying up front | 50% deposit, then silence | Milestones tied to working screens you can test |
| No code ownership | The developer "licenses" you the app | Contract says the code and IP transfer to you on payment |
| Choosing the cheapest quote | Cheap start, endless change orders | Ask why quotes differ; read the questions each developer asked |
Vague scope. Write one page: one user, one job, the screens, the hard parts, and what's out of version one. Our MVP scope document template gives you the form.
Accounts. Domain registrar, hosting, the Apple and Google developer accounts, the code repository, the database. All in your company's name. The full list is in accounts you should own before a developer builds your app.
Payment. Break the project into milestones, each one something you can click through. "Login and today's jobs list working on my phone" is a milestone. "40% of backend done" is not. See how to pay for custom software in milestones.
Ownership. In the US, whether you own code a contractor wrote depends on the contract, so make it explicit. We cover the basics (general information, not legal advice) in who owns the code a contractor writes.
Cheapest quote. A low quote with zero questions usually means the developer priced an easier app than yours and plans to bill the difference later.
How to Compare Quotes When You Get an App Built
Put the quotes side by side and ask four questions:
1. Did they quote the scope you sent, or something they imagined?
2. What questions did they ask? Good developers find the hard parts fast.
3. What's included after launch: bug fixes, a warranty period, hosting setup?
4. What happens if they disappear: do you have the code and the accounts every week, or only at the end?
If you're weighing a freelancer against an agency, our freelancer vs agency piece covers the cost-and-risk tradeoff, and how to vet a development agency has the checks.
A Concrete Version
A physical therapy clinic owner wants a booking and exercise-reminder app. Two ways the same $24,000 project can go:
The burned version. The owner pays a $12,000 deposit (50%) on a verbal description. The developer sets up hosting on their own account "to move faster." Four months later, the app half works, the developer has moved on to a bigger client, and the owner has no login to the server. Getting the code back means a lawyer, and finishing it means a second developer reading someone else's work.
The protected version. The owner writes a one-page scope and gets three quotes against it: $19,000, $24,000 and $41,000. She picks the $24,000 team because they asked the sharpest questions about the patient data. Payment is four milestones of $6,000, each released after she tests working screens on her phone. The repository and hosting are in her clinic's name from week one. If the team vanished after milestone two, she'd have paid $12,000 and own working code she could hand to someone else.
Same budget. Very different worst case.
Patient data adds legal requirements here. This is general information, not legal advice; ask a professional before building anything that stores health information.
The Honest Counterpoint
All this protection has a cost. Milestones mean more check-ins, owning accounts means you handle billing for a few services, and a written scope takes an afternoon you'd rather spend on your business. For a $1,500 job (a landing page, a small form tool), a handshake and a trusted freelancer can be perfectly fine.
Also, these steps protect you from a bad process. They don't make a bad idea good. If you're not sure the app should exist, answer that first; our short app feasibility study walks through it.
Frequently Asked Questions
How do I get an app built for me if I'm not technical?
Write a one-page scope, create the accounts in your company's name, get at least two quotes against the same scope, and pay in milestones you can test. You don't need to understand the code to check that a milestone works on your phone.
How much should I pay up front to get an app built?
As little as possible. Tie payments to working milestones. A small first milestone is normal; a large deposit before anything exists gives away your bargaining power.
Who owns the app if I pay someone to build it?
It depends on the contract. Make sure it says the code and IP transfer to you on payment. This is general information, not legal advice.
The Bottom Line
Scope it, own the accounts, pay by milestone, get the code in writing, and compare quotes on the same page. To start with the scope, get a free Honest Read from Sol: it ends with a short spec any developer can quote from, and the read is yours to hand to anyone, including someone who isn't us. Here's what the Honest Read includes. If you'd like it built at a fixed price with full IP transfer and a 90-day warranty, see the software factory.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
