Assay Ready runs the buyer's diligence engine against your own codebase — months before the process starts. You get a remediation punch-list instead of a deal recommendation, so findings get fixed on your timeline instead of priced into their offer.
What a buyer reads into it: the business is one resignation away from a maintenance cliff, and prices retention risk into the offer.
How to close it: pair-review the single-owned files and land real commits from a second engineer. Evidence that someone else already ships in those files is what moves the number.
In diligence, a finding surfaces at the worst possible moment: after the LOI, when the buyer has leverage and you have a closing timeline. The same finding, closed six months earlier, is just an engineering ticket. Assay Ready moves the discovery to the side of the table where it's cheap.
This is not a friendlier scan. It's the identical analyzer battery a buyer runs, with the identical thresholds — because a report that flatters you is worthless the moment their engine disagrees with it.
The punch-list is sequenced by what a finding costs you in a negotiation, not by how hard it is to fix. Each item names what a buyer reads into it and the shape of closing it.
Zero dependencies, zero network calls. The engine runs on your machine, under your control, before you've decided to trust anyone with the repository.
Your prose is scanned for AI claims, then your code is checked for the model integration that would make them true — including whether it's reachable from your product's entry points. If your marketing has drifted ahead of your code, you want to be the one who finds out.
Truck factor and single-owned critical files, computed from your commit history. Buyers price this at a 0.5–1.5x multiple reduction — and it's the finding with the longest lead time to fix.
Copyleft obligations that attach to proprietary code. Counsel resolving this on your schedule is an engineering decision; counsel resolving it in a data room is a deal issue.
Credentials committed to your repository, redacted in the report. Rotate them now and you can show a buyer the rotation dates — that's a different conversation from deleting the line.
Plus code-quality signals: whether tests and CI exist, and which files are simultaneously high-churn and single-owned — the maintenance cliff a buyer's engineering lead will find on day one.
Run the engine against your codebase — on your hardware if you prefer. You get the punch-list, ordered by what it costs you, with the evidence a buyer would see.
Work the list on your own timeline. Most items are engineering tickets when they're not deal terms — knowledge transfer, credential rotation, a licence decision, copy that matches the code.
Run it again and get a delta: what changed, what's gone, what's new. Walk into diligence knowing what their screen will say.
What this is not: Assay Ready doesn't price your business, and closing every item guarantees no valuation outcome. It doesn't replace counsel on licence or disclosure questions. It reports what a static pass over your repository can establish — and says plainly what it did not assess.
Tell us where you are in the process. If a readiness screen isn't the right instrument yet, we'll say so.
Book a readiness screen