Service · Brisbane and Australia-wide

Software Project Rescue

Your developer or agency has gone quiet, moved on or run out of budget. The app is half-built or broken, and nobody can change it or put a fix live. We start with a fixed-price review of your code and systems, then tell you plainly what it will take to get it working.

Signs you need help

This is for Brisbane and Australian businesses whose software project has stalled. An offshore team stopped replying, a freelancer moved on, or the budget ran out before the app was done. Whatever happened, the first job is the same: find out what you have.

  • Your developer or agency has stopped replying, or replies but nothing changes
  • The app is half-built and the budget or contract has run out
  • Something is broken and nobody knows how to fix it
  • Nobody can put changes live, because only the old developer knew how
  • You don't know where the code is, or who owns the hosting and domain
  • You pay monthly bills for servers or services and aren't sure what they do

What we do first: a code and system review

Before anyone changes the code, we find out what is really there.

  1. Get access. You give us access to the code, hosting and related accounts. We help you track down anything missing.
  2. Check it. We see whether the code builds and runs, how it is put live, whether data is backed up, the security basics, and what is unfinished.
  3. Report back. You get a short written report in plain English, with your options and roughly what each would cost.

The report usually points to one of three options.

1. Fix and finish

Best when the code is in fair shape and most of the work is done.

We fix what's broken, finish what's missing and set up a safe way to put changes live.

2. Stabilise and hand back

Best when you have someone to run it, such as your IT person or a new developer.

We fix the urgent problems, move the code and accounts into your name, and write down how to run and update it, so your people can take it from there.

3. Rebuild parts

Best when some parts are too fragile or insecure to keep.

We keep what works and rebuild only the parts that need it, one at a time, so the app keeps running while we work.

Sometimes the honest answer is to rebuild. Sometimes it is to keep going with what's there. We'll tell you which, and why. A bigger rebuild is quoted like any custom software project. If the system is old as well as unfinished, see legacy system modernisation.

What it costs

The first 30-minute chat is free. The review is a fixed price we agree with you before we start. If the job is hard to size upfront, we charge $150/hr instead, with a cap agreed before we start, so the bill can't run past it.

Fixing or finishing work gets a fixed quote once the review is done. You see the price before any of that work starts.

Getting your code and accounts back

Before you contact the old developer, list what you need. Each of these should ideally be in your business's name, with developers added as users.

  • Domain name: who the registered owner is, and which company it is registered with
  • Hosting account: the web host or cloud account, such as Azure or AWS, that the app runs on
  • Code repository: the GitHub, Bitbucket or similar account that holds the code and its history
  • App store accounts: your Apple App Store and Google Play developer accounts, if you have a mobile app
  • Database backups: where they are kept, how often they run, and a recent copy
  • Third-party services and API keys: payments, email, maps, SMS and any other service the app uses

Send the old developer a short written request listing each item. Ask for ownership to be moved to your business, not just a shared password. For the code, ask for the full repository with its history, not a zip file. Keep it polite and specific. If you can't reach them, we can help you work through each provider's account recovery steps.

For your IT person

We start with a repository audit: build steps, dependencies and anything with known security issues, then dependency and security updates. Before changing risky parts, we add tests around them so we know if something breaks. Then we set up CI/CD so deployments are repeatable, move infrastructure into code where it helps, and add logging so problems show up early. We're comfortable with .NET, Next.js and React, React Native, SQL Server and PostgreSQL, on Azure or AWS. If it's a stack we don't know well, we'll say so.

Who you will work with

Hireadev is run by Ryan Brooker, a Brisbane software engineer. You deal with the person reading and fixing the code, not an account manager. We can meet in person in South East Queensland and work remotely with businesses across Australia.

Software project rescue FAQ

Yes. That is what this service is for. We read the code first, then tell you in plain English what we found and what it will take to change it.
Ask the old developer first, and check your contract for who owns the code. Some code can be recovered from the hosting account, but it is often incomplete. A mobile app downloaded from the store is not the source code. If the code can't be recovered, the working app still shows us what needs to be rebuilt.
Yes. Where the code was written matters less than what it was written in. If it uses a language or framework we don't know well, we'll tell you early.
No. A rebuild costs more and takes longer, so we only suggest it when the existing code can't be fixed safely or would cost more to keep. If keeping what's there is the better option, we'll say so. The report explains why.
It depends on what we already have booked. We'll tell you on the first call.
Whatever access you have to the code, hosting and domain, plus any contract, quotes or notes from the old developer. Please add us as a user rather than sending passwords. We're happy to sign an NDA first.

Related

Tell us where your project is up to

Book a free 30-minute chat. Tell us what was built, who built it and what access you have. We'll explain the next step and what the review would cost. No obligation.