Jacqui Lillyman Dencic

I recently launched Pinky Promise, a little app for making promises with friends.

The feedback has been lovely. People call it cute, say it's a great idea, and seem to like the concept.

But here's the thing: I'm not sure people would actually use it.

Curious how people here handle this in practice. When an agent has a card or API budget for bookings and SaaS, do you use a hard daily cap, approve each charge, or something else? The acting side keeps getting better, but money controls still feel bolted on.

"User requesting some feature." This is an observation. "Ten users requesting very similar features." This is a pattern. It took me way too long to figure out that our five most frequently requested features were actually the same one feature under different names because the exact wording was never the same.

I figured this out while manually re-reading three months of support tickets on a lazy Sunday morning, which clearly isn't a scalable solution. I wonder how other people find such patterns without filtering out all the important signals or being alarmed by everything coming in as a request.