AXIS Launch List your app
M&A & Exit Readiness processtimeline

How long does a micro-SaaS sale actually take?

Started by AXIS Editorial

Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.

The question: "Planning my year around a sale and getting timeline numbers from 'two weeks on a marketplace' to 'nine months.' What's the honest distribution for a small AI app, and what actually determines where in it I land?"

The answer. Both numbers are real; they describe different deals and mostly different preparation states. The honest decomposition — five clocks that run partly in parallel, with the ranges observed across micro-SaaS marketplaces and broker reports:

Clock 1 — preparation (your controllable clock): zero to three months. The financial package, transfer inventory, documentation stack — everything this category's curriculum covers. Sellers arriving prepared start clock 2 immediately; sellers preparing reactively run this clock inside clocks 3-4, where each missing artifact costs calendar time at the worst exchange rate (buyer-waiting weeks). The two-week legends are almost always sellers whose clock 1 ran for years as operating habit — the entire compounding thesis, timeline edition.

Clock 2 — market exposure to serious interest: two weeks to three months. Listing to first qualified conversations. The variance drivers: asset attractiveness (the valuation thread's top-of-range column doubles as a speed column — verified, documented apps surface serious buyers fastest), pricing realism (the actually-a-job arithmetic and SDE honesty — overpriced listings age on the market, and listing age itself becomes a negative signal buyers read), and venue fit (auction windows compress this clock by construction — a defined bidding period converts browse-someday interest into act-now decisions; open-ended listings let buyers wait you out).

Clock 3 — diligence: two weeks to two months. The buyer's-hour thread described the compressed version; the range depends on preparation (again) and deal complexity (the concentration thread's consent processes, partial-verification reconstruction, anything the checklist found late). Passport-verified, package-ready sellers report diligence in days-to-weeks; the two-month tail is almost entirely discovery — things surfacing that should have been disclosed, each one restarting some trust.

Clock 4 — agreement to close: two to six weeks. Purchase-agreement negotiation (reps, escrow, transition terms — the threads above), consent processes where applicable, and funds mechanics (escrow services at micro scale are standard and add days, not weeks). The tail here is legal ping-pong, minimized by standard documents and scoped counsel (the few-hundred-dollar-review economics, deal edition: micro-deals die of legal-cost-to-deal-size ratio when both sides' lawyers bill like it's a $50M deal — agreeing early to standard-form documents is a timeline decision).

Clock 5 — the one nobody plans: decision latency. Yours and the buyer's. Sellers' post-mortems of slow sales consistently feature their own hesitation at commitment points (the reserve decision, the first real offer, the reps negotiation) — the exit conversation from the co-founder category's four-conversations thread, arriving unrehearsed at the worst time. Buyers stall too (financing, competing deals, cold feet); the auction structure's bid-binding rules exist against exactly that, which is a reason sellers choose it beyond price discovery.

The honest planning distribution, all clocks summed: prepared seller, realistic price, auction-or-active venue: 6-12 weeks listing-to-close is a normal outcome. Median reality across all sellers (preparation incomplete, pricing discovering itself, direct-sale meandering): 4-7 months. The nine-month tail is preparation-during-deal plus a discovery or a consent process. Which is the answer's real shape: the timeline mostly isn't a market fact — it's a preparation fact. You choose your distribution now, this year, by which clocks you run before listing instead of during.

Where's your clock 1 actually at? Post the honest state — the gap between 'planning to sell this year' and 'package ready' is this thread's most common and most fixable finding.

Replies (4)

AXIS Editorial

Follow-up from maker intake: "Clock 5 hit home. What are the commitment points I should rehearse before listing, and what does rehearsal even mean for a decision like 'accept the offer'?"

The rehearsable points, in arrival order, with the rehearsal form for each: (1) the reserve/floor decision — the number at which you'd sign today without a second thought (the auction thread's framing); rehearsal is writing it down with its reasoning before market feedback exists to anchor-drag it, then pre-deciding what evidence would legitimately move it (new growth data: yes; a buyer's lowball plus fatigue: no); (2) the first-real-offer moment — offers below hopes but above floors create the classic freeze; rehearsal is the pre-written decision rule ('at floor-to-floor-plus-20%, I counter once at X and accept the result') — mechanical rules feel unromantic exactly until the emotional moment they were built for; (3) the reps-and-escrow flinch — signing warranties feels different from reading about them; rehearsal is the mock run-through: read the standard purchase-agreement form now (they're available), imagine signing each rep for your actual app, and note which ones scare you — that fear list is your remaining preparation queue (the boring-reps thesis from the structure thread, used diagnostically); (4) the identity moment — the underrated one: sellers stall at closing because the app is who they've been; rehearsal is the co-founder category's exit conversation had with yourself, including the day-after plan (the next build, the rest, the non-compete-shaped sabbatical). Decision latency compresses to near-zero for sellers who've met each moment before it's live — which is cheap, since every rehearsal above is an evening.

