The Asset Inventory That Turns a Scary Handover Into a Boring One
In short
The deal doesn't die at the price. It dies in the handover – and one document, built before you list, prevents almost all of it.
Most sellers pour their prep into the numbers – clean P&L, tidy traffic, defensible multiple. Almost none prepare the thing that actually breaks late-stage deals: the transfer itself.
Why transfers stall, and how a handover works layer by layer, is covered in the transferability guide. This piece is about something narrower and more practical: the single document that de-risks the whole thing, and the one legal trap most sellers don't know is sitting inside it.
The fix is unglamorous. Build a complete asset inventory before you list, not after you've shaken hands and the buyer is waiting.
The document itself
A complete inventory is one page, structured as four columns:
- What the asset is – the domain, the repo, the payment account, the email list.
- Who controls it – which account, whose name, which registrar or platform.
- How it transfers – a clean handover, or the migration path if it can't move directly.
- Known blocker – transfer locks, personal-account dependencies, anything that will slow the move.
Run everything that has to move through those four columns and you have a handover document ready to give a buyer before they even ask for one.
What has to move falls into five buckets: domains and DNS, code and hosting, accounts and analytics, revenue rails, and customer data. The mechanics of why each is awkward – especially why payment processor accounts can't simply be reassigned to a new owner – sit in the transferability guide linked above. For the inventory itself you don't need the theory. You need to have actually checked each line: gone and confirmed who owns it and how it moves, rather than writing down what you assume is probably true.
It doesn't need to be polished. It needs to be honest. The useful version is the one where you've verified every row.
The landmine most sellers don't know is live
Four of the five buckets are logistics. The fifth – customer data – is where a deal can hit a wall that goodwill can't fix, because the problem is legal, not operational.
Your terms of service and privacy policy contain statements about how user data is handled. If you ever told your users "we will never share your data with third parties," you may have just described the buyer: a third party you have no lawful basis to share their data with.
Under GDPR and similar frameworks, transferring a subscriber list or user database without a lawful basis isn't a paperwork technicality. It's a genuine liability, and it lands on the buyer the moment the deal closes. A newsletter or app built under terms that prohibit exactly what the sale requires is a business whose core asset legally can't move. The list is the thing being bought. The list is the thing that can't be sold.
So this is the row to check first, not last. Before you list, read what you actually promised your users, then confirm a sale is compatible with it. If it isn't, that's a problem to fix early – with proper wording and consent – not one to discover with a committed buyer waiting on the transfer.
A clean inventory is a pricing lever
The payoff isn't only defensive.
Buyers are pricing risk, and in a sub-$200k deal the biggest risk usually isn't the fundamentals – it's the fear of what they can't see. The domain is probably fine. The accounts are probably transferable. But "probably" is uncomfortable, and discomfort compresses offers.
A seller who hands over a clear, verified inventory has removed that discomfort before it becomes a negotiation. They've shown operational competence and shrunk the buyer's perceived risk, and that shows up in the price, the speed, and how the whole deal feels. It's the same preparation that runs through the 14-day handover sprint: everything documented, every path mapped, every blocker defused before it's live.
That's the whole point. When the transfer is boring, both sides get exactly what they agreed to, nobody loses two weeks untangling preventable problems, and the deal that should have been straightforward turns out to be.
Build the inventory. Keep it current. Check the customer-data row first. Then let the handover be boring.
More on transfer

What an Asset Sale Agreement actually covers when you buy or sell a digital asset – parties, asset description, price settled in …

The legal essentials of buying or selling a mobile app – IP and asset transfer, app-store account moves, the agreement, and what …

The single highest-leverage thing you can do before listing is not tidy the code or raise the price. It is writing the …