Early in almost every conversation about selling an app, the buyer asks some version of the same question: why are you selling? Founders tend to treat it as small talk. Buyers do not. It is one of the few questions where the buyer is listening less to the answer itself than to how well it fits everything else they are about to learn.
1. What the buyer is really asking
Every buyer starts from the same uncomfortable position: you know the app far better than they ever will. You know whether the last update hurt retention, whether a competitor is about to launch, whether a platform policy change is about to bite. "Why are you selling?" is the buyer's way of asking whether you are leaving because of something you know and they do not. They are not looking for a perfect story. They are looking for a reason that explains the timing without pointing at a problem.
2. Reasons buyers hear all the time, and accept
Most honest reasons are unremarkable, and that is fine. A founder wants to put their time into a new product. A small team has taken the app as far as it can without a marketing budget, a bigger engineering bench, or a growth function they have no interest in building. A founder runs several apps and wants to concentrate on one. A life change: a new role, a family situation, a move. Even "I have been doing this for years and I am tired" is a reason buyers hear often and understand. None of these lowers a buyer's opinion of the app on its own. What matters is what comes next.
3. The answer has to match the data
A reason for selling is a claim, and buyers test claims. If you say you want to move on to a new venture, but subscription revenue has slipped for the last two quarters, the buyer will assume the slip is the real reason until you show otherwise. If you say the app runs itself, and also that you are burned out, both cannot be fully true, and the buyer will want to know which one is. If you say the app needs more resources than you can give it, the buyer will look for the evidence: growth that flattened when paid acquisition stopped, a feature backlog, reviews asking for things you have not built. A plain reason the numbers support does more for a sale than a polished one they contradict.
4. Where founders get it wrong
The most common mistake is a vague answer. "Just exploring options" or "seeing what the market says" tells a buyer either that you are not committed to selling, which makes them reluctant to spend money on diligence, or that you are holding the real reason back. The second mistake is an answer that drifts. A founder tells a buyer it is about a new project, then later tells the same buyer's diligence team it is about time with family. Both may be true, but the shift reads as a story being managed. The third is over-explaining. A long account of why the timing is perfect makes a buyer wonder what it is defending against.
5. How to prepare your answer
Write it down before the first buyer conversation, in two or three sentences. Make it true, give the same answer every time, and connect it to what happens after closing: how long you will support the transition and what you plan to do next. If there is a soft spot near the reason, such as a recent dip in downloads or a dependency on one store, name it yourself in the same breath and show what the data says. A buyer who hears about a weakness from you can size it. A buyer who finds it alone starts to wonder what else your reason for selling left out.
The takeaway
Buyers do not need an exciting reason for selling. They need one that is true, consistent, and supported by your numbers and your transition plan. Treat "why are you selling?" as the first piece of diligence, because that is how buyers treat it. A clear answer early makes every later question easier to answer.
