Yuzool / Field notes · 19 Aug 2026
What to measure after your first app sale
The first sale is proof of a decision. The next job is learning which decision to repeat.
It is tempting to add every dashboard after a first purchase. More data feels like more certainty. In practice, a small product usually needs four answers: where did the person come from, what promise did they respond to, did they reach the useful moment and what would make them return?
1. Source
Record the page, post, directory or conversation that led to the click. A simple tagged link is enough at the beginning. The point is not attribution theatre; it is knowing which door deserves another visit.
2. Promise
Write down the sentence the buyer saw. Was it “see Stripe and Polar together,” “split a trip without a spreadsheet” or something else? The language around a sale is evidence about the job the product is being hired to do.
3. Activation
Choose one useful moment and watch for it. In a revenue app it might be connecting a source or seeing a product total. In a travel app it might be adding the first shared cost. In a launch tool it might be completing the first brief.
4. Return reason
Ask what brings the person back tomorrow or next week. That answer can shape the next feature, the next screenshot and the next article. Revenue Bear is built around the small daily revenue check; Dispatch Kun turns a release workflow into a repeatable review.
Keep the loop small enough to use
A first sale should make the next experiment clearer, not create a new job maintaining ten reports. Track the few signals that change what you will do next, then make that next action while the evidence is still fresh.