Your AI code works on your machine. We make it work everywhere.
We read the whole codebase, find what's actually broken, and fix it without rewriting your product.
A repo that mostly works. Bugs you can reproduce, and bugs you can't. Code you didn't write and don't fully understand.
A working build, a plain-English list of what was wrong, and commits you can actually read.
What's actually included.
A full read of the codebase, not just the file that's throwing.
Every reproducible bug fixed, with the reproduction written down.
Dead code, unused packages, and hallucinated dependencies removed.
A refactor of the parts that will bite you in three months.
What we work with.
We read whatever it is written in. If it is not on this list, send it anyway and we will tell you quickly whether we can help.
Fair things to ask.
Will you rewrite everything?
No. Rewrites are how projects die. We fix what's broken and leave what works.
What if the code is really bad?
We've seen worse. And if a rewrite is genuinely cheaper than a repair, we'll say so instead of billing you for the repair.
Do I need to explain the code?
No. We read it ourselves. That's the job. It helps to know what the product is supposed to do, but you don't need to walk us through the files.
What do you need to start?
Repo access, a way to run it, and a note on the bugs you already know about. If there's no README, you'll have one by the end.
It has no tests at all. Is that a problem?
It's normal. We fix against reproductions we write ourselves, and those reproductions stay behind as your first tests.
Can you work in our repo, on our branches?
Yes, and we prefer it. You see every commit as it lands rather than getting a zip at the end.
What if you find something that isn't a bug, like a security hole?
You hear about it the same day. Whether we fix it is a separate conversation if it's outside what you asked for.
Will you update our dependencies?
Only where they're the cause. We'll flag anything abandoned or unpinned, but an unrequested version bump is how a working build breaks.
What if we disagree about a fix?
It's your codebase. We'll tell you what we'd do and why, then do it your way if you still want that.
What do we have at the end?
A working build, a plain-English list of what was wrong, and commits your own engineers can read.