closing the loop when the answer is "no"
a public "won't do" is the highest-trust move a roadmap has. how to write the rejection, when to send it, the three flavors of no, and the four ways teams botch it.
- feedback
- playbook
- roadmap
how we think about feedback, pricing, and building tools for indie SaaS.
a public "won't do" is the highest-trust move a roadmap has. how to write the rejection, when to send it, the three flavors of no, and the four ways teams botch it.
metering on tracked users doesn't just raise the bill. it quietly teaches your team to collect less feedback. how the metric attacks each step of the loop.
the tradeoff isn't "push vs pull" — it's which failure mode you'll debug at 2am. when each is right, and why serious integrations do both.
when is a feature request validated enough to commit to? the heuristic we use, three modifiers it needs, and the cases where you should ignore it.
most feedback systems work backwards — they reward you for hearing less. a six-step playbook we use ourselves, with the trade-offs spelled out.
tracked-user pricing punishes growth. flat pricing aligns incentives. why we copied plausible's model instead of canny's, and what we give up.
three concrete workflows: linear sync on vote thresholds, slack alerts on shipped posts, and a dashboard mirror with hmac verification. copy-paste ready.
a no-fluff comparison of canny, featurebase, userjot, frill, and spirby. real prices, real api access, no scoring rubric. you decide.
feedback tools gate the api behind enterprise, betting you'll never integrate. you will. what changes when the api is on every plan.