Start a salvage
Tell us what broke
No form, no discovery call funnel, no gated PDF. An email describing the situation is enough — and if the honest answer is that you don't need to hire anybody, that's the answer you'll get.
What to put in it
None of this is required. Send what you have — a repository link and one furious paragraph is a perfectly normal first contact.
-
What is happening
The symptom in plain language. "Checkout times out for about one order in twenty, started last Tuesday" beats "we have performance issues".
-
What it runs on
Language, framework, database, where it is hosted — as much as you know. "Nobody here knows" is a real and common answer, and it changes nothing about whether we can help.
-
What has been tried
Including the things that did not work. Ruling out four theories before the first call is worth real money.
-
The pressure you are under
A launch date, a board meeting, an angry customer, a contract clause. Urgency changes the shape of the right answer, not just the speed.
-
What access exists
Repository, hosting, logs, someone who remembers how it was built. If the honest answer is "we are not sure what we have", say that — establishing it is part of the work.
- austin@salvage.software
- Time zone
- MST (UTC−7, no DST)
- Based in
- Phoenix, Arizona
- Working with
- Agencies, MSPs, and small product teams — remote, anywhere
- Confidentiality
- NDA before access on request, and standard on agency work