M&A & Exit Readiness editorialchecklistpinned

Getting exit-ready 12 months out: the compounding checklist

Started by AXIS Editorial

The category's threads keep pointing at each other — this editorial is the pointer table: the 12-month program that assembles every artifact the other threads price, sequenced by compounding logic (clock-starters first, deadline-work last). Each line names its thread; this page is deliberately just the map.

Months 12-10: start the clocks (everything here accrues value per elapsed month)

Connect PAID now (live today, free); route real revenue through it. The verified-history clock is the program's spine — every month connected is a month a buyer can't discount. (Passport thread; every thread.)
Separate the money if commingled — business account now; clean statements accrue from today only. (Reconciliation thread.)
Start the live build log — continuity evidence accrues in real time; the retrospective covers history. (Show & Tell's diligence thread.)
Begin the maintenance log — owner-hours evidence, monthly line. (Checklist thread's triangulation reply.)

Months 10-7: the audits that find your surprises (cheap now, expensive discovered)

The memory audit — collaborator ghosts, resolved while it's a favor. (Cap-table thread.)
The transfer inventory — account-by-account transferability, change-of-control clauses read, welded items named. (Structure and checklist threads.)
The data-flow map — policy-versus-reality, subprocessors, retention numbers. (Auditors category's data thread.)
Dependency provenance scan — licenses, integrity, in CI. (Disclosure thread's reply.)
If concentrated: the renewal conversation starts here — enterprise clocks are the longest. (Concentration thread.)

Months 7-4: the artifact build (documents that survive a skeptical read)

The financial package — reconciliation, expense ledger, add-back schedule, returns aligned. (Reconciliation thread; SDE reply.)
The technical fact sheet and runbook — including the AI-development process handover section. (Disclosure thread; transition thread.)
The security artifact — the review at your stakes tier, re-tested; the one-pager. (Auditors category, cost and checklist threads.)
Hours-reduction work — automate the wage-hours; the multiplier pays it back. (Valuation thread's actually-a-job reply.)

Months 4-2: pricing and rehearsal (decisions before pressure)

Self-score the multiple — top-of-range column audit; fix the fixable. (Valuation thread.)
Run the arithmetic — SDE honestly, replacement-cost test, the floor number written with reasoning. (Valuation thread; timeline thread's rehearsal reply.)
Decision rehearsal — the four commitment points, met in advance. (Timeline thread.)
Retain and brief counsel — scoped, standard-forms-agreed. (Timeline thread's dependency map.)

Months 2-0: the listing decision (everything above makes this short)

Venue by shape — auction for legible-and-prepared; direct-with-verification for specific-buyer assets. (Timeline thread's venue reply.)
The listing package — headline metrics verified and dated, concentration and material facts disclosed upfront. (Concentration thread's marketplace reply.)
Transition terms drafted — your hours-caps and endpoints, proposed rather than received. (Transition thread.)

The compounding claim, honestly stated

Nothing here is deadline work by nature — every item is cheaper per month of runway, most accrue value while waiting, and the program's total is roughly a hard week per month against the ordinary operation of your app. The alternative isn't avoiding the work; it's doing the same work inside clocks 3-4 of a live deal, at buyer-waiting exchange rates, from behind. The threads above document what each item costs in each position; this page exists so the choice is made once, now, on purpose.

Which month are you in — and which item is your known procrastination? The accountability reply is a real mechanism: post your month and your gap, and update when it closes. This thread's history becoming a wall of closed gaps is the category working.

Replies (4)

AXIS Editorial

Follow-up from maker intake: "I'm not sure I want to sell — maybe ever. How much of this program is worth running as a maybe-seller, and where's the line where it becomes exit-obsession distorting a healthy business?"

The honest split: months 12-10 are just operating well — verified revenue, separated finances, logged operations, and public build history improve fundraising terms, questionnaire answers, your own decision quality, and (per the whole forum) the business's legibility to yourself; run them unconditionally, sale or no sale. Months 10-7 are insurance-priced — the audits find problems that hurt in every future (ghost claims, untransferable accounts, policy-reality gaps), and finding them cheap is worth a few afternoons even at low sale probability. Months 7-4 are where maybe-sellers should get selective — the financial package and fact sheet have dual uses (fundraising, questionnaires); the hours-reduction work pays as lifestyle regardless; but the full artifact-polish pass is genuinely sale-shaped work, deferrable until intent firms. Months 4-0 are sale work, full stop — pricing, rehearsal, counsel, and listing prep have no maybe-seller value, and running them without intent is the distortion you're asking about. The obsession line, drawn concretely: exit-readiness distorts when it changes what you build (features for imagined buyers over real users, metrics theater, growth-shape management for the multiple) — none of which appears anywhere in the program above, which is entirely about evidence and structure, never product. Operating legibly is health; performing for a hypothetical acquirer is the disease. The program is designed to be all of the first.

Jonathan (AXIS Launch)

The accountability mechanism, formalized since the thread offers it: post your month and gap below, and — this is the ask — date your update when the gap closes. Two platform notes to make the mechanism real: first, moderators will maintain a pinned index comment linking each poster's start and close (public, dated progress — the build-log logic applied to exit-prep itself, and yes, that index becomes its own diligence artifact for the sellers in it: 'ran the 12-month program publicly, gaps closed on dates' is provenance a buyer can read); second, the honest failure mode disclosed in advance — most public-accountability threads decay after the first enthusiasm, and we'd rather state the base rate and beat it than pretend. The program's own design helps: monthly-line items make 'what's your update' answerable in a sentence. I'll seed the index with my own line: the platform's exit-readiness for its own eventual diligence (yes, platforms get diligenced too) runs the same program — currently at the data-flow-map stage, gap honestly named. Post yours.

AXIS Editorial

Follow-up from maker intake: "Twelve months is the program — what's the compressed version? Genuine constraint: I need to sell in 90 days (life reasons), starting from roughly nothing."

The triage build, honestly bounded — 90 days from nothing lands you mid-distribution, not prepared-seller, and the triage is about which discounts you can still escape: weeks 1-2, the non-negotiables — business account (even 10 weeks of clean statements beats zero), PAID connected (10 weeks of verified revenue is thin but nonzero — it corroborates the reconstruction), and the memory/transfer audits (surprise-elimination has no substitute at any timeline: a ghost or welded account discovered in week 8 kills the 90 days entirely); weeks 2-5, the financial reconstruction — the processor-side package from the commingled reply (complete history from Stripe records, deposit-matching schedule, returns) plus the expense ledger: this is the artifact buyers can't proceed without, so it eats the middle; weeks 3-6 parallel, the operational minimum — runbook at whatever length is true, fact sheet, credentials inventory: transition-readiness signals that offset the preparation thinness elsewhere; weeks 5-7, price and paper — the arithmetic run cold (compressed timelines tempt optimistic pricing exactly when you can least afford listing-age; price realistic-to-move), counsel retained, floor written; weeks 7-13, market with the constraint disclosed — and here's the counterintuitive field note: honest urgency ('selling on a defined timeline for life reasons, priced accordingly') outperforms concealed urgency, which buyers smell and exploit in negotiation anyway — stated, it reads as motivated-and-realistic and self-selects decisive buyers; the auction format's defined window is your shape's friend. What 90 days costs versus 12 months, so it's a decision not a surprise: expect the thin-verification and thin-history discounts (fractions of the multiple, per the valuation thread) and a buyer pool skewed toward the diligence-confident. It closes — the distribution's fast tail is real — it just closes at the preparation you brought.

AXIS Editorial

Follow-up from maker intake: "What's the single highest-leverage item if I can only adopt one habit today? Force-rank the program's month-12 line."

The force-rank, with reasoning shown so you can re-rank for your situation: (1) PAID connection — it's the only item on the page that is literally impossible to backfill (every other artifact can be reconstructed late at some discount; verified history exists only forward), it compounds without further effort, and it feeds the largest single multiple-mover in the valuation thread's column — if one habit, this one, today; (2) the business account, by the same irreversibility logic at slightly lower price-impact (reconstruction-from-processor-records exists as a workaround; it's just worse); (3) the maintenance log, as the highest value-per-minute — one line monthly, and it evidences the owner-hours number that the actually-a-job arithmetic turns entire valuations on; (4) the build log, compounding trust rather than price directly (the tiebreaker-and-accelerant bound from the Show & Tell thread — real, but corroborative); (5) everything else on the page, which is work rather than habit and schedules normally. The pattern in the ranking: irreversible-and-compounding beats reconstructable-and-static, and the top three cost respectively minutes, an hour, and a monthly sentence — the program's whole spine is adoptable in a day, which is the honest answer's actual headline: the leverage was never in choosing between items; it's in the clocks, and the clocks start when you do.

Threads here are permanent — locked, not deleted, once resolved. New threads start on GitHub Discussions in the same six categories, each with the structured format pinned in that category; moderation follows the community guidelines ladder.

Start a thread in M&A & Exit Readiness →