Cash at Close: Reading an App Offer Past the Headline Number

Two offers arrive for the same app carrying the same top-line number. One is worth considerably more than the other, and the difference has nothing to do with how hard anyone negotiated. It is in the structure — how much is paid at closing, how much is conditional, what happens if the metrics move, and how long you stay attached to a business you no longer own. Founders tend to compare offers on the headline. Buyers build them on everything underneath it.

1. Cash at close is the only number that is certain

Start every comparison by stripping the offer down to what actually lands in your account on closing day. Everything else — earnout, holdback, seller note, retained equity — is a claim on a future that has to happen first. That does not make the rest worthless. It makes it a different asset with a different probability attached, and it should be evaluated that way rather than added straight into the total. A structure that is heavily back-loaded is not automatically a bad deal. It is a deal where you are still carrying risk after you have handed over the keys, and you should be paid for carrying it.

2. An earnout is a buyer naming a risk out loud

When a buyer proposes an earnout, they are telling you which part of the story they are not yet willing to pay for. In app deals it is usually one of a small set: retention that has not been observed long enough, revenue concentrated in a single feature or a recent campaign, an install base built through paid acquisition whose economics may not survive the handoff, or a monetization change that has not yet cycled through a full renewal period. Naming the risk is not an insult. It is a starting point.

What matters is the mechanics. Which metric, measured how, over what period, and — the question founders skip — who controls the levers that move it. If the buyer takes over user acquisition spend, store listing optimization and pricing on day one, and your earnout is tied to revenue, you have accepted a payment schedule you can no longer influence. Tie it to something durable and observable, cap the measurement window tightly, and get the reporting obligation in writing.

3. Holdbacks answer the question "does this actually belong to you"

A holdback or escrow exists to cover what turns out not to be true. In app transactions the recurring items are specific. Code written by contractors without a signed IP assignment. Third-party SDKs and libraries whose licenses do not permit commercial transfer. Store accounts with unresolved policy strikes or a review history that complicates a transfer. Privacy and consent obligations that were handled informally. Refund and chargeback exposure that has not finished aging. Every one of those is cheap to resolve before a buyer finds it and expensive to resolve inside a holdback negotiation.

4. The transition period is real work, and it should be priced

Almost every app deal includes some post-close involvement, because almost every app has knowledge that is not written down. Store account and developer program transfers, backend and hosting migration, API and signing keys, analytics and attribution tooling, ad network accounts, the build and release pipeline, the support queue. Scope it in the agreement as a defined number of hours over a defined number of weeks, with anything beyond that billed. An open-ended commitment to be "available for questions" has a way of becoming a part-time job that nobody agreed to pay for.

5. The non-compete is the clause that prices your next app

If you build apps for a living, this is the term with the longest tail. Buyers reasonably want protection against you launching a competitor. What you want is a definition narrow enough that you can keep working — bounded by a specific category or use case rather than by an entire platform, with a duration that matches the buyer's actual risk rather than the longest term their counsel could ask for. Read it as though you already have your next idea, because you probably do.

The takeaway

The headline number tells you what a buyer is willing to say. The structure tells you what they actually believe. Compare offers on cash at close first, then price the conditional pieces by how much control you retain over whether they pay out. The best offer is frequently not the largest one, and the founders who understand that before diligence starts are the ones who end up negotiating terms instead of accepting them.

Wondering what your app could be worth? Request a free, confidential app valuation from AppBusinessBrokers.com, or book an intro conversation with Eric Owens. No hype, no obligation — a straight read on where you stand.