About
A small shop for other people's disasters
Salvage Software exists because the hardest work in this industry is not writing new software. It is walking into a system somebody else built, under pressure, and working out what is actually true about it.
Who you'd be working with
Salvage is run by Austin Adamson, a senior software engineer based in Phoenix, Arizona. The work here is the work he has spent a career doing: inheriting systems, finding out what they really do, and getting them back under control.
That background is the entire proposition. Salvage is not a twenty-two-year-old freelancer who knows a framework. It is someone who has been the senior engineer on the other side of these conversations — who has been handed the repository nobody wanted, has watched a confident rewrite go badly, and knows what happens when you start changing a system you do not understand yet.
It is deliberately small. There is no bench, no account manager, and no incentive to turn a two-week problem into a six-month engagement. When capacity is full you get told that, immediately.
How the work runs
Six things you can hold us to
Assessment before opinion
No recommendation is worth anything before the system has been read. That includes the popular ones — rewrite it, move it to the cloud, replace the framework. Findings come from evidence or they do not come.
It gets written down
Every engagement ends in a document, not a verbal summary on a call nobody recorded. You should be able to hand it to a developer who has never met us, or to a board that needs a reason.
Boring where it counts
A rescue is not the place to introduce an interesting technology. The goal is a system your team can still run in two years, using tools they can hire for.
Say no out loud
Some systems are not worth saving, some problems are cheaper for your own team to fix, and some engagements are a bad fit. Saying so costs an invoice and earns the next three.
We propose, you merge
Salvage does not merge code into your repository. Changes arrive as pull requests with the reasoning attached and your engineer approves them — so no part of your system ends up understood only by us. Nobody gets replaced, and nobody is made to look stupid for inheriting a mess they did not create.
The scope is the scope
Fixed fees where the work is fixed, written scope where it is not, and no discovery of extra billable urgency halfway through.
Not on the menu
What Salvage doesn't do
A rescue practice that also sells everything else is just an agency with better marketing. Keeping this list short is what makes the rest credible.
- Greenfield builds. If nothing exists yet, you want a development shop, and there are good ones.
- Design and marketing sites. Not the skill being sold here.
- Ongoing feature development. Salvage stabilises and hands back. Long-term feature work belongs with your own team or your agency.
- 24/7 on-call. A small shop promising round-the-clock response is a small shop that will eventually miss the call.
- Taking your client. Agency work is white-label, and non-solicitation goes in writing on request.
- Merging our own code. Changes are proposed, reviewed by your team, and merged by your team. There is a logged break-glass path for outages and nothing else.
The umbrella
Part of Rogue Wolf
Salvage Software is one of the things built under Rogue Wolf LLC, alongside FiveFour Games and the rest. Different work, one standard — and one reason the sites look like siblings.
Visit Rogue WolfWorth a conversation?
The first one is free and often ends with a suggestion you can act on without hiring anybody. That is not a loss leader — it is how this practice gets called back.
First reply usually within a few business days, from a person