Executive Summary
The uncomfortable thing about failed outsourcing engagements is how visible the warning signs were beforehand. Almost always, in hindsight, they were sitting in the first sales call.
The problem is that red flags do not announce themselves as red flags. They arrive as reassurance, enthusiasm, and a rate that looks better than everyone else’s. A vendor who says yes to everything feels like a good vendor right up until month four.
The numbers give some sense of the stakes. Standish Group’s CHAOS research consistently finds only around 31% of software projects finish on time, on budget, and within scope. PMI data puts scope creep at roughly 52% of projects with an average cost overrun near 27%. Not all of that is vendor fault but a meaningful share is, and most of it was predictable at selection.
If you are currently shortlisting an outsourcing provider, this article is the pre mortem. Twelve warning signs, what each one actually indicates, and the specific question that surfaces it before you commit.
Key Findings
- Delivery baseline: Only around 31% of software projects finish on time, on budget, and within scope according to Standish Group CHAOS research
- Scope creep prevalence: Roughly 52% of projects experience scope creep, with an average cost overrun near 27% per PMI data
- Governance gap: PMI reports mature governance organisations complete approximately 89% of projects on time and on budget, against 36% for low maturity organisations
- Change control: Projects with no formal change control process are approximately twice as likely to fail as those with one in place
- Turnover risk: Annual attrition at typical offshore delivery centres runs 20 to 30%, which directly threatens engagement continuity
- Large project overruns: McKinsey research puts the median cost overrun for large IT projects at approximately 45% of the original estimate
- Market context: Deloitte’s 2024 Global Outsourcing Survey found 80% of executives plan to maintain or grow outsourcing investment, meaning more engagements and more failure exposure
Red Flag 1: The Rate Is Well Below Everyone Else’s
A quote sitting 40% under the rest of your shortlist is not a bargain. It is information.
There are only a few ways a provider gets meaningfully cheaper than the market. Junior engineers presented as mid level. Shared resources billed as dedicated. Costs stripped out of the rate that reappear as separate charges in month three. Or an unsustainable margin that resolves itself through attrition or a rate rise at renewal.
The hidden cost is supervision. If your Australian senior engineer spends ten hours a week correcting output, and their loaded cost is around AUD 123 an hour, that is roughly AUD 60,000 a year in cost that never appears on an invoice.
Ask this. What is included in the rate, itemised, and what will be billed separately over a twelve month engagement? Get it in writing.
Red Flag 2: Recruiters Conduct the Technical Interviews
This one is easy to miss because nobody volunteers it.
Ask who conducts the technical evaluation and what their engineering background is. If the answer is a talent acquisition specialist working from a competency checklist, the provider is filtering for interview performance rather than engineering capability.
Ask to see the actual assessment. Not a description, the artefact. A provider serious about screening will show you the live coding exercise and the evaluation rubric. A provider that cannot produce either is screening on CVs.
Then ask the number that matters. What proportion of placed engineers are replaced within the first three months at client request?
Red Flag 3: Retention Gets Answered With Awards
You ask about developer churn. You receive a workplace award, an employee recommendation score, or a company wide retention figure.
Those measure different things. Company wide retention includes administrative and support staff, who churn far less than engineers. Employee recommendation scores measure sentiment, not tenure.
Industry commentary puts annual attrition at typical offshore delivery centres between 20% and 30%. At 25%, a four person team loses someone every year, and each departure costs the replacement search, the ramp up, and the accumulated codebase context.
Ask precisely this. What is your developer churn rate on active client engagements over the last twelve months, and what is your longest running engagement with the original engineers still in place?
Red Flag 4: Nobody Pushes Back on Your Brief
A provider who agrees with every requirement, accepts every timeline, and never questions an assumption is not being accommodating. They are being commercially cautious.
Good technical partners argue with you before the contract is signed, because that is when arguing is cheap. If your brief contains a contradiction, an unrealistic timeline, or a technical choice that will not scale, you want to hear about it in week one rather than month five.
The same applies to fixed price quotes against loose briefs. A provider willing to fixed price a two page brief either has not read it properly or is planning to recover margin through variation orders. Any experienced offshore software development company knows a vague brief cannot be priced accurately, and the honest ones say so.
Ask this. What concerns do you have about our brief, and what would you change?
Red Flag 5: No Defined Change Control Process
This is the single most common source of outsourcing disputes, and the research supports treating it seriously. Projects with no formal change control process are roughly twice as likely to fail as those with one in place.
Yet change control rarely comes up in sales conversations, because it is nobody’s favourite topic.
Ask how a change gets raised, priced, approved, and scheduled, and what the turnaround commitment is. Under a fixed price arrangement, ask what the variation pricing basis is. Under a dedicated team arrangement, confirm that changes are handled in sprint planning without formal variation at all, which is one of the model’s genuine advantages.
If the answer is that changes get discussed as they arise, you have found the clause that will cost you money in month six.
Red Flag 6: The Team Composition Is Vague
You ask who will be working on your project. You receive a description of the provider’s general capability.
Named engineers with specific CVs and confirmed availability is the standard. Anything less means the team gets assembled after you sign, from whoever happens to be available, which is a different proposition to the one you were sold.
Watch particularly for the bait and switch pattern where senior engineers appear in the pitch and pre sales technical discussions, then a more junior team delivers the work with senior oversight promised in the background. Oversight is not the same as delivery.
Ask this. Which specific engineers will be assigned, can I interview them, and what is their current availability? If you need a dedicated offshore developer embedded in your team, interviewing them before commitment should be non negotiable.
Red Flag 7: Timezone Overlap Is Described Rather Than Documented
Timezone gets discussed abstractly then bites concretely.
Providers often describe overlap in terms of geography rather than working schedule. A provider three hours away that runs its own shift pattern may deliver less practical overlap than the map suggests. For multi country providers, the country your particular engineers sit in matters more than the countries the company operates in.
Ask three specific questions. Which country will my engineers physically sit in? What hours do they work in Australian Eastern time? And what is the documented escalation path and response commitment for an issue raised at 2pm AEST?
Description is not documentation. Get the escalation path written into the engagement terms.
Red Flag 8: USD Billing on a Long Engagement
This one is easy to overlook because it feels like an administrative detail rather than a commercial risk.
Over a twelve month engagement, a five cent move in AUD/USD changes your actual spend by around 7%. That is frequently larger than the difference between two shortlisted vendors, which means a currency movement can retrospectively make the wrong choice look like the right one.
There is a second dimension. Ask which country’s law governs the contract and where disputes would be resolved. An offshore entity in a jurisdiction you have never dealt with is a meaningfully different risk position to an Australian entity under Australian law.
Ask this. Can you bill in Australian dollars, through an Australian entity, under Australian contract law?
Red Flag 9: Reporting Is a Monthly PDF
Live dashboards showing sprint velocity, defect rates, and hours consumed against forecast are the standard in 2026. A monthly summary document is a generation behind on operational maturity.
The deeper issue is what monthly reporting implies about governance. PMI reports organisations with mature governance complete around 89% of projects on time and on budget, against 36% for low maturity organisations. Reporting cadence is a reasonable proxy for governance maturity.
If you have to email someone to find out how the work is progressing, you are the reporting system.
Ask this. What reporting do I receive, how often, and can I see a sample dashboard from a live engagement?
Red Flag 10: IP Transfers on Final Payment
Read the intellectual property clause carefully, and read the timing.
Some contracts transfer code, documentation, and designs only on final payment. That is defensible from the vendor’s perspective and uncomfortable from yours if a dispute arises mid engagement, because your leverage disappears exactly when you need it.
Check three things. When does IP transfer occur? Is there a data processing agreement covering how your data is handled and where it is stored? And what access controls apply to production systems and customer data?
For Australian businesses subject to Privacy Act obligations, the data handling terms are not boilerplate. Any provider engaged to outsource IT services touching customer records needs specific answers here, not general reassurance about rigorous standards.
Red Flag 11: No Pilot Available
A provider confident in their delivery offers a defined pilot on real work. Reluctance, or insistence on a long minimum commitment before any trial, is itself an answer.
Watch for the softer version of this too, where a pilot is offered but structured to guarantee success. A toy exercise with no dependencies and no ambiguity proves very little. Insist on genuine scope with a measurable outcome, and include a deliberate mid pilot priority change, because how a team handles change is more revealing than a clean run.
Ask this. Will you run a thirty to sixty day pilot on real scope with success criteria agreed in writing beforehand?
Red Flag 12: Exit Terms Are Missing or Punitive
Exit terms get skimmed because nobody signing a contract is thinking about leaving.
That is precisely why they matter. The exit clause preserves your leverage for the entire engagement. Without a reasonable notice period, a defined handover scope, and clarity on whether handover is billable, you negotiate from a weak position at every renewal and every rate review.
Check the notice period, the handover deliverables, whether documentation and knowledge transfer are included or billed, and whether there are penalties for early termination beyond the notice period.
Ask this. What does exit look like in practical terms, and what does it cost?
Red Flag Bonus: Portfolio Without Contactable References
Logos on a website are the cheapest form of credibility available and the least informative. Ask for two contactable references in your sector, ideally on engagements of similar size and duration to yours. Then ask a specific question when you speak to them: what went wrong during the engagement and how was it handled? Every engagement has something go wrong. A reference who claims otherwise has been coached. Watch also for portfolios weighted toward projects completed years ago, or toward work in a different discipline to yours. A provider with an impressive custom mobile app development portfolio and no backend platform experience is not a match for a backend platform build, regardless of how good the app work looks. The related warning sign is a case study with no numbers. Delivered a scalable platform for a leading retailer tells you nothing. Reduced page load from 4.2 seconds to 900 milliseconds across 40,000 daily sessions tells you the provider measures outcomes. Businesses looking to hire software developer capacity through a provider should treat unquantified case studies as marketing rather than evidence.
Red Flags Summary Table
| Red Flag | What It Usually Indicates | The Question That Surfaces It |
|---|---|---|
| Rate far below market | Junior substitution, shared resources, or hidden charges | What is included, itemised, and what is billed separately? |
| Recruiter led technical interviews | Screening for interview skill, not engineering skill | Who conducts technical evaluation and what is their background? |
| Retention answered with awards | Developer churn is not measured or is unflattering | What is developer churn on client engagements this year? |
| No pushback on the brief | Commercial caution, or brief not properly read | What concerns do you have about our brief? |
| No change control process | Disputes and variation costs later | How is a change raised, priced, approved, and scheduled? |
| Vague team composition | Team assembled post signature from availability | Which named engineers, and can I interview them? |
| Timezone described not documented | Practical overlap narrower than geography implies | What hours in AEST, and what is the escalation commitment? |
| USD billing, offshore entity | Currency and jurisdiction risk sits with you | Can you bill in AUD under Australian law? |
| Monthly PDF reporting | Low governance maturity | Can I see a sample live dashboard? |
| IP transfers on final payment | Leverage disappears in a dispute | When exactly does IP transfer? |
| No pilot offered | Low confidence in delivery quality | Will you run 30 to 60 days on real scope? |
| Missing or punitive exit terms | Weak client leverage at every renewal | What does exit cost in practical terms? |
The Meta Red Flag Worth Naming
Underneath all twelve sits a single pattern. The provider answers questions about capability enthusiastically and questions about measurement vaguely.
Capability answers are easy to give and imposible to verify at selection. Measurement answers are harder to give and immediately verifiable. A provider who volunteers their churn rate, shows you their assessment rubric, and produces a live dashboard is telling you they measure their own delivery. A provider who redirects each of those to a story about culture is telling you they do not.
Weight the measurement answers heavily. They are the only part of a sales conversation that carries real information about what month twelve will look like.
Businesses evaluating broader IT outsourcing arrangements should apply the same filter across every function in scope, because a provider strong on measurement in one area is usually strong across the board, and vice versa.
How Upscalix Answers These Questions
We are an Australian registered offshore outsourcing company headquartered at Level 11, 580 Collins Street, Melbourne, with engineering delivery teams in Indonesia. Here are our answers to the twelve questions above, up front.
Our managed nearshore rates sit at AUD 52 to 76 an hour, all inclusive. That covers recruitment, employment, HR administration, tooling, equipment, and delivery management, with nothing itemised separately later. Against fully loaded local costs, that works out to 40 to 70% savings.
Technical evaluation is engineer led, with live coding, test tasks, and English communication assessment. We recruit from the top few percent of Indonesian technical talent, and our teams are mid to senior rather than junior heavy.
Our developer churn on client engagements stays below 2%. Some of our engineers have been embedded with the same client for more than four years.
We will tell you when we think your brief has a problem, including when we think a fixed price is the wrong structure for the scope you have described.
Our developers work Australian business hours from Indonesia, one to three hours from AEST depending on daylight saving. Escalations are handled inside your working day.
We bill in Australian dollars through an Australian entity under Australian contract law. IP transfers to you, and we start new clients with a defined pilot on real scope so both sides can validate fit against agreed criteria.
Whether the engagement is a custom software development build, a dedicated squad, or capacity alongside your existing team, the quote you receive is the number you pay.
If you are mid selection and want a provider to answer all twelve in writing, send us your requirements.
What This Means for Australian Businesses
Outsourcing failures are mostly selection failures, and selection failures are mostly measurement failures. The provider who cannot tell you their churn rate at selection will not be able to tell you why your team velocity dropped in month nine either.
Run the twelve questions. Get the answers in writing. Compare what each provider volunteers against what each one avoids, because the pattern of avoidance is more informative than any individual answer.
And be honest about your own side of it too. Providers with no defined change control fail more often, but so do clients with no product owner, no acceptance criteria, and no documented priorities. The research on governance maturity cuts both ways.
Fair enough?
FAQ
What are the biggest red flags when outsourcing software development?
A rate far below market, recruiter led technical interviews, retention answered with awards rather than churn figures, and no defined change control process are the four that most reliably predict failure.
Why is a very low offshore rate a warning sign?
Below market rates usually mean junior substitution, shared resources, or costs stripped from the rate that reappear later. Supervision overhead then erases the apparent saving.
What should I ask about developer retention?
Ask for developer churn on active client engagements over the last twelve months, plus the longest running engagement with original engineers still in place. Company wide retention figures are not comparable.
Should I insist on a pilot before signing an outsourcing contract?
Yes. A thirty to sixty day pilot on real scope with written success criteria reveals more than any reference call, and reluctance to offer one is itself informative.
Sources
- https://www.deloitte.com/global/en/issues/work/global-outsourcing-survey.html
- https://www.pmi.org/learning/library/scope-creep-rising-11308
- https://www.intertec.io/en/resources/blogs/preventing-scope-creep-software-budget-control
- https://news.designrush.com/project-success-rate-discovery-phase-scope-creep
- https://ia.acs.org.au/article/2026/australia-s-tech-workforce-shrinks-for-first-time.html
- https://www.seek.com.au/career-advice/role/software-engineer/salary
- https://www.ato.gov.au/businesses-and-organisations/super-for-employers/paying-super-contributions/how-much-super-to-pay