Is My Side Project Sellable Yet? The Pre-Listing Diagnostic

Before you ask what your side project is worth, ask whether it's sellable at all. Five tests that give you a straight answer.

You're standing in the kitchen at half past eleven at night, deciding whether to sell the thing you built. The trigger is usually one of three: you're tired of it, something newer has your attention, or a bill landed that the project could quietly clear. So you open a tab, type "what's my side project worth," and start reading about revenue multiples.

Wrong question. Or rather, right question, wrong order.

Whether you want to sell is an emotional, situational thing – only you can answer it, and it changes with your mood, your bank balance, and how the last support ticket went. Whether you can sell is structural. It has a real answer, and you can diagnose it tonight, in about twenty minutes, without a valuation calculator and without telling anyone you're thinking about it.

This piece is the diagnostic for the second question. Run it before you spend a single hour worrying about price.

The question behind the question

Most builders conflate two things that have nothing to do with each other. "Is this worth selling?" gets answered as a numbers problem when most of the time it's a readiness problem. Sellable and valuable are different axes: valuable is about the size of the prize – revenue, growth, defensibility – while sellable is about whether you can hand that prize to someone else without it falling apart in transit. A project can score high on one and zero on the other. Plenty of profitable side projects are, in their current state, completely untransferable. They're not assets. They're jobs with good margins – which is the whole reason being listed and being sellable are not the same thing.

The good news is that "sellable" is fixable in a way that "valuable" often isn't. You can't conjure another year of growth by Friday. You can usually make a project listable inside a month. But first you need to know where you stand, which is what the next five questions are for.

The five-test diagnostic

Answer each one yes or no. Be honest – nobody's watching, and a generous "sort of" only costs you later when a buyer's accountant finds the gap.

1. Can you describe the asset in two sentences, without checking your notes?

Not the pitch. The plain description. What it is, who pays for it, and why. If you can say "it's a newsletter for freelance illustrators, 4,000 subscribers, makes money from a job board and two recurring sponsors" without opening a doc, you pass. If you find yourself saying "well, it started as X but really it's more of a Y, and the revenue is sort of..." then the asset doesn't have a clean shape yet. A buyer needs to understand what they're acquiring in the time it takes to read a listing. If you can't compress it, you can't sell it.

2. Is there a single owner of record for every external dependency?

Domain, hosting, code repository, email service provider, analytics, payment processor. Every one of those is an account, and every account belongs to someone. Walk the list. If the domain is on an old registrar login you share with a co-founder who drifted off two years ago, that's a no. If the Stripe account is tied to a personal bank account you can't transfer, that's a no – and worth checking early, because even payment processors have specific account migration paths that take planning rather than a single click. Transfer day is the moment all of this gets handed over. If you don't know who holds each key, you're not ready to give them away.

3. Could someone else keep it running for four weeks without it breaking?

This is the one that matters most, so sit with it. Imagine you vanish for a month – no laptop, no phone, no "quick fix from the beach." Does the project keep serving customers, sending invoices, publishing, and collecting money? Or does it quietly seize up because every issue, every reply, every deploy runs through you?

If it survives four weeks of your absence, it's an asset. If it doesn't, it's a job that happens to have a logo. Buyers are acquiring something they can operate. They are not acquiring you.

4. Do you have three months of clean revenue records you'd be willing to show a buyer?

Clean means a buyer can see the money move and trust the numbers. A Stripe dashboard, a simple profit-and-loss, bank statements that match the revenue you're claiming. Three months is the floor; twelve is better. If your "records" are a feeling and a rough sense that it does "about two grand a month," you don't have records, you have vibes. Vibes don't survive due diligence.

5. Is the asset legally yours to sell?

No unresolved IP. No co-founder who could surface mid-deal claiming half. No freelance contract that quietly assigned ownership of the code to the agency that built it. No platform terms of service that forbid the transfer outright – some integrations and a number of app-store arrangements are explicitly non-transferable, and you want to find that out now, not in escrow. If there's any tangle here, it's a lawyer's question before it's a listing.

What each "no" actually tells you

The diagnostic earns its keep on the failures. A pass is reassuring; a fail is a map. Here's what each one points at.

A no on test 1 is the cheapest to fix. The asset lives in your head and needs to come out of it. A documentation pass – what it is, how it works, where the money comes from – usually closes this in a day or two.

A no on test 2 is an ownership-cleanup sprint. Consolidate every dependency under one account you control, document the login trail, sort the registrar mess. Tedious, not hard.

