The 30-Day Pre-Sale Checklist for Small Digital Projects

There's a particular kind of listing that goes nowhere. The revenue figure is vague ("around $800/month, sometimes more"). The tech stack is described in one word ("WordPress"). The time commitment says "a few hours a week." The asking price is a round number with no reasoning attached.

These listings don't fail because there's no demand. They fail because the seller hasn't done the work that earns buyer trust – and unprepared listings signal exactly what serious buyers are scanning for: a seller who doesn't fully understand what they're selling, or what it's worth.

If you've been meaning to list your project for six months and haven't started, this is probably why. Not because you don't want to sell. Because preparing feels like a project in itself, and you don't know where to begin.

Here's where to begin.

Week 1: clean the numbers

Before you write a single word of your listing, pull at least six months of clean revenue data – twelve if the project is old enough to have it.

Not an estimate. Not a screenshot from your dashboard. A proper spreadsheet: monthly gross revenue, monthly expenses (all of them, including the Notion subscription you've been ignoring), and the resulting net profit. If you use Stripe or LemonSqueezy, export the full transaction history. Reconcile it with whatever accounting you've been doing, however informal.

The goal is a P&L you could hand to a stranger in five minutes and have them understand it. If that's not possible yet, it's the first thing to fix.

A few things to be honest about in this stage. Owner salary or founder draws are an expense – if you've been paying yourself and not recording it, buyers will find this gap in due diligence and reprice accordingly. Platform fees, hosting costs, and contractor spend are all operating costs, not noise. Include them. The number that matters is net profit, and it needs to hold up to scrutiny.

Why does this matter beyond basic transparency? Because the multiple buyers apply to your earnings is directly affected by how confident they are in those earnings. Clean, consistent, reconciled financials command better multiples. Vague financials invite aggressive discounting – often more than you'd have lost by spending a weekend getting this right.

The rule of thumb: if your P&L takes more than twenty minutes to produce and verify, your documentation isn't sale-ready.

Week 2: document the product

Write a handover guide – even if you never share it.

This is the most counterintuitive advice in this checklist, but it's the highest-leverage thing you can do. The act of writing a handover guide forces you to surface everything that lives only in your head. That tribal knowledge is both the thing buyers most need to understand and the thing most sellers underestimate.

What to include: the full tech stack (not just "it's built on Next.js" but the hosting provider, database setup, third-party APIs the app depends on, and what breaks if any of those go away). Every external service account that the new owner will need to take control of – payment processor, email provider, analytics, CDN, domain registrar. A login inventory. The DNS setup, including any subdomain configurations that aren't obvious from the main domain.

Then the less obvious parts. How do you handle customer support? What are the three questions you answer most often? Is there a recurring task that only you know to do, and only you know when to do it? These questions reveal owner-dependence – and owner-dependence is one of the first things buyers are looking for, because it directly affects the risk profile of the transfer.

A project that runs without you is worth more than one that runs because of you. The handover guide is how you prove the difference.

One practical note: the guide doesn't have to be perfect. It has to be complete. Rough documentation that covers everything is more useful – and more reassuring – than polished documentation with gaps.

Week 3: verify the traffic and revenue claims

Buyers discount what they can't verify. This is rational. If your listing says "12,000 monthly visits from organic search," but you can't connect a Google Analytics account to confirm it, serious buyers will discount that number heavily – not because they think you're lying, but because they can't afford to assume you're not.

Connect your analytics. If you're using GA4, get it linked. If you have Search Console data showing ranking keywords and click history, attach it. If your revenue flows through Stripe, the API connection is the cleanest possible verification – it turns a claim into a fact, and it compresses buyer due diligence from weeks to days.

If you don't have GA4 installed at all – common on older projects, side experiments, and anything built before 2022 – install it this week and wait thirty days before listing. Yes, that means delaying. A month of clean, live data is worth more than listing now with nothing to show. In the meantime, use the week to export whatever historical data you do have: old Universal Analytics exports, server logs, third-party analytics screenshots with dates visible. Incomplete verification is not the same as no verification.

This step matters more than most sellers realise, for a specific reason: the buyers who offer quickly and close cleanly are almost always the ones who could verify everything upfront. The buyers who take three weeks, ask for six rounds of screenshots, and then pull out at the escrow stage are usually the ones who couldn't verify the basics and spent the whole process building a case to discount or walk.

Verified data signals confidence. Sellers who offer it close faster and at better terms. The inverse is also true.

Week 4: write the listing properly

Most listing descriptions fail at the headline. Not because the business is weak – because the description is written for the seller's comfort rather than the buyer's evaluation.

"Profitable SaaS tool – great opportunity for the right buyer" tells a buyer nothing useful. It's the listing equivalent of a CV objective that says "seeking a challenging and rewarding role." The person writing it knows what they mean. The person reading it doesn't.

A high-converting listing has a specific structure. The headline names the asset type and niche: "Email automation tool for e-commerce brands – 3.2k subscribers, $1,400 MRR." The revenue summary is precise and honest: a trailing six-to-twelve-month average, not the best month, not an aspirational figure. The time commitment is stated plainly – buyers are extremely sensitive to undisclosed owner involvement, and finding out post-offer that "minimal maintenance" means fifteen hours a week is the fastest way to kill a deal.

The transferability statement matters more than most sellers include. What does a buyer actually need to take this over? Specific skills? Technical knowledge? Existing relationships? A particular software stack? State it plainly. Buyers who are the right fit will self-select in. Buyers who are the wrong fit will self-select out – which saves you both time and the particular frustration of a deal that collapses at transfer because the buyer couldn't actually operate what they bought.

Finally: the asking price needs reasoning, not just a number. On Indiemaker, the minimum listing price is $1,000 – but the platform's floor is not the reasoning. Your reasoning is. "Listed at $18,000, based on 12× average monthly net profit of $1,500" is a sentence that tells a buyer how you thought about the valuation and gives them something to respond to. An unexplained number invites unexplained counter-offers.

Why this sequence works

The four-week sequence isn't arbitrary. It mirrors how buyers evaluate a listing once inquiry starts.

Week 1 handles the financial scrutiny that comes first. Week 2 handles the operational and technical due diligence that comes second. Week 3 handles the verification questions that stall most deals in the middle. Week 4 handles the listing copy that determines whether you get serious inquiries or no inquiries at all.

Most transfer abandonment happens mid-process – after the offer but before the payment. The dominant reasons: confusion about the steps, unexpected fees, and misaligned expectations about what the transfer involves. Every element of this checklist is designed to surface and resolve those issues before listing, not after.

A prepared listing doesn't just sell faster. It closes.

The project you built is worth more than you think. A serious buyer is looking for exactly what you have. The only thing standing between you and the inquiry is a weekend of documentation work you've been putting off.

Do it this weekend. List next week.