AXIS Editorial

Follow-up from maker intake: "'Listing age becomes a negative signal' — my listing's been up four months with two lowballs. Am I now damaged goods, and what's the reset move?"

The signal mechanics first: aged listings read as 'the market has seen this and passed,' which buyers price defensively — but the signal attaches to the listing-as-presented, not the asset, which is what makes resets real rather than cosmetic. The honest diagnostic before any reset: four months with only lowballs is the market saying one of three things — price above the arithmetic (the SDE and actually-a-job audits, re-run cold; this is the answer in most cases and the one sellers check last), evidence below the claims (attractive numbers that aren't verifiable get browsed and skipped — the whole verification curriculum), or venue-shape mismatch (a concentrated/complex asset sitting in a browse-listing format when it needed the auction window's forcing function or direct outreach to profile-matched buyers). The reset that works is substantive relist: fix the diagnosed problem (repriced, or re-evidenced — Passport months accrued, package built, the trendlines the threads keep prescribing), then relist with the delta explicit ('relisted [month]: now includes 8 months verified revenue, reconciled financials, revised terms') — the dated-changes format converts 'still for sale' into 'differently for sale,' which buyers legitimately re-evaluate. What doesn't reset anything: same listing, new coat of adjectives, third marketplace — buyers cross-browse, and the asset seen everywhere priced identically is the aging signal amplified. And the withdrawal option is real too: if the diagnostic says 'the asset needs a year of the curriculum,' unlisting to run clock 1 properly beats marinating in market-age — the listing's permanence promise here covers listings, not for-sale status.

Jonathan (AXIS Launch)

The venue-fit variable deserves the platform's honest elaboration, including where our own model isn't the answer: auction windows compress clocks 2 and 5 by construction (defined period, binding bids, reserve mechanics — the forcing functions this thread credits), and that compression is real for assets that fit the format: verifiable, legible, priced-in-range apps where a bidding population can form. Where the auction shape underperforms: assets needing a specific buyer (the strategic-fit and anchor-as-buyer patterns — one right acquirer isn't a bidding population; those deals are direct-outreach shaped, and the listing's job is discoverability while the deal happens in conversations), and assets whose diligence is inherently long (heavy consent processes, complex partial-verification stories — a 30-day window can't contain a 90-day consent clock, and forcing it produces failed auctions that then carry age-signal). Our own guidance to sellers at intake reflects this: the auction is the default for the prepared-and-legible; the direct path with platform verification underneath is the fit for the specific-buyer shapes. The meta-point for the timeline question: venue choice is a clock decision, and choosing by preparation-state and buyer-shape beats choosing by fee schedule every time.

AXIS Editorial

Follow-up from maker intake: "What can I run in parallel versus what's strictly sequential? A dependency map of the five clocks would change my year's plan."

The dependency map, honestly drawn: fully parallel with everything — clock 1's artifacts (each document builds independently; the reconciliation doesn't wait for the runbook), verification accrual (the Passport clock runs through every other clock — connect-now logic yet again), and the enterprise-consent groundwork if the concentration thread applies (renewal negotiations are a business-as-usual activity no buyer process needs to know about). Sequential by nature: listing follows preparation (the aged-listing reply is the cost of inverting it), diligence follows serious interest, agreement follows diligence-substantially-complete (parallel-track agreements-during-diligence happen in hot processes and can compress weeks — but every discovery mid-negotiation reprices from a worse position, so the compression is a confidence bet on your own package's completeness: prepared sellers can afford it, others can't). The false sequential — things sellers queue that shouldn't wait: counsel selection (retain-and-brief before listing, not at first offer — the scramble-hire bills worse and reads worse), the transition checklist (pre-closing work per the transition thread, startable at listing), decision rehearsal (the commitment-points reply — before listing, definitionally), and buyer-side diligence prep (your questions for them, the two-way-diligence field note — ready before the first conversation, because asking late looks like afterthought and asking early looks like professionalism). Drawn as a year plan: months 1-3 clock 1 plus rehearsal plus counsel, listing at month 3-4 with everything parallel-ready, and the 6-12-week prepared-seller distribution becomes your realistic window for months 4-7 — with the tail risks named, mapped, and mostly pre-drained.

Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.