What your app developer isn't telling you
I run an app development agency. I'm about to tell you everything the industry would prefer you didn't know.
Not because every agency is dodgy. Most aren't. But there are things that are standard practice in this industry that are genuinely bad for clients. Things that get buried in contracts, glossed over in sales calls, or explained with just enough jargon that you nod along without really understanding what you agreed to.
I've sat on both sides of this table. I've worked at agencies that did some of this stuff. Now I run one that doesn't. Here's what to watch for.
Hourly billing is designed to benefit the agency, not you
Let's start with the big one.
Most agencies bill by the hour. They'll give you an "estimate" of, say, 800 hours at $180/hour. That comes out to $144,000. Sounds reasonable. You shake hands.
Then at hour 600, you get an email. "We've run into some complexity we didn't anticipate. The revised estimate is 1,100 hours." Your $144k project is now $198k. And you're too deep to walk away.
Here's what nobody tells you: under an hourly model, the agency has zero financial incentive to be efficient. Every extra hour is more revenue. Every "unforeseen complexity" is a line item. The slower the project goes, the more they make.
I'm not saying agencies deliberately drag things out. Most don't. But the incentive structure is pointing the wrong way, and you should know that going in.
What to ask instead:
- "Can we do fixed-price for defined phases?" This forces the agency to estimate properly because overruns are their problem, not yours.
- "What's included in the estimate and what's explicitly excluded?" Get this in writing. Vague scope documents are where budget blowouts start.
- "What happens if the project takes longer than estimated?" If the answer is "you pay more," that tells you everything about where the risk sits.
For a deeper look at how pricing works in Australia, read our complete cost guide.
The quote doesn't include everything you need to launch
A common trick (and sometimes it's not even intentional, just sloppy scoping) is quoting the build without everything you need to actually go live.
Things that are regularly left out of initial quotes:
- App Store submission and approval. Someone has to set up your developer accounts ($99/year for Apple, $25 one-time for Google), prepare screenshots, write descriptions, handle the review process, and deal with rejections. This takes 10-20 hours depending on complexity.
- Backend infrastructure. Your app needs a server. That server costs money every month. Hosting, databases, CDN, email services. For a typical consumer app, expect $200-800/month depending on user volume. Some agencies quote the app build but not the backend, then surprise you later.
- Third-party service costs. Push notifications (Firebase is free to a point, then costs scale). Payment processing (Stripe takes 1.75% + 30c per transaction in Australia). SMS verification. Analytics. Maps. These add up to $100-500/month before you have a single paying user.
- Testing on real devices. Some agencies only test on simulators. Real devices behave differently. If testing across 8-10 device types isn't in the quote, ask why.
- Post-launch bug fixes. Every app launches with bugs. Every single one. If there's no warranty period (we include 60 days), you'll be paying hourly to fix issues that should have been caught before launch.
Ask your agency to list every cost you'll incur in the first 12 months. Not just the build. Everything. If they can't give you that number, they're either hiding it or they haven't thought about it. Both are bad.
Scope creep is a feature, not a bug
Agencies love scope creep. Not because they're evil. Because scope creep is extremely profitable.
Here's how it works. During the build, you'll have ideas. Good ones, usually. "Hey, what if we also added a chat feature?" "Can we integrate with Shopify?" "Users should be able to share to Instagram directly."
A good agency will tell you: "Great idea. Let's add it to the v2 backlog and focus on shipping v1." A mediocre agency will say: "Sure, we can add that. It'll be an extra 80 hours." And because you're excited and mid-build, you say yes. Then it happens again. And again.
I've seen projects go from $120k to $220k purely through in-build additions that could have waited until after launch. The founder didn't even realise how much they'd added until they got the final invoice.
The fix is simple but requires discipline:
- Lock the scope before development starts. Detailed, written, signed off. Every screen, every feature, every integration.
- Create a "v2 parking lot." Every new idea goes here. You're not saying no. You're saying "after launch."
- Require a formal change request for anything new. With a cost estimate and timeline impact, in writing, before work begins.
Our development process guide explains how we handle scope management, if you want to see what a structured approach looks like.
"Maintenance" is the most misunderstood word in app development
After your app launches, your agency will offer you a "maintenance package." Sounds straightforward. Keep the app running, fix bugs, make small updates. Usually $2,000-5,000 per month.
What most founders don't realise is that "maintenance" can mean wildly different things depending on who you're talking to.
At a minimum, maintenance should include:
- OS updates. Apple and Google release major OS versions annually. Your app needs to be updated to stay compatible. If you skip this, your app starts breaking for users who update their phones. This alone can be 40-80 hours per year.
- Third-party SDK updates. Every service your app uses (Stripe, Firebase, analytics tools) releases updates. Some are mandatory. If your payment SDK falls behind, transactions start failing.
- Security patches. Vulnerabilities get discovered in libraries your app uses. These need to be patched. Quickly.
- Server uptime monitoring. Someone should be watching whether your backend is actually running. At 2am on a Saturday, not just during business hours.
- Bug fixes for issues discovered after launch. Real users find bugs that testing didn't. Maintenance should cover fixing these without charging you extra per bug.
What maintenance should NOT include (but agencies often bundle in):
- New features. That's development, not maintenance.
- Design changes. Also development.
- Marketing support, analytics reporting, or "strategy calls." These are separate services being padded into your maintenance bill.
Ask for a line-item breakdown of what's covered. If the agency can't clearly define what your $3,000/month buys, you're paying for vagueness.
You probably don't own what you think you own
This one catches founders off guard constantly.
You paid $150k for an app. You own it, right? Maybe. Maybe not. Check your contract for these specific things:
- IP assignment clause. Does the contract explicitly state that all intellectual property created during the project transfers to you upon final payment? If this clause is missing or vague, the agency may retain ownership of the code.
- Source code access. Some agencies host everything on their own infrastructure and don't give you access to the raw source code. If you ever want to switch agencies or bring development in-house, you're locked in.
- Third-party licenses. Your app uses open-source libraries and third-party code. Make sure the agency documents what's included and confirms the licensing is compatible with commercial use.
- Design assets. Do you own the Figma files? The design system? The icon sets? Or just the final output? If you don't own the design files, rebranding or redesigning later becomes much harder.
Get explicit, written confirmation that you own everything: code, designs, assets, documentation. Before you sign. Not after.
Launching without a strategy is the most expensive mistake
Here's the one that hurts the most. And agencies rarely mention it because it's not their problem.
Building the app is maybe 40% of what it takes to succeed. The other 60% is what happens after launch. User acquisition. Retention. Monetisation. Feedback loops. Iteration based on real data.
I've watched founders spend their entire budget on the build, launch to crickets, and have nothing left for marketing. The app was good. The launch strategy was nonexistent.
Before you commit your budget, answer these questions:
- How will your first 1,000 users find your app?
- What's your customer acquisition cost target?
- What does your monetisation model look like in month 1 vs month 12?
- How much budget are you reserving for post-launch marketing?
- What metrics will you track in the first 90 days to know if the app is working?
If your agency isn't asking you these questions during the scoping phase, they're building you a product without caring whether it succeeds as a business. And you're paying them either way.
The best agencies won't just build what you ask for. They'll push back, ask hard questions, and occasionally talk you out of features you don't need yet. That tension is valuable. If everyone's just nodding, nobody's thinking.
How to protect yourself
This isn't about being paranoid. It's about being informed. Most agencies are full of talented, well-meaning people. But the industry's standard practices have some structural problems that favour the agency, and you need to know that going in.
Quick checklist before you sign anything:
- Get a fixed-price quote for defined phases, not just an hourly estimate
- Ask for a full 12-month cost projection including hosting, third-party services, and maintenance
- Lock scope in writing before development starts
- Confirm IP ownership transfers to you upon payment
- Demand source code access and repository ownership
- Get a clear, line-item maintenance agreement
- Reserve 20-30% of your total budget for post-launch marketing and iteration
The founders who ask these questions upfront are the ones who don't get burned later. Knowledge is leverage. Now you have some.
