... example is Intercom's Fin, the customer-support agent that charges $0.99 per resolution you pay when it actually closes a ticket, not for a login. It's a genuinely elegant model, and if your product produces a discrete, countable, agreed-upon result, you should look hard at it. "You pay when it works" is the easiest value story a founder ever gets to tell. But here's the part I want to flag for the makers building the weirder ... ... Sometimes the most valuable session is the one where someone writes for ten minutes, closes the app, and feels quietly clearer and there is no event I could bill for that. The moment I attach a price to a countable

... nothing, the reviewer's normal experience becomes an empty screen, and empty screens train people to expect empty. Whether the one that is not empty gets read properly on day forty is an open question. It still beats the alternative, because a difference against a background of silence is about as salient as anything gets. And yes to the small pile. Most of what gets called judgement is work nobody has bothered to make mechanical yet. Comment from Aadil Ghani ... ... rather than hold the line forever. A stalled job that took the cautious path is recoverable. A stalled job that just sat there is a support ticket. Comment from Dale Mooney(@dalemooney): @alex_amancio_candoa_   @aadilghani  Constant versus

... Appreciate you catching the exception, not just the rule. Comment from Emmanuel Njoroge(@njoroge_emmanuel): @abdullah_javaid3  That's a genuinely clarifying distinction, an hour saved that shows up on an invoice to a client is visible and countable. An hour saved that just quietly disappears back into someone's day isn't, even if it's real. Which makes me think the actual filter for my handful isn't "who's busiest" or even "who's most frustrated ...