A no on test 3 is the expensive one, because it usually means the asset isn't an asset yet. The fix isn't a document; it's a structural change to how the thing runs. You have to engineer yourself out of the critical path before anyone can step into it. That can take weeks, and occasionally it can't be done at all without changing what the project fundamentally is.

A no on test 4 is a metrics-discipline problem. Start keeping clean records today and you're three months from passing, no sooner. There's no shortcut – you can't retroactively manufacture trust in numbers you weren't tracking.

A no on test 5 means you stop and call a lawyer before you do anything else. Don't list, don't negotiate, don't take a deposit. Resolve the ownership question first, because every hour spent on a deal you're not legally clear to make is an hour you'll want back.

The 30-day path from 'almost' to 'listable'

Most builders who run this score three out of five. Tests 1 and 2 are usually fine; the gaps cluster around 3 and 4 – the project runs through you, and the records are thin. Both are typically a 30-day fix: a week consolidating ownership and writing the description, a week building the operating manual that makes test 3 pass, and a three-month clock on clean records that you start now. The week-by-week version of that sequence is its own piece – the 30-day pre-sale checklist – so run the diagnostic first, then follow that once you know which gaps you're closing.

The test-3 fix is the one worth seeing concretely. A newsletter doing $5k a month scores four out of five and fails test 3, because the founder writes every issue and the whole thing stops the week they stop. The fix: hire a freelancer to draft two issues against the existing voice guide, document the sponsor-outreach process, and check the test issues land within the audience's tolerance. If opens and replies hold, the project just passed test 3. It runs without its founder. It's listable.

When the answer is "not yet, and not in 30 days"

Some projects won't pass in a month, and the honest move is to say so plainly rather than talk someone into listing a thing that will sit unsold and sour.

The clearest example is the single-client service business. Picture a custom-built tool doing $2k a month from one client who pays $24k a year. It can pass tests 1, 2, 4 and 5 cleanly. It still fails test 3 at the structural level, because the asset is the client relationship, and a relationship doesn't transfer in a deed. The honest answer isn't "fix it in 30 days." It's "this isn't sellable as an asset. The underlying skill is sellable as a service. Those are two different businesses, and only one of them is for sale here."

The other irreducible cases: revenue concentrated in one customer who could leave; an IP situation that's genuinely contested rather than just untidy; a platform whose terms make the asset non-transferable by design. None of these is a 30-day fix. Some are six-month projects. A few are "this will never be a clean sale, and that's fine – just don't build a listing around the pretence that it is." Knowing which bucket you're in is the entire value of running the diagnostic honestly.

What being listable buys you, even if you never sell

Here's the part worth staying for. Every test in this diagnostic is also a test of whether your project is a real, independent thing or an extension of you. The documentation that closes test 1, the ownership map that closes test 2, the operating manual that closes test 3, the clean records that close test 4 – none of that work is wasted if you decide to keep the project.

A project that passes all five is one you can hand to a co-founder, delegate to a contractor, raise money against, or simply step back from for a fortnight without the dread. The disciplines that make an asset sellable are the same disciplines that make it operable by anyone other than its founder. Sellability is just the cleanest external test of internal health.

This is also where a platform built for this end of the market earns its place. Indiemaker exists for exactly this transition – the builder standing in the kitchen at half eleven, deciding whether the thing they made can become something someone else owns. The diagnostic above is the work you do before you ever list. The platform is what you use once the answer is yes.

So run the five tests tonight. Whatever the score, you'll know something concrete in the morning that you don't know now – not whether you want out, but whether you can get out cleanly. That's the only question worth answering first.

Quick reference: the five-test diagnostic

Save this somewhere you'll find it again.

#	Test	A "no" means
1	Can you describe the asset in two sentences, no notes?	Documentation pass – a day or two
2	One owner of record for every external dependency?	Ownership-cleanup sprint
3	Could someone else run it for four weeks unbroken?	It's a job, not an asset yet – the expensive fix
4	Three months of clean revenue records to show a buyer?	Metrics-discipline sprint – three-month clock
5	Is it legally yours to sell, free of claims and TOS blocks?	Lawyer before listing – stop until resolved

Score 5/5 – sellable now. Score 3–4 – usually listable inside 30 days. Failing test 3 or 5 structurally – not yet, and possibly not in 30 days. Be honest about which one you are.

For the deeper version of what a buyer is actually checking once you list, our proportionate due diligence guide walks the same ground from the other side of the table – a reminder that the questions above aren't bureaucratic. They're the ones any serious acquirer will ask before they wire a penny.