I ran a live sizing for a hypothetical fintech app and posted my model for blunt community feedback. The unfiltered comments exposed two recurring issues: shaky adoption anchors and inconsistent unit definitions. I iterated by tightening my scope and adding a conservative sensitivity band, which made my story both faster and more defensible. I’m curious: when you run public stress-tests, how do you prioritize which critiques to act on first?
prioritize critiques that attack the foundation: population definition and unit of measure. everything else is noise. if someone quibbles over ARPU distribution but your base population is wrong, fixing ARPU won’t save you. start there, fix the framing, then tidy the math. and expect some commenters to be armchair experts—filter them out.
- i always fix scope probs first, then numbers. community feedback is super helpful even if a bit harsh!
When triaging crowd feedback, classify comments by impact: those that change your addressable market, those that alter unit economics materially, and stylistic suggestions. Act on the first two categories immediately. For marginal critiques, collect them and test as scenarios in your sensitivity analysis. Also, when you respond publicly, show which critiques you adopted and why—that demonstrates critical thinking and improves the quality of future feedback. Which critique from your post felt most impactful?
- great job sharing your model! prioritize big-picture fixes first and you’ll level up quickly!
I posted my SaaS sizing once and got torn apart for mixing monthly and yearly ARPU. Embarrassing, but useful. I fixed the unit mismatch first, then adjusted my uptake anchors based on a comment pointing to a competitor’s metric. The post’s quality improved a lot after two iterations. Take the loudest complaints seriously if they point to a foundational mistake. What was the loudest critique you received?
My approach is to map each comment to a metric impact: does it change TAM by >10%? 10–30%? >30%? Prioritize fixes that swing your result materially. For example, correcting a population definition often shifts TAM by tens of percent; swapping an ARPU from $2 to $3 might be smaller relative to addressable size but still relevant. After prioritizing, rerun the model with revised assumptions and present a short before/after summary to the community. Which assumption produced the biggest swing in your model?