Answer eight quick questions about software you no longer run and this tool gives an instant verdict, Strong fit, Worth a look or Not a fit today, with the reasons behind it. It runs entirely in your browser, stores nothing and takes about two minutes.
The check above gives a quick first read on whether code from a product you no longer run matches what Odys AI Labs buys. It is not a valuation and it never asks for your code: it only weighs the answers you give against the same checks set out in how we evaluate a codebase. Here is what each question means, how the verdict is worked out and what to do with it.
What does each question ask?
- Product name or old website. Only so the verdict has a label. It is not looked up or sent anywhere.
- What it was. A web app or SaaS, a mobile app, a platform or marketplace, a game, a backend or API, an internal tool or other software. Every type qualifies; this only describes it.
- Status today. Shut down, abandoned or never launched, online but earning nothing, or still making money. The first three are exactly what we look for.
- Size of the codebase. A bucket of lines of code: under 10,000, 10,000 to 50,000, 50,000 to 250,000, 250,000 or more, or not sure. Free counters such as cloc give the number by language. The guide on how to count lines of code explains what to leave out.
- Who wrote most of it. Your team, about half your team and half libraries or templates, or mostly a template, fork or copied libraries. We buy original code.
- Git history. Full history, only the latest code, or not sure. Git history adds value; code without it is still sellable.
- Docs and tests. Both, one of them, or neither. They add to value and are never required.
- Who owns the rights. You, a company you can sign for, not sure (co-founders or contractors), or client work.
How is the verdict worked out?
Each answer lands in one of three groups. Some are strengths, such as full history or code your team wrote. Some are notes that never count against you, such as only the latest code, no docs or tests, or not knowing the size. A few are shortfalls.
There are two kinds of shortfall. A soft shortfall is a point that often can be fixed or explained: rights you are not sure about, or a codebase under 10,000 lines. A hard no is an answer that rules the code out on its own:
- the software is still making money;
- it was client work;
- it is mostly a template, a fork or copied libraries.
No shortfalls gives Strong fit. One soft shortfall gives Worth a look. Two soft shortfalls, or any hard no, gives Not a fit today.
What does each verdict mean?
| Verdict | What it means | What to do |
|---|---|---|
| Strong fit | No longer earning, mostly your team’s code, rights you can sign for, a reasonable size | Send the details for a free valuation |
| Worth a look | One point needs a closer look, usually rights or size | Send the details; we will say plainly whether it can be resolved |
| Not a fit today | A hard no, or two points that fall short | Read the reasons and see your other options |
The reasons listed under your verdict matter more than the label. A product that is Worth a look only because a contractor never signed an IP assignment is in a different position from one that is small and has unclear rights at the same time.
Why are some answers a hard no?
Still making money. We only buy code of software that no longer earns. A running, profitable product is usually worth more sold as a business, priced on its revenue or profit, through a marketplace such as Acquire.com or Flippa, or through a broker. That is where it belongs.
Client work. Code you built for a client usually belongs to the client under your contract, and we can only buy code whose rights you hold. Your agency’s own products and internal tools are a different matter. The guide on who owns the code explains the difference; it is general information, not legal advice.
Mostly a template or copied code. Open-source libraries inside a product are normal and do not stop a sale. But when most of a repository is a template, a fork, a tutorial project or copied libraries, there is little original work in it, and original work is what we buy.
What can the check not tell you?
It cannot tell you what the code is worth. Value depends on size, originality, languages, quality, history, docs and tests, the offer is made after review, and how we value a codebase is explained on the call. The check also takes your answers at face value. If you are unsure about rights, the honest answer is Not sure, and that is often the most useful thing to discuss on a call.
It also does not look at sensitive data. Many old codebases hold secrets, such as API keys in an environment file, or test data with real names in it. That is never a reason for a no: secrets, keys and personal data are removed before transfer, and we help.
What happens to the data I enter?
Nothing. The check runs entirely in your browser and makes no external calls. Your answers are not stored, sent or shared, and they disappear when you close the page. It never asks for code, and no fair buyer needs your code before a signed agreement.
What to do next
- If you got Strong fit or Worth a look, send us a few details for a free code valuation and we will review it properly.
- If you got Not a fit today, read your options for code you no longer use before you decide anything.
- Whatever the result, do not delete the original repository: keep it, history included, so every option stays open.
Frequently asked questions
Is the code value check really free and private?
Yes. The check runs entirely in your browser. Nothing you type is sent to us or to anyone else, nothing is saved, and there is no account or email required. It never asks for your code. If you want us to look at the product, you send the details separately through the short form on the homepage, and only then do we see them.
Does a Strong fit verdict mean you will make me an offer?
No. It means the answers you gave match what Odys AI Labs looks for, which makes an offer likely to be worth discussing. We still review the product based on what you tell us on a short call, and the offer comes after that review. Payment is cash only, one agreed price, paid on transfer, and there is no obligation to accept.
My result says Worth a look. Should I still contact you?
Usually, yes. Worth a look means one point needs attention, most often rights that depend on a co-founder or contractor, or a codebase on the small side. Those are often easy to sort out. Send the details through the homepage form and we will tell you plainly whether the point can be resolved and what it would take.
Why does the check say no if my software still makes money?
Because we only buy code of software people no longer use for income. A product that still earns is a running business, and it is usually worth more sold as a business, priced on its revenue or profit, through a marketplace or a broker. If it stops earning later, the code may then be a fit.
I do not know how many lines of code my product has. What should I pick?
Pick Not sure. It does not count against you. If you want a number, free counters such as cloc or tokei report lines by language, and you run them yourself on your own machine. Count only code your team wrote, and leave out copied libraries, generated files and minified files, since those are not what a review of original code looks at.
Find out what your old code is worth right now.
Tell us about the product in about a minute. No code needed. We review the details and come back with a cash offer or a plain no.
Get my free code valuation →