handing over a $900/mo tool — what order do stripe, dns and the repo move in

Costs to have in the model, since at nine hundred a month every hundred matters.

If a marketplace is involved, the seller side closing fee on small deals runs high single digits of the sale price, which on a deal this size is real money. Escrow may be included or may be separate. Expect the buyer to ask for thirty to sixty days of transition support, so price your evenings into the number rather than discovering them.

Also agree in writing what happens to annual customers who already paid you for months the buyer will have to serve. Either you transfer a prorated amount at closing or you knock it off the price. Doing this after the fact is how friendly deals turn sour.

One correction on the domain: a domain can be locked against a registrar transfer for sixty days after certain changes, which people discover on closing day. If you are both at the same registrar you can usually push the domain between accounts internally and it is effectively instant. Check which situation you are in a month early, not the morning of.

Write down what happens if the migration goes wrong halfway. Who reverses what, who tells the customers, who eats the refunds. Ten minutes on that beats any checklist.

The bit that is easy to skip: check that you are allowed to hand over the customer data at all.

Your privacy policy should say something about a change of ownership. If it does not, you have a problem you want to find now rather than after. Any enterprise-ish customer contract may have a change of control clause requiring notice or consent. And decide when customers hear about it, which in my opinion is the day it happens, from you, in plain language, with a name and a face attached to the new owner.

Also do not send the list before the money is genuinely in escrow. A spreadsheet of customers is the only asset in this deal that cannot be un-sent.

And do not let the buyer point DNS at their box before the app is genuinely serving. I watched a planned forty minute cutover become three days of intermittent errors purely because the order was reversed and half the world was still cached on the old record.

Did a much smaller version of this last year and the thing that saved us was a shared document with two columns, mine and theirs, and every asset as a row: domain, DNS, repo, hosting, database, error tracking, email sending, analytics, the support inbox, the social account, the docs site, the status page, and every third party key. Twenty three rows. We ticked them off on a call together. Three of them were things I had completely forgotten existed and one of them was still billing my personal card.