Assay Ready runs the engine a buyer would run against your own codebase, months before a sale process starts. It finds what their diligence would find, like the one engineer who holds the system or a credential sitting in the git history. You get a punch-list of what to fix, ordered by what each item would cost you. Each finding gets closed on your schedule 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 moment: after the LOI, when the buyer holds the cards and you have a closing date. The same finding, closed six months earlier, is an engineering ticket. Assay Ready moves the discovery to your side of the table, where it's cheap.
You get the analyzers and thresholds a buyer runs, unchanged. A report that flattered you would be worthless the moment their engine disagreed with it.
The punch-list puts first the findings that would cost you most at the table, however easy or hard they are to fix. Each item names what a buyer reads into it and how to close it.
Nothing to install and no network calls. The engine runs on your machine, under your control, before you've decided to trust anyone with the repository.
Assay finds the AI claims in your README, docs and copy, then checks your code for the model integration that would make them true, and whether your product's entry points ever reach it. If your marketing has drifted ahead of your code, you want to be the one who finds out.
Your truck factor and the critical files only one person has changed, read from your commit history. Buyers price this at a 0.5–1.5x multiple reduction, and it takes longer to fix than anything else on the list.
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, which makes a better conversation than a deleted line.
Plus code-quality signals: whether tests and CI exist, and which files change constantly while one person writes nearly all of them. That is the maintenance cliff a buyer's engineering lead finds on day one.
Run the engine against your codebase, on your own hardware if you prefer. You get the punch-list, ordered by what each item would cost you, with the evidence a buyer would see.
Work the list on your own timeline. Before a buyer is in the room, most items are engineering tickets: 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.
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 names 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