Most of what goes wrong in a Sydney app development project is predictable. Not inevitable — predictable. The studio which is missing your timeline will typically have indicated that in the first talk. The contract which generates the surprise bill has the clauses to make it happen. And the team that goes silent after launch? If you know to ask then the way they treat post-launch always comes into play over the course of the selling process.
Our Sydney team would pass on to a trusted friend before they sign with any Sydney app development studio, including us, this checklist. Ten questions about where most projects really go wrong: the structure of the contract, IP ownership under Australian law, pricing model, team composition, compliance with the Privacy Act and what happens once the app is actually live.
We will discuss for every question the characteristics of a strong answer, of a weak answer, and what should make you run away with your mouth agape.
Aside from scope, this checklist is for signing with a Sydney studio, but not for determining the decision to build. If you’re still in that earlier stage, then head over to our Sydney app developer guide instead.
If you are evaluating studios across both cities, our Melbourne equivalent checklist covers the same ten questions with Melbourne-specific vertical expertise, R&D Tax Incentive guidance, and Collins Street studio context.
Why These 10 Questions Specifically
These are not the top 10 questions Sydney home buyers ask about Sydney studios. They’re the ten that will reliably bring up what information is relevant and important before you sign.
Portfolio, timeline and cost are some of the most common questions that most buyers ask. Those questions are important — but not sufficient, an impressive portfolio does not reveal the studio’s ability to communicate during the project, and a competitive quote does not guarantee who’s going to be responsible for the scope of something uncovered.
The two most common areas of issues are the contract layer and the process layer and these are explored below and most Sydney app development projects can be avoided issues that could have been identified prior to the initial invoice being raised.
Three of these are specific to Australian law and cannot be addressed in a generic manner by an offshore agency: IP assignment under Australian contract law, superannuation obligations of contractor staffed studios, and the December 2026 Privacy Act automated decision-making requirements.
Question 1: Is this a fixed price or time & materials contract?
This is the one question that should be answered straight, and not an explanation of how flexible they are.
Fixed price” — where the agency agrees to the scope, price, and timeframe in advance. If they underestimate it, they take the loss. You’ll have to pay for everything that doesn’t fit within the spec. Time and Materials is a style of billing that calls for paying per hour worked at a fixed rate, each increment of integration complexity, each design change, and all stakeholders revisions are billed, and the final price isn’t known when signing up.
What good sounds like: We do a structured discovery phase, after which we quote a fixed price. The development price is based on that scope document. If the scope changes outside what we agreed, a change order is raised before we build it.
Things to give up: “Time and material—it’s too hard to predict what apps will be worth.” This is the case when the scope is truly uncertain, but not when proper discovery has been conducted and the scope is not truly uncertain. If a studio cannot come up with a fixed price after discovery, then they haven’t done enough discovery.
To learn more about the two types of models and when to use each, read our fixed-price vs time-and-materials breakdown.
Question 2: Do you have a typical contract where you can provide me with the IP assignment clause?
Australian law stipulates that IP developed by a developer is not automatically transferred to you simply for being the purchaser – it must be assigned in writing. There are some Australian businesses that believe that the code they bought works for them, but which is actually the case is discovered when they attempt to move the project to another developer.
All IP rights and copyright in the source code and documentation and all related materials are assigned to you upon full payment by the correct clause. It should be free and unfettered, no license held by an agency, no retained rights, no restrictions.
What good sounds like: The studio can in 24 hours or less give you the IP assignment clause, explain it to you in normal English, and then it assigns you everything on final payment, no conditions whatsoever.
What to walk away from: “Of course you own it, you’re paying for it” but never actually demonstrate to you the clause. Verbal assurances aren’t enforceable under Australian law. Again, if not in the contract, it may not be transferred, even if discussed verbally.
Red flag someone that gives you a “licence” to use the software but not to own it outright. A licence is a contract that means ownership remains with the agency, and it may be terminated at any time. Ownership, not a licence – you’re looking for it.
Question 3: Was there a final price for each of your last 3 projects that is within 20% of the original quoted price?
This is the best question to ask of a studio than any portfolio review could ever be. A studio that has a discovery process which routinely falls into the 20% range of its quote has an accurate discovery process. The one that does blow that range on a regular basis is either underquoting to get the job or scoping poorly to start in the first place.
What it sounds like: A straightforward response with an easy to understand explanation of any differences, particularly if it was something that the client requested and not something the studio would have noticed.
What NOT to walk away from: evasion, “every project is different” or actually not being able to remember. A studio with structure delivery understands its numbers.
How to check: request two to three client references during the previous 12-month period and inquire directly about them, “Did the project fit the quoted price?” Never ask “were you happy with the work?”: this question is almost always answered with a yes and provides no information on cost accuracy.
Question 4: Who specifically will work on my project — and can I meet them before signing?
It’s not an answer of an experienced team. A $130–$160/hour Sydney studio for a “blended team” should be able to list the names of the project manager, lead developer and QA lead to be working on your project before you sign anything.
This is so that you can see if your project actually goes through in Sydney or it’s quietly subcontracted offshore. There are some Sydney-branded studios that do not refer to their locally developed studios and send them overseas. Directly ask: “Is the development team in Sydney? Where is it done and by whom if any work is done remotely or offshore?
Sounds good: names of people with LinkedIn profiles, an introduction to the lead developer and PM before committing to a signature, a simple and direct response regarding the location of the team.
What not to walk away from: fluffy language about ‘our experienced team’ or ‘our global talent network’ while expecting ‘Sydney rates’ and ‘Sydney accountability’. If the team is offshore, the rate should account for that and so should your expectations on overhead for communication.
Red flag: “We’ll give the team after the contract is signed. Before you commit to a project, they should be able to tell you who will actually be working on it, or you don’t really have the basis for determining if they’re a good fit.
Question 5: What is your change order process and how are scope changes dealt with?
There are changes in scope on all of the projects. The question is not if they’re going to happen, it’s how does the studio plan on dealing with them prior to implementation?
Anything not in the scope document is a change order process and will be discussed with you in a professional Sydney studio before any time is spent on building it. Australia does not recognize a scope change as a legally binding variation to a contract, unless it is agreed upon verbally.
What good boils down to: “If it sounds good, it gets put in writing as a change order detailing the additional scope, cost and timing implications. We don’t go on it until you’ve signed it off on in writing.
Things to give up: “We’re flexible and just make adjustments as they come. This is where time-and-materials projects go wrong: they end up being charged 50-80% more than originally estimated. There is no flexibility without process, it’s just another word for uncontrolled billing.
Request a copy of an actual sample change order document. One will be provided by a studio that has a professional delivery process.
Question 6: So far, how have you worked out the automated decision-making obligations under the Privacy Act for a December 2026 app such as mine?
The Privacy and Other Legislation Amendment Act 2024 amends the Privacy Act 1988 (Cth) (the Act) to include requirements for Australian apps employing automated decision-making on personal data to make it clear in their privacy policies that they are doing so. That includes credit recommendations, health triage, product recommendations, dynamic pricing, fraud scoring, and all sorts of other systems based on data algorithms that differentiate users.
Any Sydney studio actively building Australian apps in 2026 should know this requirement exists and should have a structured process for scoping it during discovery. A studio that doesn’t get a heads up on this will either overlook the compliance work altogether (hence leaving you vulnerable) or impose it as a cost change during the course of the project.
What good sounds like: one answer for how they discover automated decision-making during discovery, one answer for how much this costs an industry, ($2,000–$12,000), and one answer for who deals with the privacy policy legal review, a privacy lawyer, not the studio.
Things to avoid: “We will deal with compliance to the Privacy Act,” without any details. So, a studio that combines the two together is not quite understanding the difference between development scoping and legal review.
For the full budget and timeline impact of the December 2026 changes by industry, see our Privacy Act 2026 guide.
Question 7: What is my superannuation and tax responsibility for the developers of my project?
This is a particular concern in a studio with independent contractors and not full-time employees. In Australia, there are instances when businesses are required to provide super for their contractors. If a studio is silently shifting some of its compliance responsibilities to clients (and it should be) through the contract, then it’s shifting legal liability.
Please directly ask: “Are you the developers of my project, or are you independent contractors?” Who pays for their super, payroll tax and workers comp?
What good means: “Our developers are employees [or contractors who we hire through our own entity]; we take care of all their super, payroll tax, workers comp, etc.; it’s not your responsibility.
Don’t walk away from any deal where you have to pay a contractor directly, or contract that puts you liable for tax or super duties of those actually doing the work on your project. This is true for legal liability under the Superannuation Guarantee (Administration) Act 1992 (Cth) and ATO contractor rules.
The one that is most obviously an Australian question and one that all first time buyers miss is this one.
Question 8: What does “post-launch” support entail and what isn’t covered?
Twice as many Sydney app projects go amiss in 90 days after launch as in the build itself. All these things require constant development focus: production bugs that weren’t discovered in testing, App Store update requirements, users are not doing exactly what you assumed they would do during testing, platform policy changes, and more. If an artist agrees to do work in a studio without any contract, then it is gone when the final invoice is paid.
The question actually has two components: what is included in the contract and what the continued support will cost after the contract.
What good sounds like: “We provide 30 days of post-launch bug fix support for free, and a monthly maintenance retainer of $X,000 per month for OS updates, security patches and minor fixes, with new features being scoped and quoted separately.
The things you should avoid: “We provide 30 days of free support” without specifying anything else. Ask what Happens If An iOS Update Breaks Your App During Month Four? If the response is “we would quote that separately,” make sure to clarify the terms beforehand, and not after you’ve built a business.
Red flag: No post launch offering whatsoever, or terms that are mentioned only when you ask about them. To learn about the true cost of the annual operating budget (plus post launch maintenance costs), please read our true cost guide.
Question 9: Is there a non-technical founder that has used your studio in the past 12 months?
Reference is the one most effective tool of due diligence and, probably, the least used. Most buyers either do not bother to ask about them, or ask questions that they fail to get a clear answer on.
The kind of reference is important, it should be a non-technical founder or business owner within the past 12 months, not a 3-year-old CTO. You’re thinking about communicating with a non-technical client in the present delivery environment, right now.
The specific questions to ask the reference: did the project come in under the quoted price by 20%? Was the final time taken as originally promised? What was the communication between the studio when difficulties arose during the project? Would you use them again?
What good sounds like: good studios will provide you with two or three names and contact information within 24 hours and when you do call they’ll answer you directly and not require any prodding.
What not to do: “Our clients want to be kept confidential. There’s no need to refuse to provide references, there is only a need for clients to consent to sharing their contact information. A studio that has happy clients will have references that they can reach out to. If they cannot, consider that a serious WARNING.
Question 10: If you underestimate the project scope, what happens? And, is it possible to see this in the contract?
Fixed price, the studio takes the risk of underestimation. In time and materials, you do! So if you ask this straight out, and explicitly state in the contract, you will immediately know that this is a studio that really does mean business when they talk about “fixed-price”.
You read the contract specifically for: a scope document that is incorporated by reference (as is the definition of what is being built), a change order process that must be agreed upon in writing before any work is done that is not in scope, a payment schedule that is based on milestone completion, not elapsed time, and a defect liability period (30-90 days after the product is released) that allows the studio to fix bugs within its scope for free.
What good sounds like: “If we underestimate something that really was in the scope we agreed in our fixed-price contract, we take the hit on that. If you overestimate something that wasn’t in the scope of what we agreed on, that’s a change order. This is exactly where both of those situations fall in the contract.”
Don’t walk away from: a contract which contains a “scope may evolve” clause without a specific change order process. In most cases, it’s a simple, yet underhanded way to pass unlimited cost risk to you as ‘agile’.
For the full contract checklist covering every clause a Sydney app development contract should include, see our non-technical founder guide.
The 8 Red Flags That Should End Any Sydney Conversation
If you notice these eight signs in the evaluation or just before signing, you should be able to say goodbye to any Sydney studio.
- A quoted fixed price within 24 hours of your initial brief. No discovery happened. That’s an estimate and that’s going to change.
- Of course you own the code’ without producing the IP assignment clause. Verbal assurances are not contracts. Under Australian law, IP does not transfer without an explicit written assignment. Promises are not promises. In Australia, the transfer of IP is not automatic, but must be expressly stated in writing.
- When there is no one who is going to work on your project when you sign. Our team is not a project team. You’re paying for somebody with a particular skill set.
- References that are more than 3 years old, from a completely different industry or from a company that is also the sponsor or partner of the studio – it’s a testimonial, not a real reference.
- Prices are much less than $100 an hour from a “Sydney studio”. This is typically a reference to an offshore delivery with a Sydney address. Point out the place where development actually takes place.
- If you use automated decision-making in your app, then you must have an answer (or an obvious one) to the December 2026 Privacy Act question. As an active Sydney studio in 2026, it is well known.
- A contract in which the first payment is over 30-40% of the value of the project itself. Do not give over 30-40% payment to any development studio.
- Post launch support will be dealt with after the launch. Initial terms in the contract must include post launch. Once it is launched, it’s too late to be negotiating it.
How to Run This Checklist: A Practical Process
Do this on all the studios you are considering, and not just the studio that you are already considering! The comparison is informative and the answers that each studio provides tell you just about as much as the answers.
In advance: ask for the standard contract sheet and IP assignment clause for the studio. A pro studio won’t hesitate to send it. Before meeting even begins, review Questions 1, 2 and 10 in light of what actually is in the contract.
In the first meeting: Discuss Questions 3–9. Write down each answer but also write down how the answer is said. Evasion, deflection and uncertainty in the sales process are good indicators of the same in the sales process while the project is running.
Following the meeting: make contact with the references from Question 9. Specifically inquire about the accuracy of costs and the process of communication that occurred during the occurrence of cost problems. If your reference is not willing to talk about a particular issue, he or she is not providing you with the information you need.
Before signing: make sure that Questions 2 and 10 are actually written in the contract document and not just verbally during the meeting. The project is regulated by the contract. Any oral prior notice is not binding.
To determine if your quote is within the market range for Sydney, refer to our Sydney app developer rate guide.
The 10-Question Checklist Summary
The ten questions above reduce a complex, high-stakes decision to a structured, repeatable process. They are not the only questions to ask a Sydney app developer — but they are the ten that reveal the information most commonly missing when a project goes wrong. These are not the only questions to ask a Sydney app developer, but they’re the top 10 that always bring up what is typically missing when things go wrong.The three which are most important: Question 2 (the IP assignment clause) as it is an Australian legal requirement many buyers find out too late. I’m going to go ahead and pick a question that I think every studio that’s live will be familiar with, which is question 6 (Privacy Act 2026). And Question 10 (what if they underestimate?), since the answer in the contract will tell you if the certain pricing is genuine or a pleasant phrase they used during the sales call.
We’re a Sydney App Development Studio ourselves and we have responded to these 10 questions for all our projects that we have ever taken on from our Barangaroo Avenue Studio. If you would like to ask us these questions before you make any decision whatsoever, simply contact us for a complimentary consultation and we will answer them all on the record!
Questions to Ask a Sydney App Developer, Frequently Asked Questions
Q1: Which are the most crucial questions to ask the app developer Sydney before signing up?
The ten most important questions before signing with a Sydney app developer: (1) Is this fixed-price or time-and-materials? (2) Can I see the IP assignment clause? (3) Were your last three projects within 20% of the quoted price? (4) Who specifically will work on my project and can I meet them? (5) How do you handle scope changes? (6) How have you scoped the December 2026 Privacy Act obligations? (7) What are your superannuation obligations for contractors? (8) What does post-launch support include and exclude? (9) Can I speak to a non-technical founder reference from the last 12 months? (10) What happens if you underestimate the scope and where is this in +the contract?
Q2: Does IP automatically transfer to me when I pay a Sydney app developer?
No. IP generated by the Developer does not pass to you on payment under Australian contract law, it must be specifically assigned by the Developer in writing. Before you sign a Sydney developer’s standard contract, have them demonstrate the IP assignment clause. It shall transfer to you all the right to the use of the IP rights, the copyright relating to the source code, the documentation, other materials, without reservation, without conditions and without retained licence. Without this written clause to support it, a verbal “you own the code” is not legally binding in Australia.
Q3: What’s the December 2026 Privacy Act obligation Sydney developers should know about?
The Privacy and Other Legislation Amendment Act 2024 will introduce a new requirement for any Australian application that relies on automated decision making of personal data to include this in its privacy policy from 10 December 2026. That includes credit scoring, health triage, tailored recommendations, adjustable pricing, fraud scoring and any algorithmic systems that look differently at users because of their data. Any Sydney app development studio that is actively developing apps for the Australian market in 2026 should be able to explain how they scope this in to discovery and what it has to do with the build cost. If they cannot get engaged in the question at all, this work will be missed or will become a cost variation during the project.
Q4: What questions should I pose a Sydney studio about superannuation?
Have the developers on your project confirm their status as employees or independent contractors and who is responsible for their super, payroll tax and workers comp. Some contractual agreements may result in superannuation liabilities being assumed by the engaging party under Australian law. A professional Sydney studio will verify that all obligations of the employer(s) and contractor(s) are included within the Sydney studio entity and not on your shoulders.
Q5: What is the initial amount I will need to pay a Sydney app developer?
Do not pay up to 30-40% of the total project cost as a lump sum deposit. The common approach to milestones for fixed price work is 30–40% at contract sign, 30–40% at design signoff or project start and 20–30% at App Store launch and project completion. Anything that requires more than 40% up front is outside industry standards and puts a lot of risk on you before you have received anything.
Q6: So what exactly does a true fixed price Sydney Contract offer?
It ensures a committed price for a clearly outlined set of tasks in a defined timeframe. It should contain a scope document incorporated by reference; a change order process which must be approved in writing before any work that is out of scope is done; milestone payments based on actual deliverables; a clear IP assignment clause for work done after the work is complete but before the end of the defect liability period; and a defect liability period of 30 to 90 days during which bugs can be fixed after the work has been completed but prior to the end of the term. If any of that is absent, then it’s not a true fixed price, it’s a time and materials contract with a ceiling you can sneak up on with scope changes.
Q7: How to check the authenticity of a Sydney app developer’s references?
Request 2-3 non-technical references from the past 12 months who are not the CTO or technical stakeholder, but rather a founder or business owner. Call them on your own, rather than take written referrals. Inquire specifically, was the project contained in the original quoted price, did it get done on time, and how did the studio communicate if something did go wrong mid-project? A real reference will address all three points. Anyone who gives general praise or doesn’t remember specific details is doing little to no due diligence.
Q8: Is it OK for a developer in Sydney to hire people overseas and not let me know?
It does occur and it is not illegal, but should be mentioned. Another approach is to pass off the client relationship for one or two local studios, while keeping the client uninformed and providing the real build to an offshore team without so much as a word. This impacts your actual hourly cost of your creation, your communication burden as well as the IP jurisdiction of the folks actually creating your product. Please ask outright, “Do your development team operate in Sydney? Where and by whom “is there any work done remotely or offshore?”. A pro studio will respond to this question without a doubt.