Services
Four ways in. Each is scoped and priced so the first cheque buys you an answer rather than a hopeful start, and each one ends with something written down.
Something is broken right now and nobody knows why
A production system is down, degraded, or behaving in a way your team can't explain. We take the repository, the logs and the infrastructure, reproduce the failure, and tell you what is actually wrong.
What's includedYou inherited a system and need to know what you're holding
A full read of a codebase you didn't write, ending in a written report: architecture, risk, technical debt, the unknowns, and a ranked plan. The product to buy before you commit money to a system you don't understand.
What's includedThe build is late, over budget, and technically stuck
A project that should have shipped months ago and hasn't. We assess it, stabilise it, and drive it to something you can actually put in front of a customer — working with the team you already have.
What's includedSenior engineering behind your team, on retainer
A standing retainer for agencies and small product teams. Architecture review, escalation, code review, and someone senior to call before a difficult decision becomes an expensive one.
What's includedBefore you buy one
A full worked example of the Codebase Autopsy deliverable is published here — executive summary, risk register, unknowns, and a ranked plan with effort against it. The system in it is synthetic, the findings are the ones that recur. It is the fastest way to know whether this is worth $4,000 to you.
Read the sample reportHow the money works
Nothing gets quoted as a fix until it has been diagnosed. If an assessment turns into a repair engagement, its fee comes off the first invoice — so getting the diagnosis first costs you nothing extra, and getting it wrong costs you a great deal.
Assessments and reports are flat. An hourly rate on a diagnosis is an incentive to take longer, and you should be able to say yes to one without a procurement cycle.
Some systems are not worth rescuing, and some problems are cheaper for your own team to fix once someone has pointed at them. You will be told that. It is a bad way to maximise an invoice and a good way to be worth calling twice.
Then describe the situation and let us pick. Most enquiries arrive as a paragraph of frustration rather than a service name, which is completely fine — sorting that into the right engagement is part of the job, and it happens before you are asked for money.
Describe what is broken, what you inherited, or what has stopped moving. You'll get a straight read on whether Salvage is the right call.
First reply usually within a few business days, from a person