How to choose
an app developer

What type of developer do you need?

Before you start evaluating anyone, get clear on what you actually need. The answer shapes every other decision.

Agency vs freelancer. An agency brings a team, a process, and accountability across design, development, and QA. A freelancer brings flexibility and sometimes lower cost, but you carry the coordination risk. For non-technical founders building a consumer app for the first time, an agency with a structured process is usually the safer choice. The problem when something goes wrong is not just fixing it, it is knowing there is a problem in the first place. A freelancer who goes quiet or drops scope leaves you stranded in a way a structured agency generally does not.

Local vs offshore. Offshore development is cheaper on paper. In practice, time zone gaps, communication friction, and rework cycles often erode the saving. More importantly, as a non-technical founder, you need a developer who will fill knowledge gaps and flag issues in plain language. That relationship is harder to build across a language barrier and a 5-hour time difference. Read more in offshore vs local app development.

Specialist vs generalist. Some agencies will say yes to any build. Some have a clear focus. If you are building a consumer app, look for agencies that have built consumer apps before, not ones whose portfolio is split between e-commerce integrations, corporate dashboards, and your type of product.

Portfolio: what to actually look for

Portfolio review is where most founders go wrong. They look at the logos, the screenshots, and the case study copy, and decide the agency is good. None of that tells you what you actually need to know.

What you want to find is:

• Full products they built from scratch, not feature additions or upgrades to existing apps
• Products at a similar stage to yours, launched by a non-technical or first-time founder
• Products that are still live and have users, not abandoned MVPs
• Evidence they can do the design work, not just the code

When you look at a case study, ask: when was this built and is it still live? What was the founder's background? What did they specifically contribute? Do not accept a case study as a reference without being able to speak to the founder directly.

Engagement model and access

The single biggest predictor of a good or bad agency experience is whether you have direct access to the person actually building your product.

Large agencies often run an account management model. You have a dedicated account manager or project manager as your main contact. That person is not a builder. They translate between you and the dev team. Every question you have goes through them. Every concern you raise gets filtered. By the time feedback reaches the person writing code, it has been paraphrased at least once.

For a technical buyer who knows what they want and can specify it clearly, this model works fine. For a non-technical founder trying to communicate a product vision and needing someone to challenge bad decisions, it adds friction and creates gaps.

Before you commit to any agency, ask: who will I be talking to in our weekly calls? If the answer is a project manager who is not involved in building, ask whether you can have direct access to the lead developer and designer on your project.

Also ask about team structure. Are the developers employees of the agency, or subcontractors? Is development done locally or offshore? Neither answer is automatically disqualifying, but you want to understand the chain between your product vision and the person implementing it.

Pricing and commercial model

There are two main pricing models: fixed price and time-and-materials (T&M). Each has genuine tradeoffs.

Fixed price gives you cost certainty. You know the number before you sign. The risk is that to deliver a fixed price, the agency has to scope tightly. Anything outside that scope costs extra. If your requirements evolve during the build (and they will), you pay for every change. Fixed price works best when the scope is very well-defined before the build starts.

Time and materials gives you flexibility. Changes during the build are absorbed into the ongoing work. The risk is that without discipline, scope creeps and the final bill is higher than expected. T&M works best when you are working with a team you trust and who have a strong process for flagging cost impacts before they happen.

On pricing level: quality Australian app development starts at around $80,000 for a consumer app build. Quotes significantly below that, especially from agencies claiming to be Australian, usually mean offshore development, junior team, or scope that has been cut to the point where the product will not work as intended. The hidden cost of a bad build is always more than the difference between quotes.

IP, code ownership, and handover

This section is non-negotiable. Before you sign anything, you need clarity on three things:

• IP ownership: all code, design files, and assets should transfer to you on completion or on payment milestones, not retained by the agency
• Repository access: you should have access to the code repository from day one, not just at the end
• Infrastructure: your app should be deployed on your own accounts (AWS, Google Cloud, Apple Developer, etc.), not the agency's infrastructure

Some agencies will try to maintain leverage by retaining code ownership until final payment, or by hosting on their infrastructure. Both create dependency. If the relationship ends badly, you are in a difficult position.

On handover: when the build is done, you should receive a full handover package including code repository, credentials, design files, documentation, and a handover session. If the agency cannot tell you what the handover includes before you sign, that is a problem.

Red flags to watch for

These patterns show up regularly in bad agency experiences. None of them are guarantees of a poor outcome, but each one is worth a direct conversation before you proceed:

• They say yes to everything in the sales process without pushing back on any of your assumptions
• They cannot give you a reference from a founder at a similar stage to yours
• All portfolio work is more than two years old
• They use a lot of technical language without checking whether you understand it
• The quote came back very quickly and feels very cheap
• They cannot tell you who will specifically be working on your project
• There is no clear process for handling scope changes or budget overruns
• IP ownership is vague or retained by the agency until final payment
• Communication during the sales process is slow or disorganised

How they treat you during the sales process is usually a fair signal for how they will treat you during the build. If they are hard to get hold of before you have committed, it will not improve after.

Questions to ask before you sign

Run this list with every agency you are seriously considering. The answers will either build confidence or reveal problems before they cost you.

• Who specifically will be working on my project day-to-day, and can I meet them before we start?
• Can you show me an app you built from scratch for a founder at a similar stage to me, and can I speak to that founder?
• How do you handle scope changes mid-build, and what is the process for approving additional costs?
• Who owns the IP and code at each stage of the project?
• Will the app be deployed on my accounts or yours?
• What does handover include, and what do I receive at the end of the engagement?
• How will you communicate progress, and how do you flag problems when they arise?
• What happens if the project runs over time or over budget?
• Do your developers work in-house or are they contractors or offshore?
• What is your capacity right now, and when could you start?

A good agency will answer all of these clearly and without defensiveness. Any evasion or vagueness on IP, team, or scope handling is a signal to probe further or walk away.