You built something that makes money. Now you want out — or at least want to know what it's worth. This course takes you from "I have no idea what this is worth" to a priced, packaged, listed asset that attracts real buyers.
"I built an AI tool. It has paying users. I think it's worth something. But I genuinely don't know if anyone would buy it, or for how much, or what I'd even need to do before listing it."
Most AI builders who want to sell their project think the main question is "how much." The real first question is "is it ready" — and the answer changes what you do next.
We score AI projects on 5 dimensions, weighted as Traction 25, Revenue 25, Transferability 20, Automation 20, and Risk 10. Total 0–100. This is the AI Asset Score.
| Criterion | Max Score | What it measures |
|---|---|---|
| Traction | 25 | Evidence of real demand, usage, and retention. |
| Revenue | 25 | Quality, durability, and proof of current revenue. |
| Transferability | 20 | Can a new owner take over without relying on the founder? |
| Automation | 20 | How much of the operation runs reliably without manual intervention? |
| Risk | 10 | Platform, legal, technical, and concentration risk. |
| Band | Score | Meaning |
|---|---|---|
| Approved Candidate | 85–100 | Strong evidence across all five dimensions. |
| Asset Candidate | 70–84 | Credible asset with identifiable packaging gaps. |
| Potential Asset | 50–69 | Working project that is not yet transfer-ready. |
| Demo or Toy | <50 | Prove demand and operability before listing. |
Answer these 7 questions honestly, score yourself 0–2 on each:
10–14 out of 14: You're ready. Start Module 2.
6–9: Get a free AI Asset Score — you need specifics on what to fix.
Under 6: Focus on the product for 2-3 months, then come back.
Sellability is about transferability, not just revenue. A project that makes $3k/month but only works because you're there every day is worth much less than one that makes $1k/month and runs itself. Fix transferability first — it's what unlocks the valuation premium.
"Someone offered me $5,000 for my bot. It makes $600/month. I said yes without thinking. Later I found out I should have asked for $10,000–$15,000. I left half the value behind."
This story is common. AI builders systematically underprice their projects because they don't know the market benchmarks. Here's what the data actually shows.
Net revenue means after API costs, hosting, and any contractor costs. Not gross.
Don't start with a number — start with the story. Present your financials as a timeline: "Here are the last 6 months of MRR. Here's the churn. Here's what it costs to run. At current numbers, you're looking at a 17-month payback, which is well inside the healthy 12-24 month range."
Then name your price. Anchored to data, not to what you feel you deserve or what you need to replace your income. Buyers pay for math, not for your sunk cost.
Your price is Net MRR × (12–24). Where you land in that range depends on your churn, trend, concentration, and documentation quality. Know your number before you talk to any buyer — and know how to justify it with data, not feelings.
"Everything is in my head. The code is a mess I never cleaned up. I have Notion docs half-started but they're outdated. I don't know where to begin."
Packaging is the single highest-ROI activity a seller can do. Proper documentation doesn't just make transfer possible — it raises your valuation by 30-60% and cuts time-to-close from months to weeks. Here's the 4-week plan.
List every single account, API key, domain, server, and service the product depends on. Organize into a spreadsheet: service name, URL, login method, current cost. This is your transfer manifest. If you can't complete it in a week, the product is not ready to sell.
Write a README-level document: how does this work? What does each part do? How do you restart it if it crashes? What are the main dependencies? Have a non-technical friend read it. If they can't follow the logic, it needs more work.
List every paying customer: name, email, plan, how long they've been paying, any notes about their usage or requests. Identify your top 3 by value. Note any at risk. This document is gold to a buyer — it shows you know your customers and the relationships can transfer.
How do you run this thing day-to-day? What do you check in the morning? What does support look like? What are the 10 most common customer questions and their answers? Write the operations manual an intelligent non-technical person can follow from day one.
The last point matters: known issues documented honestly. Hiding problems doesn't work — buyers find them during due diligence or after close, and both outcomes are worse than disclosing upfront. Transparency at packaging stage builds trust that closes deals.
Documentation can materially improve transferability and reduce buyer uncertainty, but it does not guarantee a higher price or a sale. Package the asset before listing and let evidence support the valuation.
"I posted on Indie Hackers. I posted on Twitter. I got questions from people with no money and no intention of buying. Zero serious inquiries. I don't know what I'm doing wrong."
Most AI project listings fail for one reason: they describe the product instead of the opportunity. Buyers don't want to understand your tech. They want to understand: can I make money with this, and is it safe?
Channels in order of quality for AI assets in $5k–$100k range:
Your listing is marketing for a financial product. Write it like an investor memo, not a product launch post. Lead with the outcome for the buyer, support it with real numbers, and give enough detail that a serious buyer can evaluate without asking 20 questions first. The best listings attract 2-3 serious buyers, not 50 curious ones.
Before you list, know what you're working with. We score your project across 5 dimensions and tell you where to focus your packaging effort for maximum sale price.
Get a AI Asset Score →