Executive Summary
Most offshore selection conversations cover capability, portfolio, and price. Those three things are the easiest to present well and the hardest to verify before you commit.
The questions that actually predict how month twelve will look are less comfortable, which is exactly why they get skipped. Churn figures. Screening rubrics. Escalation commitments in hours. Exit costs.
The stakes justify the awkwardness. Standish Group’s CHAOS research consistently finds only around 31% of software projects finish on time, on budget, and within scope, while PMI reports that organisations with mature governance complete roughly 89% of projects on time and on budget against 36% for low maturity organisations.
If you are about to engage a dedicated offshore developer or a small squad, these are the ten questions to send in writing before any contract goes near a signature, along with what a strong answer sounds like.
Key Findings
- Delivery baseline: Only around 31% of software projects finish on time, on budget, and within scope according to Standish Group CHAOS research
- Governance premium: PMI reports mature governance organisations complete approximately 89% of projects on time and on budget, against 36% for low maturity
- Turnover benchmark: Annual attrition at typical offshore delivery centres runs 20 to 30%, making churn the single most predictive metric
- Hiring speed: Engineering roles take around 62 days to fill globally against 42 days across all occupations
- Scope creep: Roughly 52% of projects experience scope creep, with an average cost overrun near 27% per PMI data
- Currency exposure: Over twelve months, a five cent AUD/USD move shifts actual spend by roughly 7%
- Local context: Australia’s tech workforce shrank 0.3% in 2025 to around 967,000 workers per ACS Digital Pulse 2026
1. What Is Your Developer Churn Rate on Client Engagements?
Start here, because this is the question that predicts everything downstream.
Note the precise wording. Not company wide retention, which includes administrative staff who churn far less than engineers. Not employee recommendation scores, which measure sentiment rather than tenure. Not workplace awards. Developer churn, on active client engagements, over the last twelve months.
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 you a replacement search, a ramp up period, and accumulated codebase context that no handover document reproduces.
A strong answer is a specific figure, ideally under 5%, backed by a named long running engagement where the original engineers are still in place. A weak answer redirects to culture.
Follow up with this. What is your defined replacement window when someone resigns, and is the replacement’s ramp up period billable?
2. Who Conducts the Technical Interview, and What Is Their Engineering Background?
Ask this early, because the answer tells you what you are actually buying.
If technical evaluation is run by a talent acquisition specialist working from a competency checklist, the provider is filtering for interview performance rather than engineering capability. If it is run by a working engineer with relevant stack experience, they are filtering for the thing you care about.
Then ask to see the assessment itself. Not a description of the process, the artefact. The live coding exercise, the take home task, the evaluation rubric. A provider serious about screening will show you all three without hesitation.
Ask about English communication assessment separately, because providers who take it seriously assess it separately. Written technical communication in tickets and pull requests matters as much as spoken fluency in standups.
Any credible offshore software development company will have a documented, engineer led process. The absence of one is not a small gap.
3. Which Specific Engineers Will Be Assigned, and Can I Interview Them?
Named engineers with specific CVs and confirmed availability is the standard. Anything vaguer means the team gets assembled after you sign, from whoever happens to be free.
Watch particularly for the pattern where senior engineers attend the pre sales technical discussions and a more junior team delivers the work, with senior oversight promised in the background. Oversight is not delivery, and the difference shows up in your code review queue.
Interviewing your engineers before commitment should be non negotiable for a dedicated engagement. You would not hire locally without meeting the person.
Ask for the team composition in writing, including seniority level, years of relevant stack experience, and current allocation percentage. If someone is 50% allocated elsewhere, you need to know that now rather than in sprint three.
4. What Exactly Is Included in the Rate?
Get this itemised, in writing, covering a full twelve month engagement.
The list to run through: recruitment, employment costs, HR administration, payroll, hardware, software licences, workspace, delivery management, onboarding, and replacement recruitment. All inclusive and all inclusive with conditions are very different propositions.
Then ask what will be billed separately over twelve months. This is where surprise costs live. A rate that looks 15% cheaper stops being cheaper once tooling licences and management fees arrive as separate line items in month three.
Ask the productive hours question too, because it changes the annual number materially. A rate quoted against 2,080 hours and the same rate quoted against 1,820 hours produce annual costs that differ by around 12%. Most offshore engagements realistically deliver around 1,820 billable hours after local public holidays and leave.
Any outsourcing provider confident in their pricing will give you a single all inclusive figure and stand behind it.
5. Which Country Will My Engineers Sit In, and What Hours Do They Work in AEST?
Two separate questions bundled together, and both matter.
For multi country providers, the country your particular engineers sit in matters far more than the countries the company operates in. Indonesia, Vietnam, and the Philippines all sit within a few hours of Australian business hours. India is workable with structure. Eastern Europe and Latin America require asynchronous discipline that most Australian SMEs have not built.
The working schedule question is the one people forget. A provider located three hours away that runs its own shift pattern may deliver less practical overlap than the geography suggests.
Then get the escalation path documented rather than described. What happens to an issue raised at 2pm AEST? What is the response commitment in hours? Who specifically is the escalation contact?
Description is easy. Documentation is what you can hold someone to.
6. How Does a Change Request Get Raised, Priced, Approved, and Scheduled?
This is the question that prevents the most expensive category of dispute, and it almost never comes up in sales conversations.
The research is fairly direct on this. Projects with no formal change control process are roughly twice as likely to fail as those with one in place, and around 52% of projects experience scope creep with an average cost overrun near 27%.
Under a fixed price arrangement, ask for the variation pricing basis and the turnaround commitment. Under a time and material arrangement, ask about the monthly spend cap and what approval is required to exceed it. Under a dedicated team arrangement, confirm that changes are handled in sprint planning without formal variation, which is one of the model’s real advantages.
If the answer is that changes get discussed as they come up, you have found the clause that will cost you money in month six.
7. What Reporting Will I Receive, and How Often?
Live dashboards showing sprint velocity, defect rates, code review turnaround, and hours consumed against forecast are the 2026 standard. Ask to see a sample from a live engagement, with client details redacted.
A monthly summary PDF is a generation behind, and it tells you something about governance maturity more broadly. Given the gap PMI reports between mature and low maturity governance organisations, reporting cadence is a reasonable proxy for how the engagement will actually run.
Ask who the named delivery lead is and what their engineering background is. Ask what cadence of client facing meetings is included in the rate, because some providers charge separately for anything beyond a monthly check in.
If you have to email someone to find out how the work is progressing, you are the reporting system.
8. What Currency Is the Invoice, and Which Country’s Law Governs the Contract?
This looks administrative and is actually commercial
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 price difference between two shortlisted providers, which means currency movement can retrospectively invert your decision.
The legal question is the more serious one. An Australian entity under Australian contract law, with disputes resolved locally, is a meaningfully different risk position to an offshore entity in a jurisdiction you have never dealt with.
Ask three things. Can you invoice in Australian dollars? Is there an Australian registered entity contracting with us? And where would a dispute be resolved?
9. When Does Intellectual Property Transfer, and How Is Our Data Handled?
Read the IP clause and pay attention to the timing.
Some contracts transfer code, documentation, and designs only on final payment. That is defensible from the vendor’s side and uncomfortable from yours, because your leverage disappears at exactly the moment a dispute arises.
Three specific asks. When does IP transfer occur, and does it cover code, documentation, designs, and infrastructure configuration? Is there a data processing agreement covering how our data is handled, where it is stored, and who can access it? And what access controls apply to production systems and customer records?
For Australian businesses subject to Privacy Act obligations, this is not boilerplate. Any engagement where developers touch customer data needs specific answers, particularly if you plan to outsource IT services beyond development alone.
10. Will You Run a Pilot, and What Does Exit Look Like?
Two bookend questions, and both reveal confidence.
On the pilot: will you run thirty to sixty days on real scope, with success criteria agreed in writing beforehand? Insist on genuine work rather than a toy exercise, and include a deliberate mid pilot priority change, because how a team handles change is more informative than a clean run.
On exit: what is the notice period, what handover deliverables are included, is handover billable, and are there penalties beyond the notice period?
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, and without reasonable terms you negotiate from a weak position at every rate review.
The Ten Questions at a Glance
| No | Question | Strong Answer | Warning Answer |
|---|---|---|---|
| 1 | Developer churn on client engagements? | Specific figure under 5%, named long engagements | Awards, sentiment scores, company wide retention |
| 2 | Who runs technical interviews? | Working engineer, rubric and live coding shown | Recruiter with a competency checklist |
| 3 | Which named engineers, can I interview them? | Named CVs, allocation %, interviews welcomed | General capability description, team assigned later |
| 4 | What is included in the rate? | Single all inclusive figure, itemised in writing | Base rate plus extras clarified later |
| 5 | Which country, what AEST hours? | Named country, Australian hours, documented escalation | Company wide location list, described overlap |
| 6 | How does change control work? | Defined process with turnaround commitment | Changes discussed as they arise |
| 7 | What reporting, how often? | Live dashboards, named delivery lead | Monthly PDF summary |
| 8 | Currency and governing law? | AUD billing, Australian entity, local jurisdiction | USD billing, offshore entity, foreign law |
| 9 | When does IP transfer? | On creation, with DPA and access controls | On final payment, vague data terms |
| 10 | Pilot and exit terms? | 30 to 60 day pilot, defined exit and handover | Long minimum commitment, punitive exit |
Send all ten in one email and compare the responses side by side. What each provider volunteers, and what each one avoids, carries more information than any individual answer.
A Note on Sequencing These Questions
Order matters more than people expect, because the early answers determine whether the rest are worth asking.
Send questions one, two, and three first. Churn, screening, and named engineers. If those three come back weak, the remaining seven are irrelevant and you have saved yourself two weeks.
Questions four through eight are commercial and can be negotiated. Rate inclusions, timezone commitments, change control, reporting, and currency are all things a willing provider will adjust. Weak answers here are a starting position rather than a disqualification.
Questions nine and ten are contractual and should be settled before any commitment, because they determine your position if things go wrong. IP timing and exit terms are much harder to renegotiate after signature than before.
Send all ten in a single written request regardless, and note how long each provider takes to respond. Response time on a written due diligence request is a reasonable early proxy for responsiveness during delivery. Businesses evaluating broader IT outsourcing arrangements across several functions should run the same sequence per function rather than once at company level.
Three Questions About Your Own Readiness
Fair is fair. Providers fail more often when clients are not set up either, and the governance research cuts both ways.
Do you have a product owner? Someone on your side who owns the backlog, sets priorities, and accepts work. Dedicated team engagements punish absentee clients harder than any other model, because you are paying full rate for capacity you are not directing.
Do you have documented acceptance criteria? Vauge definitions of done favour whichever party has more patience for argument, and that is rarely the client with a launch date.
Do you have an onboarding plan? Repository access, environment setup, architecture walkthrough, and a first ticket ready on day one. Engineers waiting two weeks for credentials are billable and idle, and it sets a tone that is hard to reverse.
If you are hiring a React developer or a Python developer into an existing codebase, the onboarding quality on your side determines the first month’s output more than the engineer’s capability does.
How Upscalix Answers All Ten
We are an Australian registered offshore outsourcing company headquartered at Level 11, 580 Collins Street, Melbourne, with engineering delivery teams in Indonesia. Our answers, up front.
Developer churn on client engagements stays below 2%. Some of our engineers have been embedded with the same client for more than four years.
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.
We name your engineers before you commit, and we expect you to interview them.
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.
Our developers sit in Indonesia and work Australian business hours, one to three hours from AEST depending on daylight saving. Escalations are handled inside your working day.
Under a dedicated team engagement, changes are handled in sprint planning rather than through variation orders.
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 against agreed criteria.
Whether the engagement is a custom software development build, a dedicated squad, or additional capacity alongside your existing team, the quote you receive is the number you pay.
If you have a shortlist and want these ten answered in writing, send us the requirements.
What This Means for Australian Businesses
The value of these questions is not that they identify the best provider. It is that they identify which providers measure their own delivery.
A provider who volunteers a churn figure, shows you an assessment rubric, and produces a live dashboard is telling you they instrument their own work. That is a far better predictor of month twelve than a portfolio or a reference call, both of which are curated by definition.
Australia’s tech workforce contracted last year for the first time on record, which means more Australian businesses will be running exactly this selection process over the next few years. The ones who get value from it will be the ones who asked the uncomfortable questions before signing rather than after.
Fair enough?
FAQ
What questions should I ask before hiring an offshore developer?
Start with developer churn on client engagements, who conducts technical interviews, which named engineers will be assigned, exactly what the rate includes, and what the escalation commitment is in hours.
What is the single most important question to ask an offshore provider?
Developer churn on active client engagements over the last twelve months, because high turnover destroys the accumulated codebase context that makes offshore engagements pay off.
Should I interview offshore developers before they join my team?
Yes. Named engineers with confirmed availability is the standard for dedicated engagements, and reluctance to allow interviews usually means the team is assembled after signature.
How do I check whether an offshore rate is genuinely all inclusive?
Ask for an itemised list covering recruitment, employment, HR, tooling, licences, and delivery management, plus a written statement of what will be billed separately over twelve months.
Sources
- https://www.pmi.org/learning/library/scope-creep-rising-11308
- https://www.deloitte.com/global/en/issues/work/global-outsourcing-survey.html
- https://ia.acs.org.au/article/2026/australia-s-tech-workforce-shrinks-for-first-time.html
- https://www.intertec.io/en/resources/blogs/preventing-scope-creep-software-budget-control
- 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
- https://news.designrush.com/project-success-rate-discovery-phase-scope-creep